Jitters when reparenting a rigidbody

Description

Following this part of the documentation I’m trying to implement the carrying behavior. It works, but with noticeable jitter when character drops the object.

This is my pick up code (it actually matches the documentation example):

GetComponent<NetworkObject>().TrySetParent(newParent);
GetComponent<Rigidbody>().isKinematic = true;
GetComponent<NetworkTransform>().InLocalSpace = true;
transform.localPosition = newParent.InverseTransformPoint(handlePosition);

And drop:

transform.transform.parent = null;
GetComponent<Rigidbody>().isKinematic = false;
GetComponent<NetworkTransform>().InLocalSpace = false;

Reproduce Steps

1. Setup a scene with two network objects, one is rigidbody
2. Parent rigidbody to another object
3. Move them by moving the parent one
4. Set rigidbody’s parent to zero

Actual Outcome

Object teleports for a moment to 0,0,0 (apparently, not sure) and then teleports back to its correct position. Also, it also participates in physics simulation, so it can move other objects located in 0,0,0 (you can see on the video that it pushes another character)

Expected Outcome

Object should persist it’s current position without teleports or jitters

Screenshots

Host is on the left. Jitters appear only on the client.

https://user-images.githubusercontent.com/5504685/232324945-be4b15d3-17f1-4824-be27-a76def1f850e.mp4

Environment

• OS: Windows 11
• Unity Version: 2023.2.0
• Netcode Version: 1.3.1, I also tried it with develop branch, the same results.

[NoelStephensUnity]

Excellent! 🚀 Feel free to reach out to us any time, and if later in your development cycle you feel like you have achieved (or are getting close to achieving) your project’s goals we always love to see the progress made!

Happy Netcoding! 😸

[NoelStephensUnity]

Ok, I think I have a solution but it might require a slight minor update to NetworkTransform. Same concept, just need to handle resetting the interpolators when a NetworkTransform is enabled when already spawned. Both sides still place the Cube under the socket… there is a timing issue with switching between Kinematic and non-Kinematic when dropping (it can collide with the player and cause slight bouncing off of the player), but that type of issue is easily handled. Will post the solution and have a PR up for the minor change (since you are pointing to the develop branch anyway).