Search Issue Tracker
By Design
Votes
1
Found in
5.3.4f1
Issue ID
788752
Regression
No
OnTriggerEnter called before Start
Steps to reproduce:
1. Download and open attached project "New Unity Project.zip"
2. Open scene "scene1" and play it
3. Press "y" on keyboard
Object gets created and immediately disabled. After pressing "y" it gets enabled and messages printed on each stage of its life cycle
Expected result: Messages appear in expected order:
"Parent Started"
"Start!!"
"OnTriggerEnter"
Actual result: Messages appear in wrong order, indicating that execution order of events is not respected - OnTriggerEnter called before Start:
"OnTriggerEnter"
"ParentStarted"
"Start!!"
Tested and reproduced on:
Windows 10
Unity 5.1.4f1, 5.2.4p1, 5.3.4p3, 5.4.0b15
Comments (1)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
jethrogillgren
Apr 11, 2018 19:12
If this isn't actually a bug, can the diagram/documentation be updated to include it please?
https://docs.unity3d.com/Manual/ExecutionOrder.html
The diagram there shows Start() before any of the OnXXX functions.