HingeConstraint CurrentAngle not replicating to server properly

Bug Reports Engine Bugs
#1

Reproduction Steps
The CurrentAngle and/or TargetAngle property of HingeConstraints do not properly replicate to the server, returning simply as 0 if below an approximate value of 0.8 degrees irrespective of whether it is positive or negative

Expected Behavior
Client CurrentAngle = Server CurrentAngle

Actual Behavior
See the following video:

Issue Area: Engine
Issue Type: Other
Impact: High
Frequency: Constantly
Date First Experienced: 2021-10-14 10:10:00 (-04:00)
Date Last Experienced: 2021-10-15 14:10:00 (-04:00)

1 Like
#2

Thank you for the report! I’ve created a ticket for this, we will look into it.

Edit: Would you mind uploading a repro place? It’s not clear to me how ActualCurrentAngle and LocalCurrentAngle are being calculated.

1 Like
#3

ActualCurrentAngle is set by taking the CurrentAngle property on the server and setting the attribute for it on the server

Conversely, LocalCurrentAngle takes the CurrentAngle property on the client and sets the attribute for it on the client

A place file will be provided shortly

Edit: Unable to provide a place file at this time

#4

The train community is also having a major issue with the trains. We use rod constraints to connect each car together, and it’s having issues displaying other people’s trains going around curves and switches. Here is a link to the full post I made about this last night.

I’m not sure if this stems from the same issue that you are having, but there’s an issue nonetheless with constraints I believe.

#5

I rolled back the change that was causing this issue, so it should now be fixed. Thank again for the report!

Edit: Based on the last reply to this thread (Ro-Scale train games broken!?!?! - #8 by DieselMultipleUnit) it looks like the issue is fixed.

1 Like
#6

Do me a favor
START USING BALL IN SOCKET CONSTRAINTS theyre much better and stabler on trains

1 Like
#7

I’ll look into it, thank you so much!

#8