I didn’t know it still works…
Will this update significantly impact physics systems?
Could it break tower and obby genre games?
Then, can we expect features that limit PreSimulation (Stepped) and PostSimulation (Heartbeat) to 60Hz, while allowing other tasks to operate at 240/144Hz?
Not “significantly” from what we can tell, in part due to it being capped at 240Hz at the moment. There may be subtle differences, but players with FPS unlockers have never reported anything “significant”.
If the user raises their framerate cap, and their device can hit those higher framerates, then these events will run faster. As an example, if my powerful machine can run at 100 FPS, then task.wait()
may return 0.01 (whereas before it could only go down to 0.0167, 1/60).
If players get slower when laggy then with faster framerates than 60fps the character could be faster, or the character has speed limit?
After reading a bit more, I grow more attached to this change since it does affect certain built in functions.
However, what will replace the old task.wait()
? In some instances the strict 1/60 may of been essential to some games out there.
Nothing changes? If you use task.wait on it’s own w/o params you expect it to last a single frame…
What do you mean? I mean’t the 1/60 interval it’s self, like how the wait()
function is always 1/30 of a second.
While the idea sounds good on paper this would probably just lead to developers forcing a capped framerate because they’re too lazy to make their code not framerate dependent.
i assume the FPS unlock options are still pending because i don’t know how to enable that
Same, I have a 165hz monitor, but… I don’t see that framerate listed up there :/. Also, it’s weird to not see 120hz up there either, since that’s usually the refresh rate of most gaming laptop displays.
Some obby “tricks” don’t work well (or at all) on high FPS. Specifically, wall hopping. (Would rather have unlocked FPS though).
Really liking all the new settings but I feel like the settings menu is getting too unorganised. Definitely now that we have setting descriptions. I hope the menu can get split into categories (audio, video, controls, advanced) or even a general overhaul of the entire Roblox menu, like the one we had in AB testing in 2020-2021 if I recall correctly.
Not gonna lie the best menu was the v3 menu (2022), not sure why they just created a carbon copy of the old one.
All of these questions are like if having higher FPS was just introduced today which it isn’t lol. People have been using FPS unlockers for years and game developers have had plenty of time to prepare for them. If there was a serious issue with it then Roblox wouldn’t make it official
Yep, only affects parts with Shape = Block.
You would just pass a duration to task.wait if you want it to wait a certain amount of time
Note that this isn’t backwards incompatible. Frame time has always been variable.
If a script will run too fast because it doesn’t compensate for frame time, then it’s already running too slow on an old Androids where FPS can be much lower, and too fast on VR where FPS can be much higher.
If you want to wait 1/60 you should just call… well… task.wait(1/60)
!
task.wait()
has the specific meaning of “wait one frame regardless of how long it is”, if you want to wait for a particular duration then you should specify that duration.
An option to go below 30hz would be pretty useful too.
ex: Ensuring that a system doesn’t break in such a heartbreaking circumstance.