Fix inaccuracies in FPS counter

No offense to the previous coder, but the previous FPS counter was horribly implemented. How it worked is that it grabbed a set of FPS samples, spaced them over time and summed them. The problems with that approach, however, was:

• Frames too close to each other were ignored, causing frame drops to either not impact the counter or have a much higher effect than it should
• Since the samples were spaced, it was possible for it to keep samples that are many seconds old.

Either way, I simplified the counter to just counting the previous frames and summing them, and it's now way more accurate. It's not perfect, but it's closest to the current behavior while still fixing the problem.

Fixes #1047 (closed)

changed the description

added Bug label

mentioned in merge request !2048 (closed)

added 1 commit

• e3824b9f - fixup! Fix inaccuracies in FPS counter

Compare with previous version

marked this merge request as draft from Hanicef/SRB2@e3824b9f

marked this merge request as ready

merged

mentioned in commit 4ccba2a9

This was my goof so I'm just gonna merge it now.

changed milestone to %2.2.12

mentioned in merge request !2536 (merged)