Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.3.3f1
2020.2
Issue ID
1223627
Regression
No
Awake is called in a different order when IProcessSceneWithReport.OnProcessScene() is called in the Editor and the Build
How to reproduce:
1. Open the attached project's Scene labeled "OnProcessSceneTest"
2. Enter the Play Mode
3. In the Console Window, inspect the order of the "Awake" and "OnProcessScene" callbacks
4. Build the project
5. Play the Build
6. Inspect the Player.log
Expected result: Player.log has the same order of callbacks logged
Actual result: Player.log has a different order of callbacks logged
Reproducible with: 2018.4.18f1, 2019.3.4f1, 2020.1.0a25, 2020.2.1.0a1
Couldn't test with: 2017.4.37f1 (IProcessSceneWithReport does not exist)
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
- Inconsistent ShaderGraph RGBA channels compared to the Inspector when "Alpha Is Transparency" is used
- Crash on "The GUID inside 'Assets/asset.png.meta' cannot be extracted by the YAML Parser." when opening the project
- Shadows disappear when looking at a certain angle in Scene view and using Cloud Shadows with Volumetric Clouds
- StackOverflowException freezes or silently crashes the Editor
- Microsoft Surface Device freezes when detaching and reattaching physical keyboard attachment to the device in Standalone Player for Windows
Resolution Note:
The ProcessScene callback has always been called after the scene is loaded. In the case of an editor build though, the call to Awake is blocked while in Playmode it is not blocked.