What's Changed
Performance and CRC correctness
#70 includes a significant performance fix related to the calculation of CRCs. There are also correctness fixes for the CRC calculation. However investigation discovered another existing flaw with CRC that could be relevant when comparing objects between different analyze databases, That will require its own separate fix, tracked in #74 .
Usability improvements
- Improve dump command: add --stdout, refactors, more tests by @SkowronskiAndrew in #69
- [#49] Improve analyze file specification, CLI help and docs improvements by @SkowronskiAndrew in #76
- [#77] Detect missing TypeTrees up front in analyze and dump by @SkowronskiAndrew in #78
The support for "--stdout" makes it easier to use the dump command interactively and for piping in scripts.
The new support for file and path specification for analyze makes it easier to analyze individual files, and to analyze Build Report files along with the build output.
Initial support for content directory builds
New type being introduced in Unity 6.6. More support will come in follow up releases.
- [#70] Fix analyze CRC for cah:/ ContentDirectory resources; add --skip-crc by @SkowronskiAndrew in #73
- Document ContentLayout.json and publish its schema by @SkowronskiAndrew in #75
Documentation improvement
- Docs: Addressables local→remote dependency example by @timt-unity3d in #67
- Also doc improvements included in #77
Compatibility
These changes should be pretty backward compatible for existing scripts and tools based on past version of UnityDataTool.
However the fixes for CRC included in #70 can mean that the calculated CRC values for objects will now be different from the value calculated on the same objects in the older version of UnityDataTool.
Full Changelog: v1.3.4...v1.3.5
