What's Changed
This release adds new functionality to the analyze command, buiding on top of the AssetBundle schema cleanup that landed in v2.0.0.
The main focus is introducing support for the new Unity 6.6 "content directory" build system. To analyze these builds properly the ContentLayout.json file should be read at the same time. For convenience a --build-history argument can be used to help match the correct layout file with the content directory build that is being analyzed. The ContentLayout.json is converted into equivalent database tables, and also used to resolve references in the actual built content.
Also, to better "expose" missing content or incomplete information, there is now a "dangling_refs" table. It is expected that references to the "unity default resources" are reported here.
Error handling to analyze is improved, instead of obscure or hidden SQL errors there will be a clear error if more than one serialized file with the same name is encounted.
There are also significantly more documentation explaining the content inside Player and Content Directory builds, and improvements to the AssetBundle documentation.
PRs
For details see the individual PRs that landed:
- Document AssetBundle dependency references by @Abhinav-0311 in #91
- [#92] Add Player build and content directory format documentation by @SkowronskiAndrew in #95
- [#85] Track dangling references in analyze by @SkowronskiAndrew in #96
- [#97] Add Unity scenes to LeadingEdge reference builds by @SkowronskiAndrew in #98
- [#99] Import ContentLayout.json into the analyze database by @SkowronskiAndrew in #101
- [#99] Resolve ContentDirectory references via ContentLayout.json and validate analyze inputs by @SkowronskiAndrew in #102
- [#99] Create build report schema on demand; view rename and Content Directory docs by @SkowronskiAndrew in #103
- [#51] Clear error for duplicate SerializedFile/archive names by @SkowronskiAndrew in #104
- Match SerializedFile names case-sensitively by @SkowronskiAndrew in #106
- [#99] Resolve ContentDirectory references when content files lack the .cf extension by @SkowronskiAndrew in #105
- [#99] Add --build-history option to analyze by @SkowronskiAndrew in #109
Schema differences
Minor changes is case sensitivity and enforcing uniqueness for archive file names.
New "content_layout_*" tables are added.
New Contributors
- @Abhinav-0311 made their first contribution in #91
Full Changelog: v2.0.0...v2.1.0
