Try it with your actual screen FPS: https://turbowarp.org/1120529267 What you can do here: - Watch the numbers; - Drag sliders to try different things; - Press (R) to reset basic sliders; - Press (Space) to automatically calibrate the Smoothness slider. If you're a math nerd, then you may want to read what's next: This experiment was an attempt to determine the average FPS value by using average Delta (Δ) timings, to make it stay smooth and stable. Use sliders to customise the interface and behaviour: - If Accent is set to 0, the colours will be dependent on the current shown values. - If Background is set to -1, it will use the division by 0 to have a grey colour. Default value is 0. - The converter will limit numbers to the 5 most important digits. 1 to enable, 0 to disable. (imported from an older version of Crazy Coins Showcase!) - Set Smoothness to its maximum value for absolute FPS (it won't be smooth anymore). Set it to minimal to determine the exact FPS, but you'll have to wait a while to get close to the real value (until it gets stable- of course your FPS never went to 2000+ just because the average says so!) - Reset to Defaults: Press (Space) to automatically adjust Smoothness to your current refresh rate. Press (R) to reset other sliders. The smooth timer is a (original?) way to calculate the average FPS in a certain time (it will vary less, but still adapt to the overall refresh rate). This experiment came to a few conclusions! - Scratch's exact FPS is NOT EXACTLY 30: it's on average 30.3030303... - TurboWarp's 60 FPS mode isn't exactly 60 FPS (at least on my device) It actually falls between 62 and 63. Set the FPS to 0 to make it exactly your screen's refresh rate, which is usually 60. (better screens usually have 90, 120, 144 or 240). - Again in TurboWarp, I've also tried multiple custom FPS values and it seems to often round to the next tens. For example setting it to 95 FPS may make it around 100. - This experiment helped me fix a bug in the game! - I made a smoother stopwatch, that was my main goal. But it's not perfect, because it's slowed down at the beginning. The "username" block is only used to determine if customisation settings should be reset while clicking the green flag. It is logged in a local variable, but will immediately change if another account uses this project. Well, seeing number grow is satisfying, but maybe you should try my biggest game ever instead! Try it at:
