mirror of
https://github.com/osukey/osukey.git
synced 2025-08-03 14:46:38 +09:00
4c4939d18d
Had a feeling this would be the case. Basically, we're calculating on the update thread and checking the last value of draw thread's `ElapsedFrameTime`. In the case that value is spiky, a completely incorrect fps can be displayed. I've left the spike display do use `ElapsedFrameTime`, as `FramesPerSecond` is too averaged to see spikes.