09-10-2024, 10:17 AM
(This post was last modified: 09-10-2024, 10:20 AM by josemendez.)
Hi Paul,
The problem is that ropes are not synchronized between server and client at all, and neither are rigidbody velocities. As a result, any velocity-dependent effects such as joints, friction, or in Obi's case dynamic attachments won't work properly.
In this case the client's rope is applying a force to the rigidbody which modifies its velocity. It stands to reason that the server would then set the client's rigidbody velocity to zero (as the rigidbody isn't moving in the server), but that's not the case: only the position is synchronized, which is akin to teleporting the rigidbody back to the position dictated by the server. The client's velocity value is kept and as a result the rope starts wandering around as it believes the rigidbody is about to move to a new location - after all the server is not telling it otherwise!
A simple workaround is switching the client's attachments to static instead of dynamic. Since static attachments work purely based on position and do not involve forces/accelerations/velocities, the lack of velocity syncing doesn't have any negative effects.
A proper solution would involve syncing either rigidbody velocities, or syncing particle positions - so that the client's rope particles are properly sync'ed.
kind regards,
The problem is that ropes are not synchronized between server and client at all, and neither are rigidbody velocities. As a result, any velocity-dependent effects such as joints, friction, or in Obi's case dynamic attachments won't work properly.
In this case the client's rope is applying a force to the rigidbody which modifies its velocity. It stands to reason that the server would then set the client's rigidbody velocity to zero (as the rigidbody isn't moving in the server), but that's not the case: only the position is synchronized, which is akin to teleporting the rigidbody back to the position dictated by the server. The client's velocity value is kept and as a result the rope starts wandering around as it believes the rigidbody is about to move to a new location - after all the server is not telling it otherwise!
A simple workaround is switching the client's attachments to static instead of dynamic. Since static attachments work purely based on position and do not involve forces/accelerations/velocities, the lack of velocity syncing doesn't have any negative effects.
A proper solution would involve syncing either rigidbody velocities, or syncing particle positions - so that the client's rope particles are properly sync'ed.
kind regards,