Currently, as of 10/27/23
, if there is a BasePart
instance that has been created or cloned by the client, said basepart is not physically simulated if it is outside of the TargetStreamingRadius
, even if integrity mode is disabled. This makes it impossible to implement certain game mechanics without disabling streaming entirely.
To reproduce:
- Open the attached repro file
- Run a playsolo session
- Observe the glass ball by spawn. Drag it up into the air using studio’s dragger tool, and let it go. Observe that the ball drops like normal.
- Walk away from the ball until it is outside of the streaming range. Drag the ball into the air again. Observe that the ball is not being simulated.
- Walk towards the ball. Observe that the ball starts simulating when in-range again.
- Stop the playsolo session. Set
Workspace.StreamingIntegrityMode
toDisabled
. - Repeat steps 2 through 5. Observe that despite integrity being disabled, physics still stops simulating when outside of the streaming radius.
LocalStreamingPhysics_Repro.rbxl (53.2 KB)
Expected behavior
It is expected that parts created by the client would not be impacted by streaming, particularly for physics. Physics being impacted makes it impossible to implement certain game features (e.g. imagine a bowling minigame where you have to hit pins with a ball on a large bowling lane).