Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2019.1.X
Votes
4
Found in
2017.3.1p4
Issue ID
1036602
Regression
No
ScriptExecutionOrder ignored when reloading scripts during playmode
To Reproduce:
- Open repro.unity scene
- Press play
- Reimport a script from project view
- observe Console output
ClassA,ClassB and ClassC have ScriptExecutionOrder defined.
On Playmode:
OnEnable ClassA Obj[x]
OnEnable ClassA Obj[y]
OnEnable ClassA Obj[z]
OnEnable ClassB Obj[x]
OnEnable ClassB Obj[y]
OnEnable ClassB Obj[z]
OnEnable ClassC Obj[x]
OnEnable ClassC Obj[y]
OnEnable ClassC Obj[z]
After reimport, classes do not execute in order shown in ScriptExecution order, or even one type after another, an example:
OnEnable ClassB Obj3
OnEnable ClassA Obj3
OnEnable ClassA Obj1
OnEnable ClassC Obj3
OnEnable ClassC Obj2
OnEnable ClassB Obj1
OnEnable ClassC Obj1
OnEnable ClassB Obj2
OnEnable ClassA Obj2
Expect to see OnEnabled called in the same type order as entering playmode for classes with discrete ScriptExecutionOrder.
Reproducible: 2018.3.0a1, 2018.2.0b13, 2018.1.0f2, 2017.1.1p3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment