Differences

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

--- entities.scenes [2023/01/30 07:24]
uninomiconadmin created
+++ entities.scenes [2023/06/24 03:39]
97.126.63.199
@@ Line 3: / Line 3: @@
 ==== SerializeUtility ====
-SerializeUtility is responsible for writing entire Worlds to disk. It is written specifically for serializing Subscene Sections to disk in the editor, and then for streaming them in efficiently during runtime. It can support other use cases, but it is not designed to.
+SerializeUtility is responsible for writing entire Worlds to disk. It is written specifically for serializing Subscene Sections to disk in the editor, and then for streaming((see SceneSectionStreamingSystem)) them in efficiently during runtime. It can support other use cases, but it is not designed to.
+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.))
+==== Serialization ====
+==== SceneSectionStreamingSystem ====
+==== AsyncLoadSceneOperation ====
+These systems stream Sections of entities scenes((subscenes)) into a World. It's intended for use at runtime, but will also be used in the editor when Entity Subscenes are "Closed for Edit" in the Hierarchy.
+The AsyncLoadSceneOperation and associated jobs use the Async Mode of SerializeUtility (see above).

Uninomicon

User Tools

Site Tools

Differences

Page Tools