Search Issue Tracker
By Design
Votes
6
Found in
2017.4.0f1
2018.4.0f1
2019.1.0a1
2019.1.1f1
2019.2.0a1
2019.3.0a1
Issue ID
1155430
Regression
No
After creating a new script the default script execution order remains incorrect until Unity is reopened or Standalone is built
How to reproduce:
1. Open attached project "CallOrderBug.zip" and scene "SampleScene"
2. Duplicate "CallOrderTestB4" and rename it to "CallOrderTestZ1" script (or create a new script)
3. Attach the script to any object and add "Canvas" -> "Text" as a reference
4. Enter Play mode
5. Observe scripts' start execution orders in Game View canvas (the execution order is already incorrect)
6. Exit Play mode
7. Build and Run the game
8. Observe script execution order in Standalone (the execution order is correct)
Expected result: the script execution order is the same
Actual result: script execution order has changed
Reproducible with: 2017.4.27f1, 2018.4.1f1, 2019.1.4f1, 2019.2.0b4, 2019.3.0a3
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note (2019.3.X):
The execution order of MonoBehaviour methods is undefined unless "Script Execution Order" in "Project Settings" is used.