RunService:BindToRenderStep() Only Runs When Viewed Through Corresponding Perspective

Bug Reports Studio Bugs
,
1

When using RunService:BindToRenderStep(), the attached function only fires if viewing through the correct perspective.

For example, if a server script binds a function to render step using the method above, the function will only run when the server view is active. Remaining in the client perspective causes the function to not run at all.

Here is a solo testing video of a part with a BindToRenderStep() function in a server script that will print “This is part reporting for duty” for every second using the passed DeltaTime parameter:

When using a client / server test, however, it functions normally:

Replication:

  1. Create a part with a script inside of it
  2. In the script, create a function that gives a good indicator that it is running
  3. Connect that function to RunService:BindToRenderStep()
  4. Solo test to see if it is functioning, flip through different perspectives to see the different results.

Expected behavior

Upon starting a solo test, both the client and server BindToRenderStep() functions should be running at the same time.

3

In real games the server does no rendering at all, which is why BindToRenderStep() and RenderStepped don’t work properly on the server in Studio. You should probably be using one of the other events like Stepped, Heartbeat, PreSimulation, PostSimulation, etc.

The documentation says:

As it is linked to the client’s rendering process, BindToRenderStep() can only be called on the client.

3 Likes