So MM2 runners discussed why there seemed to be some variations in some people's times for Ignorance is Blitz, and the conclusion was reached that having a high framerate does affect the physics in an advantageous way. This wasn't acceptable, so a baseline of 60 fps was agreed upon (with FPS display required) to keep things fair for everyone.
Now, because this may also affect MM1, I will be enforcing the new rule for this game as well (not that there have been any submissions for ages). You must display your framerate using something like Fraps or Dxtory from now on, with the framerate capped at 60. If you are using VSync with a higher refresh rate than 60, cap your framerate to 60 (Dxtory can do this too, among other programs).
For current runs that do not display the framerate, I have no way of telling what the framerate is, so I would appreciate existing runners checking their settings to see if either VSync is disabled for the game, or mentioning if the monitor used at the time of the runs was better than 60hz to retroactively apply the rule. @OsamaJT @Niloquì @bluluxabica @reaXn @talal @Swaggles
I've removed my invalid "19.740" Dearborn Dash attempt from the leaderboards, because I investigated and found out that I was most definitely playing at 75FPS instead of 60FPS at the time of the record, (by looking at the timer sync) which in turn broke the game's physics engine (due to its age), and made me achieve a seemingly impossible time by inadvertently having an unfair advantage. However, due to the margin between my invalid run and 2nd placed run by @OsamaJT being small, I never noticed the irregularity of me achieving such a low time. Having an unfair advantage doesn't sit well with me, so I have removed the run.
Other than that, all my runs since July 2020 have an FPS counter, and I am not using the 75Hz mode of my monitor, but I'll still make sure that all my runs (regardless of the game) have FRAPS or MSI Afterburner's overlay displayed on top.
I truly apologize to anyone it has caused stress or confusion espiscially @OsamaJT and @Endothermia, or just even bothered them that I had an unfair advantage. I am going to attempt this speedrun again, and hope that I get a time similar to the WR.
. . .
Well at least now we know that the game breaks when the FPS is high, that's one good thing that came out of this saga.
Big salute to @PrdPak, he was more worried than any that he had an unfair chance, and he made the fair choice although it was against his advantage, after all, we are just a small community here, no place for feud among us, and this was more beneficial than problematic, thanks to @Mhmd_FVC and to @PrdPak once more.
