Open Matthew-Beckett opened 2 years ago
@Matthew-Beckett, thanks for the report! I'll try to investigate this today.
In the meantime, maybe you'll be able to answer a few questions to direct me:
@Matthew-Beckett, thanks for the report! I'll try to investigate this today.
In the meantime, maybe you'll be able to answer a few questions to direct me:
- What Unreal version are you creating these assets with?
4.26
- Does the issue reproduce on other OSes than Linux?
I will try this on Windows and report back.
- Are you able to share an asset that reproduces this issue?
Will look to cleanse an asset of sensitive information to be able to do this but cannot promise.
Ok! GitHub runs some uasset
tests against 4.26 assets on Linux as part of the CI, so it should be a supported case. Does cargo test
work for you?
Ok! GitHub runs some
uasset
tests against 4.26 assets on Linux as part of the CI, so it should be a supported case. Doescargo test
work for you?
Yes, cargo test
passes all cases successfully. I will look into providing an example uasset file which is not working.
I will look into providing an example uasset file which is not working.
Thanks, if it's easier to share it privately than publicly, you can email me at jorgen@tjer.no.
Hi Jørgen,
I have now tested this on Windows and I can dump the files successfully with no issues, so I am not sure what's happening there, definitely needs further investigation.
On another note, can you provide some information on the kind of information stored in a dump
, I've tried to identify what some of the key-value pairs are by making changes and diff'ing dumps, however, I am still struggling.
It may be helpful to advise my objective, I am trying to diff the changes made in a blueprint and hopefully generate an output of changes. Hope you can help shine some light on what exactly is included in the dump output!
Thanks for your help and swift replies! Matt ❤️
I have now tested this on Windows and I can dump the files successfully with no issues, so I am not sure what's happening there, definitely needs further investigation.
Okay, in that case it'd be helpful to see a reproducing asset to help me track down what's going on on Linux.
On another note, can you provide some information on the kind of information stored in a
dump
, I've tried to identify what some of the key-value pairs are by making changes and diff'ing dumps, however, I am still struggling.
So far, uasset-rs
has mostly focused on the shared header information common to all assets, which means that it's mostly about engine versions, imports & exports (i.e. dependency graphs), etc. My first goal with it was to be able to reason about dependencies to help ensure that people don't miss certain assets during check-in, reason about which assets need to be cooked, etc.
It may be helpful to advise my objective, I am trying to diff the changes made in a blueprint and hopefully generate an output of changes. Hope you can help shine some light on what exactly is included in the dump output!
I definitely can understand this motivation, and I'd be interested in investigating some more in-depth parsing of blueprints specifically, i.e. trying to dig into the specifics of the blueprint graph etc, though that would require some consistent time focusing on it, and I'm not sure when I'll be able to pursue that particular goal. I'd be happy to support you if that was something you'd like to expand upon, but I don't know that it's something I'll be able to implement in the foreseeable future.
@Matthew-Beckett Were you able to figure out what about the asset made it crash on Linux? The specific issue should only occur if the "magic bytes" at the start of the file aren't valid, which might mean there's some kind of endianness issue or file corruption. Was it an x86 CPU or some other architecture?
Hi,
I am attempting to dump an assortment of UAsset files as I've tried numerous Blueprints both data-only and normal blueprints however when using the
commandline-tool
I am unable tolist-imports
ordump
without a panic.Full stack trace can be found below:
I have installed version 3.0 via cargo and am on full patched Manjaro Linux.