Differences

This shows you the differences between two versions of the page.

--- entities.scenes [2023/01/30 07:32] – uninomiconadmin
+++ entities.scenes [2025/01/15 04:35] (current) – external edit 127.0.0.1
@@ Line 6: / Line 6: @@
 SerializeUtility supports two modes for deserialization:
+  * Blocking (''DeserializeWorld'')
+  * Async (''BeginDeserializeWorld''/''EndDeserializeWorld'').
+But only a blocking mode for serialization (''SerializeWorld''). This is reasonable because it's edit-time functionality, and runs via a background [[scriptedimporter|ScriptedImporter]].(([[scriptedimporter|ScriptedImporters]] run on separate Worker processes due to 2020.1's "Parallel Import" feature.))
+==== Baking ====
+There are two types of baking:
+  - Full Rebakes
+  - Incremental Bakes (''EntityDiffer'') ((Incremental bakes rely on a diffing + patching system known as EntityDiffer. This adds EntityGuid components to your entities. This system is also used to patch in changes from the authoring scene while the game is running.))
-  * Blocking (''DeserializeWorld'')
+A full rebake is triggered when:
-  * Async (''BeginDeserializeWorld''/''EndDeserializeWorld'').
+  * A subscene is **opened**.
+  * An assembly containing Baker classes is modified. ((Important! Separate your bakers into separate classes if you want to avoid a full re-import of all baked scenes whenever you modify a gameplay assembly!))
+Incremental bakes are triggered when:
+  * Open subscenes are modified.
+==== Serialization ====
+Subscenes are serialized to the binary format in several spots:
+  - When closing an opened, dirty SubScene.
+  - After modifying an assembly with bakers, triggering a full rebake.
+  - When making a player build((Can be incremental)).
+Serialization uses a ''ScriptedImporter'' called ''SubSceneImporter''. This importer is injected into the AssetDatabase directly, rather than using the normal attribute. The subscene unity files (ie. my_subscene.unity) do not get imported by this importer, rather, it operates on an in-memory "asset" representing the baked scene.
+SubScene serialization can be debugged by placing breakpoints within SerializeUtility.SerializeWorld, and attaching to the Unity Import Worker process via the Rider "Attach to Unity Process..." dialogue.
 ==== SceneSectionStreamingSystem ====