RunService.PostSimulation event giving incorrect delta time

Hello, I recently wrote a thread about a strange issue and discrepancy happening with RunService.PostSimulation where it gives you an incorrect delta time. I’m not sure if it falls under usage that is currently supported, as it appears to only happen when your framerate exceeds 240hz (which seems partially supported by Roblox, but isn’t official yet), but it still seems to indicate an underlying issue with the event. You can find more information here:
https://devforum.roblox.com/t/an-issue-currently-affecting-runservice-delta-times/2795499/6?u=thegreendeveloper

Currently, this behavior breaks the expectation set by the documentation for these events, which define the deltaTimeSim argument as The time (in seconds) that has elapsed since the previous frame.

It also causes a discrepancy with RunService.PreSimulation (as well as all the other RunService events), which one would expect to be running in lockstep with RunService.PostSimulation, as PostSimulation will outpace PreSimulation.

With every other event giving expected values, this points to an issue specifically with PostSimulation.

3 Likes

This is just an acknowledgment announcement!

We’ve filed a ticket into our internal database for this issue, and will come back as soon as we have updates!

Thanks for flagging!

1 Like

I noticed this was closed. The issue still persists, with 240fps now being an actual in-game option for all experiences. Was this closed as not being fixed?

2 Likes