Added support for specifying an extracted type tree data file (#60)

* Added support for specifying an extracted type tree data file for dump and analyze commands
* updated docs & tests
* updated UnityFileSystem dlls to 6000.5.0a8 - this version has the API needed to load extracted type tree files.
* Bump version to 1.3.3
* Add a few additional AssetBundle test files

Author: paulb-unity

Documentation/command-analyze.md

@@ -16,6 +16,7 @@ UnityDataTool analyze <path> [options]
 | `-s, --skip-references` | Skip CRC and reference extraction (faster, smaller DB) | `false` |
 | `-v, --verbose` | Show more information during analysis | `false` |
 | `--no-recurse` | Do not recurse into sub-directories | `false` |
+| `-d, --typetree-data <file>` | Load an external TypeTree data file before processing (Unity 6.5+) | — |
 
 ## Examples
 
@@ -90,7 +91,13 @@ System.ArgumentException: Invalid object id.
 
 This error occurs when SerializedFiles are built without TypeTrees. The command will skip these files and continue.
 
-**Solution:** Enable **ForceAlwaysWriteTypeTrees** in your Unity build settings. See [Unity Content Format](../../Documentation/unity-content-format.md) for details.
+**Solutions:**
+- Enable **ForceAlwaysWriteTypeTrees** in your Unity build settings. See [Unity Content Format](../../Documentation/unity-content-format.md) for details.
+- If your bundles were built with external TypeTree data (Unity 6.5+), use the `--typetree-data` option to load the TypeTree data file before analysis:
+
+```bash
+UnityDataTool analyze /path/to/bundles --typetree-data /path/to/typetree.bin
+```
 
 ### SQL Constraint Errors
 

Documentation/command-dump.md

@@ -15,6 +15,7 @@ UnityDataTool dump <path> [options]
 | `-f, --output-format <format>` | Output format | `text` |
 | `-s, --skip-large-arrays` | Skip dumping large arrays | `false` |
 | `-i, --objectid <id>` | Only dump object with this ID | All objects |
+| `-d, --typetree-data <file>` | Load an external TypeTree data file before processing (Unity 6.5+) | — |
 
 ## Examples
 
@@ -87,6 +88,14 @@ UnityDataTool serialized-file metadata /path/to/file
 
 The `TypeTree Definitions` field will show `No` when TypeTrees are absent.
 
+**External TypeTree data (Unity 6.5+):**
+
+If your bundles were built with TypeTree data extracted to a separate file, use the `--typetree-data` option to load it:
+
+```bash
+UnityDataTool dump /path/to/file.bundle --typetree-data /path/to/typetree.bin
+```
+
 ---
 
 ## Output Format

Documentation/command-serialized-file.md

@@ -305,8 +305,8 @@ Each element of `scriptTypes` in the JSON output contains:
 
 Notes:
 
-* For SerializedFiles inside AssetBundles the Unity Version is frequently stripped ("0.0.0").  See [BuildAssetBundleOptions.AssetBundleStripUnityVersion](https://docs.unity3d.com/ScriptReference/BuildAssetBundleOptions.AssetBundleStripUnityVersion.html).
-* For AssetBundles the version string may take the form "<version>\n<assetbundle-format-version>".  The assetbundle-format-version rarely changes, and is currently 2.
+* For SerializedFiles inside AssetBundles the Unity Version can be stripped, in which case the Unity Version value is "0.0.0".  See [BuildAssetBundleOptions.AssetBundleStripUnityVersion](https://docs.unity3d.com/ScriptReference/BuildAssetBundleOptions.AssetBundleStripUnityVersion.html).
+* For AssetBundles where the typetrees have been stripped out the version string takes the form `<unity-version>\n<assetbundle-format-version>`.  The assetbundle-format-version rarely changes, and is currently 2. Examples "6000.0.65f1\n2" and "0.0.0\n2".
 * The Unity Editor will attempt to load SerializedFiles regardless of the Platform.  But the Runtime will only load files built with the correct platform value.
 
 ---

Documentation/unity-content-format.md

@@ -88,6 +88,14 @@ Player built content, unless the Player was built with TypeTrees enabled.
 >[!TIP]
 >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.
 
+#### Extracted Typetrees
+
+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.
+
+For details see [Addressable AssetBundle memory considerations](https://docs.unity3d.com/Packages/com.unity.addressables@2.9/manual/memory-assetbundles.html)
+
+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.
+
 ### Platform details for using UnityDataTool with Player Data
 
 The output structure and file formats for a Unity Player build are quite platform specific.

Documentation/unitydatatool.md

@@ -41,6 +41,22 @@ Use `--help` with any command for details: `UnityDataTool analyze --help`
 
 Use `--version` to print the tool version.
 
+## External TypeTree Data
+
+Starting with Unity 6.5, asset bundles can be built with TypeTree data extracted into a separate file. When bundles are built this way, the TypeTree data file must be loaded before the bundles can be processed.
+
+The `--typetree-data` (`-d`) option is available on the [`analyze`](command-analyze.md) and [`dump`](command-dump.md) commands:
+
+```bash
+# Analyze bundles that use an external TypeTree data file
+UnityDataTool analyze /path/to/bundles --typetree-data /path/to/typetree.bin
+
+# Dump a bundle with external TypeTree data
+UnityDataTool dump /path/to/file.bundle -d /path/to/typetree.bin
+```
+
+> **Note:** This option requires a version of UnityFileSystemApi from Unity 6.5 or newer. Using it with an older version of the library will produce an error message.
+
 
 ## Installation
 

TestCommon/Data/AssetBundleTypeTreeVariations/AssetBundle-NoTypeTree/AssetBundle-NoTypeTree

@@ -0,0 +1,9 @@
+ManifestFileVersion: 0
+UnityVersion: 6000.0.65f1
+CRC: 2966982943
+HashAppended: 0
+AssetBundleManifest:
+  AssetBundleInfos:
+    Info_0:
+      Name: small.bundle
+      Dependencies: {}

TestCommon/Data/AssetBundleTypeTreeVariations/AssetBundle-NoTypeTree/AssetBundle-NoTypeTree.manifest

@@ -0,0 +1,23 @@
+ManifestFileVersion: 0
+UnityVersion: 6000.0.65f1
+CRC: 1950084276
+Hashes:
+  AssetFileHash:
+    serializedVersion: 2
+    Hash: 85d7a0628d93941ceb548a6dfa4daaa5
+  TypeTreeHash:
+    serializedVersion: 2
+    Hash: 8fe56aa230288d26e5aa9f8e595de7aa
+  IncrementalBuildHash:
+    serializedVersion: 2
+    Hash: 23708f44cf6b8ab8a9a6d6474bc8166a
+HashAppended: 0
+ClassTypes:
+- Class: 114
+  Script: {fileID: 11500000, guid: 1eb29b0714ed25b4b9acbb23c6791a75, type: 3}
+- Class: 115
+  Script: {instanceID: 0}
+SerializeReferenceClassIdentifiers: []
+Assets:
+- Assets/Assets/BasicScriptableObject.asset
+Dependencies: []