-
Notifications
You must be signed in to change notification settings - Fork 449
Re-parenting of "In Local Space" client-authoritative NetworkTransform results in large interpolation #2843
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I thought maybe I could solve this as a general case in NetworkTransform.cs in either I also explored not making edits to NetworkTransform.cs and trying to fix this interpolation issue with normally available methods:
This seems to almost work, but there's still a small noticeable visual hiccup. I'm not sure if this is a result of interrupted interpolation or not, but that's my suspicion. |
@zachstronaut Running in distributed authority mode everything can be handled on the client side. v2.0,0 will require using Unity 6 (currently 6000.0.0b13), but you will notice several of the issues you have been experiencing similar to this can be avoided using the distributed authority mode where clients can spawn their own NetworkObjects locally and have full authority over the NetworkObjects they own. |
@NoelStephensUnity Wait... like, 2.x will only ever work on Unity 6? You're not supporting LTS? |
Closing this issue as it was fixed in #3013. As per last question for future reference NGOv2.X offers support from 6000.0+ editors and NGOv1.X offers support for older editors and as per this day also supports newer editors |
Re-parenting of "In Local Space" client-authoritative NetworkTransform results in large interpolation on non-owning client.
If a non-host client owns a GameObject with a client/owner authoritative NetworkTransform that is "In Local Space" and that object is re-parented by the server, the server/host will see the object interpolated across the difference in the before & after local position even though the world position has not changed.
The text was updated successfully, but these errors were encountered: