Relevance is not applied to a client's scene syncstate before client sends the first camera position update. Currently, the client waits for 2000 ms after connecting before sending the initial camera position. This is presumably to ensure that the user avatar (if the scene in question uses avatars) has been created, and the client is looking at the scene from the avatar's perspective, and therefore the avatar will not be incorrectly marked irrelevant.
However, in a scene that is heavy with assets this wait is not reliable, as creating the avatar may take even longer. To fix properly, needs the concept of an entity which is always relevant to a particular client, to avoid applying incorrect interest management to it.
Relevance is not applied to a client's scene syncstate before client sends the first camera position update. Currently, the client waits for 2000 ms after connecting before sending the initial camera position. This is presumably to ensure that the user avatar (if the scene in question uses avatars) has been created, and the client is looking at the scene from the avatar's perspective, and therefore the avatar will not be incorrectly marked irrelevant.
However, in a scene that is heavy with assets this wait is not reliable, as creating the avatar may take even longer. To fix properly, needs the concept of an entity which is always relevant to a particular client, to avoid applying incorrect interest management to it.