Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.2.X, 2017.3.X, 2018.1.X
Votes
1
Found in
2017.2.0b6
2017.3.0f3
Issue ID
983374
Regression
Yes
Instantiated Kinematic Rigidbody2D's transform is offset when moving parent Rigidbody
To reproduce:
1. Open my attached project (RigidB)
2. Enter Play mode
3. Use A and D to move back and forth
4. Observe the differences between both swords in relation to their parents (black cubes)
Expected: rigid body added in runtime does not offset when moving
Actual: rigid body added in runtime offsets when moving (check .gif and picture attached)
Reproduced in: 2017.2.0b6, 2017.2.1p1, 2017.3.0p1, 2018.1.0b1, 2018.2.0a1
Not reproduced in: 2017.2.0b5
Note: check the project provided to see how both swords behave differently. One is parented in the editor, the other in runtime.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment