This can cause players to die which is pretty serious.
The game uses custom characters that run locally and the server sets Player.ReplicationFocus to a part inside the server’s camera (so it doesn’t replicate to everyone). StreamingMinRadius is 1280, and StreamingMaxRadius is 4096.
It seems to happen at random, and isn’t easy to repro.
I can’t believe this is still happening. We reported this bug during our Summer Incubator in 2018. Our game also uses custom characters, so I wonder if there’s any correlation there?
Are these chunks far from origin or where the character spawned? I read something about streaming enabled not loading chunks when the camera focus is not near those chunks.
The map is about 10k by 10k studs, and the glitch happened to me at 1900 studs from the origin.
The game sets camera.Focus depending on the player’s position. Although it is possible for the player’s camera.Focus to change to the character editor area when they edit their character (which is usually within a few hundred studs of their ReplicationFocus part).
I can confirm this issue is not related to custom characters as I’ve noticed this same issue when using the default character.
Yesterday, I was experimenting with an infinite terrain generator. There were a few noticeable issues with terrain and network streaming:
Terrain existing on the server did not always render on the client (as seen above, however, I can confirm the issue persists regardless of custom characters)
Other characters at far distances still rendered when the terrain around them was not being rendered giving them the appearance they were walking on nothing (the expected behavior would be for the character to not render too)
I’ve made a settings change that should hopefully resolve the issue for the places @Tomarty and @UnderMyWheel encountered them on. If others are also encountering this problem please let me know.
The issue @berezaa encountered was reported to us on Sept. 15 and fixed Sept. 18. While the symptoms are similar (holes in terrain) the causes of this recent issue and the one from 2018 are different. This is not a bug that has lingered since last year, this is a new issue.
