What do you mean someone else moves it? Only the owner of the object can move an object and the results be replicated. Is the owner changing the position initially? What type of object is it? Who owns it?
It seems that if a new player joins, they see a replicated object at the initial starting position even if the object has since moved. The only way the location updates is if someone else who sees it moves it to trigger the replication update. Is there a fix or workaround for this?
Move - like bump into it, cause it to roll over. For testing purposes, just a cube with replicate and replicate movement enabled. Players can push or bump into the cube, which moves it, but a new player that joins won’t see this change in location until the cube moves again. Basically it seems replication only happens on changes but the initial location does not get sent over to newly joined players.
For now, the workaround I’m using is to put the object elsewhere out of view and then use blueprints to move the object to its initial position at the game start. Then move the object slightly on the server when a player joins. The slight move is enough to trigger replication, but the replication only happens if the object is in view. The object starts elsewhere out of view to cover the case for if the object (on the server) is no longer at the initial position and also too far from the initial position to be replicated. Without that last addition, the newly joined player still sees the object at the initial position because the object on the server is not near the initial position (and therefore the player) to trigger replication.
This seems rather messy, so it’d be nice to know if there’s a more streamlined way to handle this.