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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment