PLEASE READ THE WHOLE THING TO UNDERSTAND HOW THIS WORKS!!! Instructions: Enter to start Space To Stop Change number Click to set number to exact value (by typing it out) Explanation: So, about a month ago I made a project that showed how the interpreter could only process an action a certain amount of times per frame. To improve my knowledge of this, I made a project that tested how many frames it took to do an action a certain amount of times. This project will count up from 0 to the number you set every iteration in a forever loop. To let you know when the iteration has finished, it will turn a bit. Guide: Here is a guide to the variables and lists onscreen: Variables: -Number is the number it counts up to, feel free to change this. -Time per iteration is many seconds (in real time) it takes to count up to that number -Frames needed is how many frames (keep in mind the fps is very low because we are straining our computers) it takes to count to the number -Fps is the frames per second for any other scripts running, whether is that sprite or in other sprite. It is very low because we are straining our computers. Lists: -Number is what the number equals each frame. It seems that on my computer, each frame (with 0.918274, fps) the counter manages to count up about 800,000 times. which means that that repeat loop is iterating 800,000 times!
@SS-2 for the same FPS tester they remixed my project with, I reused it here. @Silenttaco99 for helping me by giving their results. They said that it is controlled by your device and not just the interpreter - thanks!
