Search Issue Tracker
Fixed in 2018.2.3f1
Votes
2
Found in
2018.1.5f1
2018.2.2f1
Issue ID
1069066
Regression
Yes
Collider bounds are not calculated correctly if the transform parent is updated after the object is created
Reproduction steps:
1. Open the attached project "Bounds.zip";
2. Open the SampleScene;
3. Enter a play mode;
4. Observe the results in the console.
Expected results: there should be two lines printed in the console and both of them should be the same.
Actual results: correct results are displayed only after transform parent is updated (in the second line).
Reproduced on: 2018.1.5f1, 2018.1.9f1, 2018.2.2f1, 2018.3.0a2.
Not reproduced on: 2017.4.9f1, 2018.1.4f1, 2018.2.3f1, 2018.3.a03.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment