Resolved [1.0.0-exp.15] Prespawned ghost entities can not be immediately despawned using ghost relevancy

Prespawned ghost entities loaded in at startup can not be despawned using the ghost relevancy, neither SetIsRelevant or SetIsIrrelevant, unless a period of time has passed. In my testing, it varies between 3 to 5 seconds after initial startup of the server world. Depending on the client latency and load duration

Reproduce:

1. Have a prespawned ghost auto-load in at startup.

2. Have a ghost relevancy system setting all ghosts to irrelevant.

3. Expect that the prespawned ghost will disappear from the client hierarchy. This however does not happen.

4. Now add a 5 second delay to the ghost relevancy system. I.e., if (state.WorldUnmanaged.Time.ElapsedTime < 5f) return;

5. Notice that after 5 seconds and once the ghost relevancy system starts running, the prespawned ghost disappears as expected.

 

Yeah i have the same issue.

Also happens if that scene entity is relevant for the connection it won't receive ghost field data.

 

Thanks for taking this up.

I have 1 client ghost and about 30 prespawned plus or minus 5 depending on the location it spawned in.

 

Huh, hrm. Okay, so my custom hybrid linking system had with disabled filter option so it is rendering disabled entities, thus making them appear as if they were fully networked when they're not. The option is so prespawned entities show up in scene view and outside of play mode where all ghosts are disabled. Added in a check for that and everything works now.

Sorry about that. Bug on my end.