Nowadays, it's pretty standard to make the main category not favor machines that can run the game at higher framerates ("pay to win"). So I propose the leaderboard, especially Any%, be split between locked 60 fps and variable fps, such that they are no longer on the same leaderboard. The fixed value could be something other than 60 fps, as long as it's constant and reasonably reachable for low-end PCs.
There are many ways in which having as high a framerate as possible is ideal for speed. This includes any menu glitch segment where you hold the menu up for a certain length of time, such as pushing cabinets or warping while out of bounds (i.e. Church Skip, Sewer Skip, etc). And I just learned that I can do Marsh 1 skip easily with upcapped framerate, but it becomes impossible with uncapped framerate while I'm streaming because streaming reduces my max framerate.
Standardizing 60 fps has pros and cons, however, for the run itself.
- It would inherently make the run a bit slower, especially when traversing out of bounds, although it would make it consistent across all PCs.
- It would make the run MUCH more consistent, since maximum framerate will vary wildly based on one's CPU.
- It would allow runs to be performed WINDOWED, because it is impossible to truly uncap your framerate while windowed. This lets you alt+tab and not crash the game, and is a lot of people's preference for playing video games in general.
- It would make certain skips much more difficult, namely door boosts that shoot you upwards out of bounds. I also don't know if Air-Filled Tunnels 1 skip will work at all, since you need to fall afterward. The same is true of Church Skip, which requires uncapped fps to get out of bounds in the first place. To remedy this, you could allow uncapped fps only under specific conditions, but that feels hard to enforce consistently.
