To decompress LZ4 I have imported a subset of lz4-java, the native Java known-decompressed-size version. Might be worth considering whether to stick to a single set of structures or separate out new UnityFS classes? I haven’t implemented packing, and I don’t have examples to test all code paths here.įor now I have shoe-horned the data into the existing structures, except I've added a new BundleInfoEntryFS since they are serialised differently.there’s lots of new data I don't yet understand – not all stored and output on ‘info’ – and some old fields no longer populated.the data header is compressed with another scheme, LZ4.most lengths and offsets are now 64-bit.I don’t think this is really good enough to include as-is, but it appears to works and there's some design decisions needed that you should probably make on how to capture / structure the data and how to support LZ4. Requires a bundle property file.Īs a first step towards issue #172. List object identifiers (Unity 5 and higher only).ĭisplay embedded runtime type information. Could be useful for manual extraction.ĭisplay some information from the file header. Available commands (v0.5) Asset commands Command In case the launch script fails, try java -jar disunity.jar. Note: depending on the platform, you may need to run disunity.bat (Windows) or disunity.sh (Linux/MacOS). Right now, it only supports raw file reading and writing without any object deserialization, therefore it also can't extract any asset data directly. A note about the versionsĠ.3 works best with Unity 3.x and has most of the original extraction features.Ġ.4 is a somewhat incomplete and untested upgrade to support Unity 4 and 5 and has some of the extraction features of 0.3.Ġ.5 is a code rewrite to properly support all Unity games from 2 to 5 that also comes with unit tests.
The latest build can be found on the releases page. An experimental command-line toolset for Unity asset and asset bundle files written in Java, mostly designed for extraction.
0 kommentar(er)
