Setting rigidbody position with ".MovePosition()" a single time results in a desync between clients.
This successfully moves the rb to the desired position to the owner of the object but not the other clients.
KHi @gubebra. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. 
K----------------------
In NormalVR's networking solution, the synchronization of objects between clients is handled by the
If you're trying to directly move an object, make sure to mark it kinematic. This lets PhysX know that you're controlling its position and it should not simulate the object directly. It also tells
In a multiplayer environment, a game object and its transform can exist on multiple clients. This means that there are multiple copies that all claim to know the position of this object, but only one of them can be considered the source of truth. This is where ownership comes in.
In NormalVR's networking solution, the synchronization of objects between clients is handled by the
RealtimeTransformRealtimeTransformIf you're trying to directly move an object, make sure to mark it kinematic. This lets PhysX know that you're controlling its position and it should not simulate the object directly. It also tells
RealtimeTransformIn a multiplayer environment, a game object and its transform can exist on multiple clients. This means that there are multiple copies that all claim to know the position of this object, but only one of them can be considered the source of truth. This is where ownership comes in.
RealtimeTransformTherefore, to move an object with a
If you're calling
In summary, to ensure that the Rigidbody's position is synchronized across all clients, you need to:
RealtimeTransformRealtimeTransformRealtimeTransformRequestOwnership()If you're calling
RequestOwnership()In summary, to ensure that the Rigidbody's position is synchronized across all clients, you need to:
- Add a
component to the GameObject.RealtimeTransform - Request ownership of the
component.RealtimeTransform - Set the Rigidbody's position.
- Avoid immediately clearing ownership after setting the position.
----------------------
Note: you can ask me a follow up question by @ mentioning me again
----------------------
K@599054560270483456 kapa.ai is still learning and improving, please let us know how it did by reacting below
GI'm doing all 4 steps, and the ball was kinematic at the time I used move position.
Mmaybe you are dropping the packet if it only moves once as RT uses unreliable
Msolution is to wiggle it a bit for a few frames or use reliable to send one message when moving once
Mor wait for normcore to add a reliable move message
GYeah that’s what I’m doing, although I don’t think this is the ideal solution
Mthey are going to add reliable move in the future but this is the easy method now
Mthe other method is to make your own RT with reliable move message
GThanks for the help Mechabit