Search Issue Tracker
Fixed
Votes
0
Found in
4.5.4f1
Issue ID
646039
Regression
No
OnDestroy order for Transform hierarchy inconsistent between editor and runtime
To reproduce:
1) Open attached project (there is one scene, called Untitled) and build standalone player (version tested: OSX)
2) Enter playmode, exit playmode. In editor console log you see:
[3] +OnDisable, null: False
[2] +OnDisable, null: False
[1] +OnDisable, null: False
[0] +OnDisable, null: False
[0] -OnDestroy, null: False
[1] -OnDestroy, null: False
[2] -OnDestroy, null: False
[3] -OnDestroy, null: False
3) Run standalone app. Press "Close App". In Player log you see
[3] +OnDisable, null: False
[3] -OnDestroy, null: False
[2] +OnDisable, null: False
[1] +OnDisable, null: False
[1] -OnDestroy, null: False
[2] -OnDestroy, null: False
[0] +OnDisable, null: False
[0] -OnDestroy, null: False
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