Search Issue Tracker
Duplicate
Votes
0
Found in
2018.1.6f1
2018.2.0b4
Issue ID
1054530
Regression
Yes
Setting transform.localPosition on a rigidbody that is the child of another rigidbody causes desynchronization
How to reproduce:
1. Open the user-submitted project
2. Enter Play Mode, press the Space key and Pause the Play mode
3. Observe the Scene Window and the Console
Expected result: the localPosition on the rigidbody of the child cube is set correctly
Actual result: the localPosition is offset based on the parent's movement rather than the localPosition set
Reproduced in: 2018.3.0a7, 2018.2.2f1, 2018.2.0b4, 2018.1.9f1, 2018.1.6f1
Not Reproducible in: 2018.2.0b3, 2018.1.5f1, 2017.4.8f1, 2017.2.3p3, 2017.1.5f1
Note: Different behaviours observed between versions:
- In the 2018.1.6+ versions the child's collider ceases to update -- it stays in its previous world position until some major state change causes it to reset (like toggling whether the rigidbody is kinematic or not)
- In the 2018.3.0a7 version, the child cube remains frozen even though its position is continuously updated
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
- Errors and warnings are thrown after installing Visual Effect Graph Learning Samples
- Add Behaviour dropdown has a part in which the dropdown outline is cut out when the Add Behaviour dropdown is opened
This is a duplicate of issue #1059467