Dean Herbert 4c4939d18d Fix draw FPS being inaccurate due to using ElapsedFrameTime
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.
2022-07-21 19:17:58 +09:00
..
2022-06-17 16:37:17 +09:00
2022-06-17 16:37:17 +09:00
2022-06-24 21:26:19 +09:00
2022-06-17 16:37:17 +09:00
2022-06-17 16:37:17 +09:00
2022-06-17 16:37:17 +09:00
2022-06-17 16:37:17 +09:00
2022-06-17 16:37:17 +09:00
2022-06-17 16:37:17 +09:00
2022-06-24 21:26:19 +09:00
2022-06-17 16:37:17 +09:00
2022-07-01 15:17:26 +09:00
2022-06-17 16:37:17 +09:00
2022-06-17 16:37:17 +09:00
2022-06-17 16:37:17 +09:00
2022-06-17 16:37:17 +09:00
2022-06-17 16:37:17 +09:00
2022-06-17 16:37:17 +09:00
2022-06-17 16:37:17 +09:00
2022-06-17 16:37:17 +09:00
2022-06-17 16:37:17 +09:00
2022-06-24 21:26:19 +09:00
2022-06-17 16:37:17 +09:00
2022-06-17 16:37:17 +09:00