Search Issue Tracker
Fixed in 2018.2
Votes
5
Found in
5.6.0f3
Issue ID
898537
Regression
No
[iOS] Awake-Start order is different when loading multiple scenes
Reproduction steps:
1. Open the attached "Str" project.
2. Build and run it for iOS.
- Two scenes are combined, first scene loads a second scene additively in Awake.
- Order of calls is printed.
Actual result:
- Scene 1 awake
- Scene 1 start
- Scene 2 awake
- Scene 2 start
Expected result:
- Scene 1 awake
- Scene 2 awake
- Scene 1 start
- Scene 2 start
Not reproducible with:
Android(Mono2x, IL2CPP), OSX Standalone, Editor
Reproduced with:
iPad Air 8.1.1
5.5.3p1, 5.6.0f3, 2017.1.0b1
Mono2x, IL2CPP
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
- LineRenderer points lists suffers from performance issues when list is large
- Shaders take a lot of memory at runtime even when only one variant is used
- Lego Microgame crashes the Linux Editor at "ScanFilter::Merge" when selecting a WebGL build location
- GameObject reference is null when creating it inside Reset() function and assigning Script as component
- GameObject/Prefab inspector preview is slow for complex hierarchies
gtzpower
Feb 13, 2018 15:12
This seems to be a problem in 2017.3.0 as well. Even in the editor with 2 scenes opened, it seems like awake is called in order of scenes being loaded into the editor, even though execution order defines a specific order.
IgorAherne
Dec 15, 2017 02:31
In fact, Expected result never happens - even on standalone.
When both scenes are loaded (we wait for async operations to complete, then activate them), the "Actual result" happens both on standalone and on iOS
IgorAherne
Dec 15, 2017 01:38
Reproduced in 2017.2.0f3, iOS Metal emulation, IL2CPP .Net 4.6
IgorAherne
Dec 15, 2017 01:36
what the f!!