Client Sided Terrain Stops Being Interactable With After Being Streamed Out And Back In

Bug Reports Engine Bugs
,
1

I was trying to make some water that was loaded only on the client, to see if i could boost the server’s performance a little In my game, and I noticed that when water that has been created on the client gets streamed out, the player’s character stops being able to Interact with it once It has been streamed back in. This issue occurs only if the water has been replicated on the client, and while streaming is enabled. If the water was created on the server, or streaming is not enabled, the water behaves as normally expected.

Place File Containing a basic client water loader as well as the sprint script I used in the demonstration:
WaterCollisionBugTest.rbxl (62.9 KB)

A private message is associated with this bug report

Edit: After some further testing it appears that this occurs with all client sided terrain, not just with water.

2 Likes
2

Thanks for reporting this issue and providing a clear repro place.

Unfortunately client created terrain can currently be streamed out in streaming enabled experiences. We are investigating how to improve this behavior long term, but at the moment I would avoid client created terrain if possible.

3

Ok, thank you, it isn’t too much of a big issue, since I can just stick with server sided terrain, I had just hoped to possibly have terrain loaded only on the client in order to improve server performance.