Skip to content

UnityDataTool analyze - fix error when analyzing Unity 6.6 ContentDirectory output #70

@SkowronskiAndrew

Description

@SkowronskiAndrew

The analyze feature is hitting errors when scanning output from the new ContentDirectory build feature being introduced in Unity 6.6 (still in alpha). It happens if the build contains textures (and probably also applies for Audio, Mesh, Video cases)

example observed with a test build: UnityDataTool analyze -o out.db -p content0.archive .

Processing 0% (8/3111) 00e0ff1e38c784ed950a22f9d54e4d8e.cf
Error opening resource file 3d6fc680e3e1323a208ff45c769f794e

and many other "Error open resource file" errors are logged

The file on disk is actually  3d6fc680e3e1323a208ff45c769f794e.resS

The reference looks like this:

m_StreamData (StreamingInfo)
    offset (UInt64) 0
    size (unsigned int) 10944
    path (string) cah:/3d6fc680e3e1323a208ff45c769f794e

This does not happen when the "-s" argument is specified, which currently also turns of CRC checking.
So i think the fix would be to recognize that "cah:/" file format and in that case simply use feed the path into the CRC calculation. E.g. that path is already containing the hash of the content so we don't need to actually access the .resS or .resource file at all.
This only applies to the new build output.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions