FPS benchmark looks buggy - look at the numbers, they should go down not up then down. Rerun benchmarks also skips rerun of #1 which I think is missing a leading digit.
Updated it so that rerunning or cancelling the benchmark doesn’t break or mess up the results.
I’m not sure if this is the problem but GameMaker averages the number over the last second or two so, so if the simpler tests are too fast it’ll churn through it before the figure has time to correct itself after the lag of spawning all of the geometry. I added a five-second delay before the start of the first test which will hopefully be enough to get past that.
Yep, the start was screwing up the first reading. Numbers look good now...
Think it'll need a lot more vertices/lights to hit 60fps :)
Compare the above to the APU - an AMD 610M - part of the 7745HX CPU in my laptop...
Laptop used for reference - https://www.lenovo.com/gb/en/p/laptops/legion-laptops/legion-pro-series/legion-p...
By your own definition it doesn't work accurately other on really slow machines. The previous test will always affect the result for the current test. Test1 will always have a higher FPS so the first readings for Test2 will be artificially higher than real - repeat this observation as it will hold true for each test
Like I said, i built in a delay between rounds that should wait out the time it takes for the sliding window to catch up.
That said, I checked the HTML5 source and it apparently takes two seconds for the fps value to refresh and I only accounted for one, so I edited it again.