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
- 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
Resolution Note (2019.3.X):
The execution order of MonoBehaviour methods is undefined unless "Script Execution Order" in "Project Settings" is used.