ruby hare
The Cube with Ghost Authoring Component shown in the screenshot is moved by the server with a simple moving system.
This works good until the client disconnects and reconnects to the server, then the client's world cube position keeps resetting to the one it had when the client disconnected, trying to move but resetting every snapshot or something similar. The cube keeps moving properly in the server world.
Thank you in advance!
ruby hare
Before reconnection (position synced)
After reconnection (position keeps resetting on the client even tho server is updating it properly)
ruby hare
This guy seems to have a similar issue
https://discussions.unity.com/t/prespawned-ghosts-stay-disabled-and-missing-prespawnssceneinitialized-component-in-netcode-for-entities/1577796
ruby hare
Another not resolved thread about this: https://discussions.unity.com/t/1-0-0-pre-47-prespawned-ghosts-from-subscenes-arent-synced-up/911805
So it seems to be a bug from Unity Netcode for Entities? I've tried with versions 1.3.6 and 1.4.0 and it's happening in both.
Prespawn Ghost desynchronization on client reconnect
rough flare
This sounds like a bug recently fixed, affecting prespawned ghosts after a client reconnects. What happened was that when a new prespawn scene is detected the client will request that the server starts streaming the ghosts in that scene. When the client then disconnects and reconnects, the server will stop streaming but the client still thinks streaming has been turned on. So basically it needs to be flipped off to trigger the flow where the client will again request streaming on those ghosts. You could try this just by manually flipping the streaming flag in the Inspector, just open the Entity Hierarchy, find the SceneSection for your entity scene and find the Streaming flag in the SubSceneWithGhostCleanup component (change it to 0 to turn off, you'll see it flip right back to 1 as streaming has been turned on again). Unfortunately this component is internal, so to run a query which just fixes that flag when you disconnect it requires grabbing the source for the package and moving it into your project, so you could just make it public.
The fix for the above issue should be in the next release, but I'm not sure when that is going out.