Search Issue Tracker
Fixed
Votes
0
Found in
2018.4
2018.4.16f1
2019.3
Issue ID
1220916
Regression
No
EventSystem's ExecutionOrder is 0 instead of -1000 when opening a project without the Library folder
How to reproduce:
1. Open the user's attached project 'Bug-EventSystem-ExecutionOrder-2018.zip'
2. Observe the console
Expected result: Debug message "EventSystem (MonoScript) execution order: -1000 - OK" appears
Actual result: Debug message "!!! ERROR: EventSystem (MonoScript) execution order: 0 (current) != -1000 (required) !!!" appears
Reproducible with: 2018.4.17f1, 2019.3.0b8
Not reproducible with: 2019.3.2f1, 2020.1.0a23
Notes:
- Since this is only affecting when opening a project without the Library folder, the next time a project opens the problem will disappear
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:
Seems to be fixed at some point before the 2019.3 release.