Except there’s a new .exe file now that you run in the same folder.
Download
Windows
If you’re screen is 60hz then both are equivalent. If you have > 60Hz refresh rate then download and run one, then upload the log and then run the other and upload the log.
Auto (based on refresh rate up to 120 fps): benchmark.zip (3.1 MB)
Running
You can run the exe directly, the output in powershell is not needed. The benchmark will load scenarios and run them for a limited amount of time. They will take longer if you experience slowdown, just leave it running until it finishes and make sure you’re not running anything else that uses much CPU.
The scenarios at full speed take this amount of time:
Scenario
Time (s)
1
10
2
10
3
10
4
10
5
6
6
6
TOTAL
52
It is expected you will experience slowdowns, so it will take longer than 52 seconds overall.
Posting Your Result
It will produce a file benchmark.log. If you ever re-run the program, it deletes this file and starts writing results to a new one. Make sure you run the benchmark executable until it closes itself. Either zip it and post it in a reply or put it somewhere and link it.
I ran three tests. The last one was on the forced 60fps, on my normal refresh rate(165). This one still seems to have gotten 120 fps however, so i’m not sure if I misinterpreted what the forced meant or not.
For the other two I set my refresh rate to the specified fps of the .exe(60 and 120 respectively).
I can’t seem to directly upload zips here(it might be a discourse setting at play), or find a site that allows the “emptying” of text files, just the download of them as a zip so that’s what I went with.
What are you using to gauge that it’s 120 fps? The tps is always 120, that’s the simulation speed (at least for now), but the fps should be 60 if forced. If not forced, it picks up to 120 fps (because above that it won’t look different since I didn’t implement anything that would do things like camera smoothing).
edit: Actually now that I think about it, the fps number in the log should be capped if you set it to be 60, so maybe it’s not actually capping it, I’ll have to check and re-upload.
edit2: Maybe try again with the new zips? I tested changing my screen refresh rate, and also the forced one, and it looks like it picked it up, since it’s saying 60 fps
I was looking at the fps counter in the log, which said I was reaching 120fps at the time. In the newer zip this is no longer the case, as it seems to have forced my fps to 60 despite my refresh rate being greater than 60.
I was able to replicate this to an extent, in the sense of getting the application to immediately close after running it + an error message that differs in a few parts. I’m not sure if this has any real significance, but I’ll post it anyways.
All I did to get this was moving the executable into a place without the the sprite and font folders from the previous tests’ zip, since that seems to be the condition Solorion ran it in;
