Have you used the detailed microprofiler menu? i used to have an issue with my fps being wonky, turns out it was due to my cpu clock speed thinking roblox was a non important application, so the clock speeds were always low, which was fixed by switching to the high performance power plan.
I’m having the exact same issue after updating to Windows 11 24H2 as well.
Every Roblox experience I join (not including anything in Studio) has consistent lag spikes, even on a Baseplate.
My Specs:
OS: Windows 11 Pro (24H2)
CPU: Intel(R) Core™ i7-14700F
RAM: 32 GB
GPU: RTX 4060 TI
None of these are spiking according to the Task Manager and are running around 35% usage with the CPU running around 25%
This only happens in the Roblox client — Studio runs perfectly smooth and doesnt have these lag spikes
I also did a full reset of my PC, reinstalled all drivers, tried multiple other things with no avail.
having this issue does your fps also seem locked to 10 frames below the cap? my roblox stutters from 135 to 144 then has the regular frame drops and when i moved the cap to 240 it would be locked to 220 to 240
My clock speeds are between 5.7 ghz and 6 ghz I don’t believe that is the issue, It has to be something Microsoft did with 24H2, It has been a buggy mess since the start.
The 60 fps feels almost fake with how much stuttering there is when you lock to 60, I hope this gets fixed ASAP otherwise I’m going to have to revert my Windows version as this is like an unplayable amount of stutters.
On another post that I missed when making this post someone has the same issue and they are using the same CPU as you, coincidence? Or maybe its an issue with certain CPUS after the 24H2 update?
This same issue was happening to me on a I9-13900k and my I9-14900k and it seems people with a I7-14700F have the same issue
Could be relevant but that’s just a thought.
It’s possible its for some Intel CPU’s, not sure though, i can try to upgrade my laptop and see if that CPU is also having an issue with it. (Also Intel)
We’ve confirmed that there is another report about this issue that already has an active thread and is currently under investigation.
We’ll close this topic as a duplicate but you can stay tuned for updates and the possible fix in the following thread:
Thanks for reporting and your understanding.
Have a Nice Day!