When Roblox’s max framerate option is set to 240 fps, several RunService events will sporadically report their delta time as 0.
This behavior is unintuitive, as one would reasonably expect some time to have passed since the last frame, and very easily causes issues such as divide by zeroes by code that expects delta time to always be non-zero.
This only appears to occur at 240 fps, and also seems to affect the client significantly more than it does Roblox Studio.
I have confirmed that this issue is reproducible on hardware other than my own, but I figure the hardware must be capable of reaching 240 fps in Roblox to experience this issue.
Reproduction RBXL:
DeltaTime Reproduction.rbxl (53.3 KB)
Reproduction place, empty baseplate that prints to the Developer Console (F9):
Developer Console output:
Expected behavior
I expect all RunService events to report a non-zero delta time, as is logically expected, and as they normally would with the framerate set to something other than 240 fps.