Welcome to my test. Press flag to begin and watch result. Usually when you do nothing, score is 56-60 fps. When you go in or out fullscreen it may lag a bit. You will see recent seconds on the chart. This on right is newest Also changing browser tabs may be a bit laggy. dont try on phosphorus xd https://phosphorus.github.io/#230649875 INFO: Chart may bug when you have low FPS
PLEASE NOTE! FPS Count is not real. This project is based on this rule: -60 FPS is 100% speed and efficiency So 30 FPS means it slowed down by 50% and 15fps means it slowed down by 75% and so on... But how does it work? So every second it starts counting number in variable Count. using script: always { change Count by 1 wait (0) sec * explained soon if timer > 0.99 do some things... } So when it lags, script is slowing down and counter is adding slower, but okay, why did i put wait (0s) here? For real, in scratch there is minimum wait limit so for example wait (0.000000000001) block doesnt really wait that short. If you write number below minimum then it just waits minimum number. I still dont know whats minimum number =) So that means this wait (0) dont wait 0 seconds. It waits but for a very short time. Try it yourself- as you remove wait block, it gets to very high speeds. ***I'm not sure if that is like this. That's my theory but i hope it's true*** >>>https://phosphorus.github.io/#230649875<<< I want to explain you the 50% of reason phosphorus speeds up so fast. So okay. In scratch there is "minimum time limit" that I described above ^^^^^^ but in phosphorus there are other things- It converts project to JavaScript code. JavaScript isn't like Scratch and that's why JavaScript recognizes wait 0sec blocks as don't wait command, so phosphorus ignores that block, next half of reason is just because it runs in JavaScript what is much faster than Scratch thanks for long hours spent here on reading this =D
