RunService? Heartbeat vs RenderStepped?
(This is a bit broad) Hello, I have heard that ROBLOX has fixed the bottle-necking / bogging down of Heartbeat (RunService.Heartbeat) on client. Although, I know Renderstepped (RunService.RenderStepped) runs more off fps and client cpu/gpu. Im not sure which to use?
What im trying to ask is, which is better.. RenderStepped or Heartbeat? (Client)
I have done a few tests in studio, although Im unable to use my gaming computer at the moment, so there almost the same to me. Ideas? Which is better?
1 answer
It depends on what you are trying to do with them.
They changed Heartbeat from a fixed interval frequency of about 30 Hz to whatever framerate that the game runs at. This is very similar to RenderStepped, but there is one key difference.
RenderStepped fires before each frame is rendered and Heartbeat fires after (See this diagram).
So when you hook up a function to a RenderStepped event, it has to finish executing and yield before all the steps that go into rendering can occur. This is a potential source for lag.
But somethings you actually want to happen before each frame is rendered, such as updating a camera CFrame. In this case you would want to use RenderStepped.
However for all non-rendering related programs, you'll want to use Heartbeat.
For more information, check out this devfourm post.