Uninomicon

You've loaded an old revision of the document! If you save it, you will create a new version with this data.

#SceneManager

Notes:

`SceneManager.sceneLoaded` is called *after* the loaded Scene Awakes.
Scene Loading always happens at the start of the Update loop, within the `EarlyUpdate` phase of the PlayerLoop.

The Unity scene flushing pipeline works differently in the initialization phase of the player.
Scene loads thats are queued during initialization are blocked and fully loaded before the game starts.
For example, if SceneManager.LoadSceneAsync is called in the Awake of the very first scene (ie. called before the first Update), then the engine will wait to fully load that scene as well, before starting the first Update.

It is untested if this is also the case for SceneManager.UnloadSceneAsync. However, because Unity documentation mentions that that the scene 
loading queue is a pipeline, and only one AsyncOperation can progress at a time, I would suspect that the Engine simply "flushes" the scene loading queue
during initialization.

Phases:
- Initialization (Scene Loading happens here)
- Game Loop
 - Early Update
   - `UpdatePreloading` (Scene Loading happens here)
 - Update

(The scene load pipeline is fully flushed) I don't yet know how it handles unloads if they are in
the pipeline then, so if we need this behaviour we should debug and see how it works.
If scene unloads get flushed too, we'll need to add a bit of logic for it, in the same way LoadSceneAsync
does.

# Header
Notes [link](google.com)

Please fill all the letters into the box to prove you're human. F X U R W Please keep this field empty:

Edit summary

Uninomicon

User Tools

Site Tools

Page Tools