Performance monitor

Description

100% by me If you use anything from this project (fps meter, frametime count, interactive graph, ANYTHING), be sure to mention me in the credits section Remember that a high frametime is bad, if FPS should be high. and obviously, the average Thanks. Warnings: - This is best when you splitscreen or put it on a separate window. some computers automatically run minimized windows at a low framerate (1 fps for my computer). - Be careful on the graph, as it uses coordinate graphing instead of calculation graphing, and it might be a few pixels off - Crashes are considered under 10 FPS, it can't actually see when your computer crashed - When you scroll in the graph and you see "Err", it doesn't mean there was a lag there, it means the guessing system used to find the framerate timed out and returned "100", which isn't possible in scratch without mods. - a normal frame rate hovers around 27-31 in scratch, you can expect nearly double in Turbowarp - Turbo mode makes it return "Err" because it really does go over 100 - In my opinion, frametime is more reliable because you can see the exact millisecond it crashed

Instructions

Leave open when you go to another tab. when you see lag, you can come back and see the time it happened and the frame rate. there's also a graph if you need it. space to pause the graph. when you pause, it just keeps the graph, so when you unpause it will start with the current framerate. Got rid of graph scrolling because storing all the framerates was crashing my computer, and i have a pretty good graphics card. For those who don't know, FPS (Frames per second) is how many times the screen can update in a second. frametime is how long it took to update. 60 fps and ~0.16 frametime is exceptional, but you might not get that from a scratch project, even if your computer can do double that. it's just the limit for the java player (how scratch displays projects). Try turbowarp if you intend to leave this open for a long time: https://turbowarp.org/743239782?fps=60&hqpen