Skip to content

Commit a9d8e02

Browse files
Add mention of the new typetree extraction feature in unity-content-format.md
1 parent fdbb7d5 commit a9d8e02

1 file changed

Lines changed: 8 additions & 0 deletions

File tree

Documentation/unity-content-format.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -88,6 +88,14 @@ Player built content, unless the Player was built with TypeTrees enabled.
8888
>[!TIP]
8989
>The `binary2text` tool supports an optional argument `-typeinfo` to enable dumping out the TypeTrees in a SerializedFile header. That is a useful way to learn more about TypeTrees and to see exactly how Unity data is represented in the binary format.
9090
91+
#### Extracted Typetrees
92+
93+
Starting with Unity 6.5 and Addressables 2.9 it is possible to extract the TypeTrees from all the SerializedFiles in an Addressable build into a shared file. This can reduce the size of the build output, because the TypeTree information is no longer duplicated in each file.
94+
95+
For details see [Addressable AssetBundle memory considerations](https://docs.unity3d.com/Packages/com.unity.addressables@2.9/manual/memory-assetbundles.html)
96+
97+
UnityDataTools commands that open serialized files using the UnityFileSystem API require access to the TypeTrees. For example `dump` and `analyze`. Use the `--typetree-data` option to specify the `.typetreedata` file when examining a build that has extracted TypeTrees.
98+
9199
### Platform details for using UnityDataTool with Player Data
92100

93101
The output structure and file formats for a Unity Player build are quite platform specific.

0 commit comments

Comments
 (0)