Saving to test on turbowarp :P https://turbowarp.org/1235789733?fps=60&turbo Feel free to test this with different framerates
I'm basically making an algorithm that detects the framerate and processing speed of the system so movements are consistent in the case of lag spikes and framerate adjustments like turbowarp's 60 fps. This is done by running 2 scripts at once- one that resets a timer every _ seconds (which is the frame segment), and another that counts frames until the timer is reset (which is what the frames counted variable is for). Then the script divides the counted frames by the frame segment, which represents frames/seconds, which results in the framerate in frames per second, or fps. I think I messed up somewhere, since changing the segment length results in a different framerate. It's likely not lag caused by the process, since if that were the case, the smaller the segment, the lower the marked framerate, since it would count frames slower, but the opposite seems to be true instead. Scratch normally runs at 30 fps, so the difference between that and what I've calculated is interesting.
