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
- Unstable lighting when additional light sources are added in Shader Graph nodes
- AnalyticsSessionInfo.sessionFirstRun value is not affected when the corresponding data file is removed
- Branch Rotation can't be undone
- "Rotate Branch" is too sensitive to mouse movement
- Renders "Add" button has no OnHover action
Add comment