Uninomicon

Documenting the dark corners of the Unity Engine.

User Tools

Site Tools

Trace:
entities.scenes

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
entities.scenes [2023/01/30 07:31] – uninomiconadminentities.scenes [2023/06/24 03:39] – 97.126.63.199
Line 5: Line 5:
 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 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:  +SerializeUtility supports two modes for deserialization: 
- * Blocking (''DeserializeWorld'') +  * Blocking (''DeserializeWorld'') 
- * Async (''BeginDeserializeWorld''/''EndDeserializeWorld'').+  * 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 ==== ==== SceneSectionStreamingSystem ====
entities.scenes.txt · Last modified: 2025/01/15 04:35 by 127.0.0.1
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki