You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When syncing a Drive across the network, I can easily sync the value itself, but there's no easy way for me to then use this value to change the state of the other user's Drive. As it is, I need to either use the Target system, or manually set the position/angle of the drive based on the value and the parameters (like axis)
Describe alternatives you've considered
I would like a function like "SetValue" (and maybe "SetValueSilent") that sets the Drive to the correct state based on the value. It could be normalized or not.
The text was updated successfully, but these errors were encountered:
would this not cause an issue with the joint drive?
because i assume what you're after is:
given a linear drive has a travel of 0 to 10
if the drive is moved on client A then the joint is moved along the axis of the drive
and on client B, the position of the drive is synced immediately to the position of client A drive
But the issue with that is you're not changing the position of the interactable, you're driving it with a rigidbody force along the limits of the joint.
so client B cannot be synchronised without driving the interactable position with rigidbody force (which is what target value is doing)
Is your feature request related to a problem?
No
Describe the solution you'd like
When syncing a Drive across the network, I can easily sync the value itself, but there's no easy way for me to then use this value to change the state of the other user's Drive. As it is, I need to either use the Target system, or manually set the position/angle of the drive based on the value and the parameters (like axis)
Describe alternatives you've considered
I would like a function like "SetValue" (and maybe "SetValueSilent") that sets the Drive to the correct state based on the value. It could be normalized or not.
The text was updated successfully, but these errors were encountered: