I used to just bust out at 9:30/mile and feel okay about it but my coach told me I should be doing my easy runs at at least 10:15+ and I felt the same way as you - it was harder to run slower. I saw another person who was having a similar problem say that whenever they felt themselves getting fast, they started walking to slow themselves down. I actually tried this for a few runs and it really helped - because I'd honestly rather run the whole time so this kind of forced me to settle into that comfy pace. Once I hit autopilot my easy runs actually were more around 10:50 or 11min/mile that was my cruise control pace. Drop Jabo's plugins - using closed source plugins only stunts progress. It was hard because I think I just want to be fast all the time but I kind of had to throw away that part of me that is obsessed with numbers and just remember why I loved running to begin with. Please note: This Web-Based emulation of Quake is extremely slow the game is not playable at this speed (although manipulating the settings for a lower resolution and reduced complexity will increase speed nominally). I'd suggest add a new Game Capture, Mode: Capture foreground window with Hotkey. Include GlideN64, AziAudio, and HatCat's Angrylion fork. This item is included for historical reasons only and will hopefully one day be. Find the name you gave the Game Capture and give the same hotkey in: Capture foreground window / Deactivate Capture.

Now open up any game Project64 and once the game is running hit the Hotkey and it should show up in OBS, same will. Announce development builds in both x86/64 with the 2.3 release - include development builds of AziAudio/GlideN64, if possible.

Quake ii running slow pj64