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
- Assert error is thrown when the Editor language is set to one of the experimental ones in an HDRP project
- A BatchDrawCommand is using a pass from the shader “Universal Render Pipeline/Particles/Lit” that is not SRP Batcher compatible
- The Scene does not get rendered in the Player when MSAA is enabled and more than one Camera is used
- Crash on mono_object_get_class when generating Font Atlas of a specific font file
- GPU usage doubles when a project is running in the background
Add comment