Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0a1
2018.3.0a1
2018.3.9f1
2019.1.0a1
2019.2.0a1
Issue ID
1139140
Regression
No
Collider bounds are not updated after moving attached GameObject
Steps to reproduce:
1. Open original project "Test.zip"
2. Enter Play Mode, pause after a couple of seconds
3. Observe console
Expected result: currentTransform.position and currentCollider.bounds should be calculated in the same Update
Actual result: currentTransform.position and currentCollider.bounds are not calculated in the same Update
Reproduced in: 2017.4.24f1, 2018.3.10f1, 2019.1.0b8, 2019.2.0a9
Note: Also happens with FixedUpdate
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- A frame spike occurs when Physics Simulation Mode is switched from Script to FixedUpdate
Resolution Note (2019.2.X):
This project has 'auto sync transforms' OFF in the physics settings. In that mode, the user is responsible for syncing in-between simulation.