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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note:
There are no guarantees that Awake and Start will be called in the same.