Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.4.1f1
Issue ID
839232
Regression
Yes
[Physics] Objects with Configurable Joint get their position changed to NaN when addForce is called
To reproduce:
1. Open attached project.
2. Play "test" scene.
3. Look at the Console window. You should be getting "Invalid AABB aabb" and "Invalid AABB rkBox" errors.
These errors happen most of the time, but not always.
Expected result: Scene stays as it is.
Actual result: Objects with "Configurable Joint" get their XYZ Position changed to NaN. "Invalid AABB aabb" and "Invalid AABB rkBox" errors appear in a Console window.
Workarounds:
Select all "JointHeadpiece" and change their Scale from (-1,1,1) to (1,1,1).
or
Select all "JointHeadpiece" go to their "Configurable Joint" component and change "Angular X Motion", "Angular Y Motion", "Angular Z Motion" to Free.
or
Select all "Cube" objects, go to their "Configurable Joint" component and change "X Motion", "Y Motion", "Z Motion" to Free. (but then cubes will fall).
or
Avoid some Rigidbody.AddForce values in the script.Error happens when both X and Z values are non zero.
Reproducible with: Unity 5.4.2, Unity 5.4.1, Unity 5.4.0
Not reproducible with: Unity 5.3.6 and older
Fixed in Unity 5.5.0
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
Add comment