You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Documentation/analyze-examples.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -214,6 +214,10 @@ object_id type name pretty_size crc32
214
214
3866367853307903194 Sprite red 460.0 B 1811343945
215
215
```
216
216
217
+
## Example: Finding differences between two builds
218
+
219
+
This is a large subject, see [Comparing Builds](comparing-builds.md).
220
+
217
221
## Example: Matching content back to the source asset
218
222
219
223
UnityDataTool works on the output of a Unity build, which, by its very nature, only contains the crucial data needed to efficiently load built content in the Player. So it does not include any information about the assets and scenes in the project that was used to create that build. However you may want to match content back to the original source asset or scene. For example if the size of an AssetBundle has unexpectedly changed between builds then you may want to track down which source assets could be responsible for that change. Or you may want to confirm that some particular image has been included in the build.
0 commit comments