Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.0a1
Issue ID
856637
Regression
No
Incorrect transform values after adding some force to an object which is colliding against immovable object
Steps to reproduce (or watch attached gif):
1. Open attached project
2. Open "module_test_scene" scene
3. Enter play mode
4. Select "Thruster" game object in the Hierarchy
4. Hold "Space" to add force to "Thruster" game object
5. Observe Inspector Transform position values
Result: transform values in inspector have changed even though the object in scene/game view is in the same position
6. Change position values to (0, 0, 0) - the object hasn't moved
Reproducible with: 5.4.0f3, 5.4.3p2, 5.5.0f2, 5.6.0a5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment