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
- “[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