Roblox Studio exhibits extreme lag immediately on launch, even the Start Page UI is choppy. When opening or creating a new empty baseplate place, the framerate is consistently less than 1 FPS and remains unusable. This behavior persists regardless of which project or place is opened.
I have included a video and microprofiler dump in the private comment to this report.
System Information:
CPU: AMD Ryzen 9 5900X 3.7 GHz 12-Core Processor
GPU: NVIDIA GeForce RTX 3070 Ti Founders Edition 8 GB
RAM: 32 GB
OS: Windows 11, version 25H2 (Build 26200, 7623)
Forum Reports on the Same Issue
I have seen several recent reports of this identical or similar issue, with varied suggested fixes that have not worked for me. Here are the links for reference:
Check your graphics settings on the HW - right now there’s issues with framerate limiters that cause slow downs in Studio because of how the system views Studio’s multiple graphics contexts. So if you have the rate limited to 60, or 144 or something it will drop the rate to some multiple of that (looks like 10fps or so). So check that first, either in nvidia control panel or other graphics control panels you might have installed.
I’ve also seen reports that GSync might have some issues, but that is unconfirmed right now and we’ll need some assistance reproing.
It miraculously fixed itself with no modifications on my end, so unfortunately I probably won’t be able to serve much of a use helping to repro the issue.
I will note to your questions though, that I had no frame limits enabled. Also, when I did have the issue, I attempted disabling G-SYNC which did not resolve it. My framerate was also much below 10fps, and generally did not seem to go above around 2 fps (and was often lower). It may also be helpful to know that opening a larger place file resulted in worse framerate, after a short while I’d be lucky to get a frame every few seconds which got exponentially worse until I was just frozen.
I think this is all the information I’ll be able to provide though unless it happens again. I’ll be sure to reach out if it does. Thanks.
Ok glad you are moving again. Its possible since it occurred on empty baseplate this is related to a plugin if you had recently installed any. Also possible it was a transient issue caused by a flag flip - assuming no other changes were made like driver updates. Nothing stuck out from the log you sent, we’d probably need a full microprofiler run to validate if a specific plugin is causing the issue. Let us know if it happens again.
everytime I tab out to like another app and tab back in my fps reduced to like 1fps and studio is unusable, it used to be fine, I havent messed with any graphic card driver or software stuff nor added any plugin. Sometime it would fix it self but sometime it won’t.
I believe I’ve made significant progress in identifying the cause of the extreme lag I previously reported in Roblox Studio. After further testing, it appears to be directly related to NVIDIA G-SYNC settings, with additional interactions from the NVIDIA overlay (“Instant Replay”/“Record” features). I’m outlining all my findings below in detail to hopefully assist with reproduction and a permanent fix.
1. How the Issue Re-appeared
For an extended period, Studio functioned normally regardless of my G-SYNC or overlay settings.
At some point, while developing, I accidentally pressed F11 (full screen toggle). The severe lag (<1 FPS) instantly began and persisted even after disabling full screen and restarting Studio.
From this moment, the lag became 100% reproducible in all subsequent Studio sessions (while G-SYNC was set to “Enable for windowed and full screen”), even without using F11 again. This suggests something about toggling into full screen may be useful in your reproduction to “kick off” or trigger the bug, after which it seems to reasonably persist for testing.
2. “Set up G-SYNC” Mode
My original G-SYNC configuration was “Enable for windowed and full screen mode.”
After accidentally pressing F11 (full screen toggle) while working in Studio, the severe lag began immediately—with <1 FPS performance, persisting even after closing/reopening Studio.
I experimented with G-SYNC settings and discovered that changing it to “Enable for full screen mode” (disabling for windowed mode) fully resolves the lag after applying the settings AND restarting Studio.
With this configuration, Studio is smooth regardless of full screen (F11) toggle.
Switching G-SYNC back to “windowed and full screen”—and reopening Studio, without pressing F11 at any time—brought the lag back immediately. Thus, the F11 full-screen action is not required to trigger the issue, but may make it easier to repro. (On my end, simply opening Studio is enough now.)
3. Visual Artifacts as Lag Side Effect
I also noticed that the screen recording I shared previously captured artifacts in the upper-left corner on Studio launch (cut-off “ROBLOX STUDIO” text/logo plus a “+” icon).
These artifacts only appear when Studio starts with the lag present, suggesting they are a side-effect of the bug.
When “Instant Replay” (NVIDIA Overlay) is enabled, Studio shows the same lag while set to the problematic G-SYNC configuration (“windowed and full screen”).
Once the lag is triggered, disabling “Instant Replay” is a sufficient fix to stop the lag.
However, even if I do not have “Instant Replay” enabled, Studio will continue to lag exclusively when in full screen (F11). Exiting F11 removes the lag immediately.
Identical behavior occurs with the NVIDIA Overlay “Record” feature active.
5. Driver Information
My current driver:
GeForce Game Ready Driver Version 581.80 (11/04/2025)
A new version (591.86, 1/27/2026) is available, but I have not upgraded in case further testing is required to pinpoint the issue on the current version. Please advise if I should update for comparison.
6. Summary Table (From my Testing)
G-SYNC Mode
Instant Replay
Studio Fullscreen
Lag?
Windowed & Full Screen
Enabled
Any
Lag
Windowed & Full Screen
Disabled
Windowed
No lag
Windowed & Full Screen
Disabled
Full Screen (F11)
Lag
Full Screen Only (G-SYNC)
Any
Any
No lag
Please let me know if you wish me to perform any additional testing, provide logs, or deliver microprofiler data before I update my GPU drivers. I’m happy to help diagnose further as needed!
I wanted to add another observation that may help with investigating this further:
Additional Visual/Overlay Issue When Opening NVIDIA Overlay in Studio Full Screen
While testing Studio with G-SYNC set to “Enable for full screen mode,” I pressed Alt+Z to open the NVIDIA overlay control panel while Studio was in full screen (F11). To my horror, instead of the overlay panel opening normally from the side of the screen, I got two separate, shrunken overlay panels
One appeared over my “Explorer”
The other appeared over the main workspace view
This also gave me several mouse cursors on screen. (On the plus side: I still did not experience any lag, even with Instant Replay enabled.)
I’ve recorded a video showing this overlay behavior for reference:
It looks like there may be some confusion on NVIDIA’s/Studio’s end about where the overlay panel should be drawn when Studio is in full screen mode.
Possibly-Related Quirk: Discord Screenshare
While I’m not sure if it’s directly related, this “window confusion” feels weirdly familiar:
Often, when sharing Roblox Studio (not in full screen) on Discord, Discord would frequently “bounce” the capture between different Studio panels (like Explorer and main viewport), instead of capturing the whole Studio app window.
This only happens when selecting Studio as the window specifically to be shared (sharing my entire screen works fine).
Wanted to mention this in case it’s related somehow.
Hello! Sorry to bother, quick question - I came to the DevForum to report the exact issue with the rate limiter. Is there any plan to resolve this? Unfortunately Nvidia’s software is too broken to understand that I want to disable the rate limiter, and it’s getting tedious to have to add Studio again because each update means a new exe…
Yes, its for sure not ideal. We’re still digging in on a fix (and reported issues with GSync as well) to determine what we can do on our end to have the rate limiter work properly.
For the workaround, we’re also going to have a stable exe location soon, so that should at least alleviate having to do the exemption every week.