I have a 480hz monitor, and before the allowlist Fast Flags change, I would use the FFlags DFIntTaskSchedulerTargetFps and FFlagTaskSchedulerLimitTargetFpsTo2402 to uncap my framerate from 240, allowing me to go up to 480 fps. However, due to FPS related fast flags not being on the list, I can no longer go over 240 FPS. This makes it impossible for me to use my 480hz monitor to its fullest capabilities.
If this issue is addressed, it would improve my development experience because …
I could use my monitor to the fullest refresh rate without it being capped to a lower framerate. Even simply allowing Roblox players to type their FPS instead of using a dropdown would be sooo nice!
Going above 240Hz is intentionally not supported at the moment as it introduces some quirks to the physics engine and the rate at which RunService events and similar are fired. We would like to fix these at some point, but the limit is intentionally placed and likely will not be lifted without work in that area.
I think that high refresh rate monitors are becoming a more standard option that a lot of people are using. I would really like to see Roblox supporting higher framerates, even unlimited as I think there are a lot of games that would really benefit from it.
Hell nah, delusional take L
Keep backwards compatibility with old hardware, i hate this mindset of “just get new tech hurr durr” it’s e-waste, and you’re contributing to it.
I don’t care if i get banned or blocked for this, my opinion
It’s shocking to me that this is the official position of the dev team. I used an FPS unlocker for literal years with zero issues, and when the official FPS update finally drops, you guys are hard capping it at 240, and patching out all true FPS unlockers? Insane. Truthfully I can’t believe that Roblox even bothered releasing the update under these limitations. I don’t pretend to have any understanding of the specific issues referenced, but we’re living in the year 2025. Come on.
Also, a word about in-game framerate vs. monitor refresh rate. I’ve seen a ton of comments which claim that any in-game framerate your system can achieve above your monitor’s refresh rate is useless, and that you should cap your game to your monitor’s refresh rate to “save resources” (or some variation thereof). This is NOT TRUE!!! While your monitor may only display, say, 240 frames every second, your GPU does not perfectly generate one frame every 1/240th of a second. Therefore, a higher refresh rate will still reduce felt lag because your monitor will display a frame which was generated more recently at higher framerates. Source: https://www.youtube.com/watch?v=hjWSRTYV8e0
Additionally, I have no way of meaningfully proving what I’m about to say besides the eye test, but something is wrong with the new FPS cap. My game will often seem to stutter at random, despite the FPS counter staying at 240. This was never an issue for me when using a true FPS unlocker, but the game feels much less smooth now. This could be related to the above discussion of frame latency, but honestly the difference is so severe I don’t think that alone can explain it.
To summarize: Tired of my game feeling terrible. If we had true unlocked FPS for 7+ years, why is it being taken away now? And why is this update being billed as an improvement?
For what it is worth, this is definitely not a result of the official framerate feature. The FPS unlocking tools people used changed flags, which is all the official one does as well. It also definitely is not a result of being at 240Hz instead of over it.
I’m aware that it wasn’t an “official feature,” but it was definitely a feature that existed, that wasn’t hard to find, that a lot of people used for a long time. I don’t buy in to the argument of “the physics engine can’t support it, etc.” Also, the explicit purpose of the FastFlags crackdown was to target exploits, which also doesn’t seem relevant here.
Respectfully, I disagree. I have a good amount of hours on both versions of the game and it definitely feels much worse with the 240 fps cap, even though my monitor is only 240 Hz.
In the future, if said problems were fixed, would it be likely that we would gain the ability to select a framerate limit of our choice via something like an input box?
good question, actually! i have no idea lmao.. that would be smart, although i don’t know how odd fps values [if any] would work [for example a 73 fps limit]
I’m not sure when would be the best time to ask this, but when should players ask or even put in a “ticket” to work on those quirks so 480fps could be a future possibility?
Honestly I highly doubt this will ever happen simply due to the fact it is so low on the “to do” list because it’s so unimportant vs other stuff.
Unless it’s an easy fix, but because it’s engine physics issue I doubt it.
There are tickets, but as you have mentioned they are fairly low priority.
A specific feature request of “allow FPS higher than 240”, targeting why specifically that is valuable is something you should do if you are passionate enough.
My take has nothing to do with E-waste or trying to get rid of backwards compatibility. games have had “unlimited” as a framerate option for a long time. Not having higher framerate options just limits player experience. The argument that I made is that; in the current climate it is a lot more likely that people have systems which run at a higher performance. My system included, it is many generations behind what is currently available but still I am getting limited by the current settings that roblox offers.
How does offering the option for higher-end hardware to bring out the full potential of their hardware prevent backwards compatibility here? You’re making zero sense with this take. It’s not like they’re asking for some forced requirement that Roblox only support the higher-end stuff.
