colbert2677
(ImagineerColbert)
October 5, 2019, 5:06am
15
Please ignore my last post, it was somewhat misleading and misinformed.
RenderStepped blocks the execution of steps, not necessarily frames from being rendered. It’s better to read a few of the linked posts in the following posts since they explain it better than I do:
Where has that sort of diagram been all my life?
I made it pretty for anyone who wants to write a wiki article about all this.
[image]
To clarify, Stepped would get a frequency boost too?
Edit: Made it less eye-melty, added user input
(Diagram of how RunService events are executed)
If you look at the picture above, you can see that RenderStepped blocks the execution of any further steps until it yields. It runs before all the Rendering / Network Replicate / wait() resume / Humanoid / Stepped / Physics / Heartbeat. So if you stick all of your code in there, it means that all that code has to execute before the rest can begin. In that same image, everything after RenderStepped does run in parallel. So there are two pipelines there, and the top one (Rendering) will run in par…
(Explanation of RenderStepped and its impact)
1 Like