I noticed the CylindricalConstraint continues to rotate on the client meanwhile on the server its frozen in place.
The only way to prevent this from happening is by updating any property on a heartbeat step, but that would cost a lot of network bandwidth and cause a lot of lag when used on a bigger scale.
The issue makes the CylindricalConstraint too unreliable to use.
As of now i have to update any property of the cylindrical constraint on a heartbeatstep in order to make it stop rotating on the client.
This fix is impacting both the performance and network bandwidth as it would constantly replicate to the server on every heartbeat step for any cylindrical constraint i use.
Could i get some information on whether this issue is being looked at as of now or not?