Executing console command “t.maxfps 120” (or any other value) sets max fps to 120, but the moment I hit “Play” it is back to 60. Regardless of whether I execute the command during play or edit mode, the value gets reset back to 60 on (re)entering play mode. I’m on 5.5.4 now and it wasn’t that way in 5.5.0 and the value would persist all the way until editor restart. Did anything change? Can there be something else causing this behavior?
Hey there @deyama2012! I don’t see any notes about changes that should affect this in the hotfix notes. Maybe the minor updates triggered the defaulting of the “Use Fixed Framerate” setting in Project Settings. This may override the command if it’s checked.
Hi! Sadly, I don’t have “Use Fixed Framerate” setting enabled
I have the same issue. Maximum FPS keeps resetting to 60 every once in a while, and I have to run t.MaxFPS 0 to fix it. It’s annoying. I also have “Use Fixed Framerate” disabled. I’m on 5.6.1. Haven’t figured out how to reproduce this.
The “Errors/warnings reported while playing in editor” popup also makes the FPS go to 60 as long as it’s visible. This is reproducible always.
If I set “Use Fixed Framerate” to 120, then the game becomes slow-mo when the error popup is visible, in addition to the FPS going to 60.