Bug [1.0.8] (IN-40652) IsRelevant ghost relevancy fails to "wake" relevant prespawned ghosts

Apply IsRelevant mode to the ghost relevancy set and add all ghost entities.

Sometimes at high pings using the simulator (the higher the more likely this will occur), prespawned ghosts on the client will not receive server data despite being registered as relevant on the server. Since all entities are added to the set, all entities should be considered relevant.

For example, put the simulator on broadband 95% international. Add a rotating prespawned ghost cube to the scene. Add a system that always sets this ghost to be relevant to all connections. Repeatedly start playing until randomly the cube will stop rotating (it will continue to do so on the server but the client will not receive any rotation).

Using the inverse relevancy logic, IsIrrelevant, does not have this problem. Problem is with IsIrrelevant, there needs to be proportionally large amount of key inputs into the HashMap to indicate irrelevancy compared to only the visible entities that are relevant.

 

Dynamic or static optimized ghosts. It doesn't matter.

No. In fact, I got a reliable reproducable going. Using IPC (no simulator) going and all prespawned entities indicated as relevant from first frame, none of them receive rotation values from the server. Delaying setting any prespawned as relevant by around 100 frames makes them to rotate.

Not that I can tell. I only have 25 prespawned and 2 player ghosts. That should be practically nothing. The player ghosts in particular (player + character) are properly networked and function perfectly. As seen by the fact that they are controllable using WASD.

Both. I have a prediction switcher by distance system so two of the nearest prespawned ghosts are predicted and the rest are interpolated.

Yes. And disabling the system does not fix the problem of prespawned not rotating. In the repo sent to the bug report, the system was disabled.

Rotation is handled through the physics system and just setting initial angular velocity as a set value other than 0.

Normal (Lights rotating):
Broken (Lights not rotating):
Lights being the rotating prespawned objects. The only difference between the two is a 100 frame delay that mysteriously allows the light prespawned ghosts to be registered as relevant where doing so immediately does not.

Full reproduction project (actually my full project, I really cant trim down all the modules, too spagetti code, it should work out of the box though): IN-40652. Details on how to run and reproduce the problem in my small project located in the report description.

Should be immediately reproducable in the repo provided using IPC (no simulator) multiplayer Client/Server settings.

 

I do want to mention this remains an problem in the newly released 1.0.8 netcode version.