René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"UnityDataTool analyze - fix error when analyzing Unity 6.6 ContentDirectory output","articleBody":"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)\n\nexample observed with a test build: `UnityDataTool analyze -o out.db -p content0.archive .`\n\n```\nProcessing 0% (8/3111) 00e0ff1e38c784ed950a22f9d54e4d8e.cf\nError opening resource file 3d6fc680e3e1323a208ff45c769f794e\n```\nand many other \"Error open resource file\" errors are logged\n\nThe file on disk is actually  3d6fc680e3e1323a208ff45c769f794e.resS\n\nThe reference looks like this:\n\n```\nm_StreamData (StreamingInfo)\n    offset (UInt64) 0\n    size (unsigned int) 10944\n    path (string) cah:/3d6fc680e3e1323a208ff45c769f794e\n```\n\nThis does not happen when the \"-s\" argument is specified, which currently also turns of CRC checking.\nSo 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.\nThis only applies to the new build output.","author":{"url":"https://github.com/SkowronskiAndrew","@type":"Person","name":"SkowronskiAndrew"},"datePublished":"2026-05-15T17:34:47.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/70/UnityDataTools/issues/70"}