-
-
Notifications
You must be signed in to change notification settings - Fork 328
Roblox is still capped to 60 FPS after raising the limiter
If you have your framerate limit set to something higher than 60 FPS in Roblox or the Bloxstrap Menu, but you're still capped at 60 FPS, there are several reasons for why it could be happening.
If you're capped to 240 FPS, see Why you can't (or shouldn't) go faster than 240 FPS.
This might sound a bit stupid, but some people have reported Roblox "not feeling like it's unlocked" when it actually is (lol). Just to make sure, press Shift + F5
, which will open a framerate counter. Be sure you're looking at the 'FPS' stat. If it never goes any higher than 60, then keep reading.
If you don't know what exclusive fullscreen is, or you're not even playing Roblox in fullscreen, then skip this and move onto the next one.
Exclusive fullscreen is the alternative form of fullscreen that's enabled through the Alt + Enter
key combination. However, it typically enforces VSync, which will cap to your display's refresh rate. If you're using exclusive fullscreen, exit out of it and see if your framerate is still capped. See here for more information.
Laptops (especially gaming laptops) will often have measures in place that reduce rendering quality to increase battery life. One of these measures is to globally cap all games at 60 FPS (or even lower). Be sure you're plugged into wall power so that performance is favoured over power consumption. If that still doesn't work, check your system control software, where performance settings are often located. Windows has one, which you can find by searching "Choose a power plan" and selecting "High performance". If that doesn't work, gaming laptops will often have their own control software (e.g. Lenovo laptops have Lenovo Vantage, yours will have something similar), where you can check for settings too.
Your framerate cap may be forced in the NVIDIA Control Panel. You can look for it under 'Manage 3D Settings' and under 'Max Frame Rate'.
See something here on this page that is incorrect or you otherwise think should be changed? Please open an issue!