Hello folks,
Just wanted to explain what happened here, because I realise this looks bad from an external perspective. In our newer builds, improvements have been made to the network replication for Scene Graph. QA absolutely did manage to reproduce the issue in a build closer to what’s public right now, but when I attempted to reproduce in the newer version we’re currently putting bug fixes into, it no longer happens.
So it’s not that we just looked at it and said “works on my machine, no problem here”, it’s that it no longer happens in newer builds due to improvements that have been made to Scene Graph network replication behind the scenes. Generally if a bug no longer occurs and it isn’t something I specifically went out and fixed myself, then I’ll mark it “Could Not Reproduce” rather than “Fixed”.
If you run alongside the sphere in the repro project, then it will keep replicating no matter how far you get from where you originally spawned. Or at least, in my local version, I significantly extended the amount of floor under its path you so you could follow it a lot further, and wasn’t able to get into a state where it stopped replicating. Note that it will still stop replicating if it gets far enough away from where the player is currently standing, due to network optimizations, but it will start replicating again if you get back into relevancy range of it (I also tested this behavior to make sure that was the case).
As an aside, in case it’s useful info, if you want an object to disappear when it’s out of relevancy range instead of just freezing on the horizon, it’ll do that if you spawn it dynamically instead of placing it in the map.
Hope that was helpful.
Thanks!