Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.1.0a1
2019.2.0a1
2019.2.0b4
2019.3.0a1
Issue ID
1160641
Regression
No
Awake and Start are called not on the same frame when entering Play Mode
How to reproduce:
1. Open attached project "AwakeStartScene.zip"
2. Open "To" scene
3. Enter Play Mode
4. Observe Console
Expected result: Awake and Start are called on the same frame
Actual result: Awake and Start and called 1 frame apart as Console indicates
Reproducible with - 2017.4.26f1, 2018.4.3f1, 2019.1.8f1, 2019.2.0b7, 2019.3.0a6
Notes:
Awake and Start are called in the same frame when changing the scene while already in Play Mode
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
There are no guarantees that Awake and Start will be called in the same.