-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
struct.error: unpack requires a buffer of 3714449519 bytes #92
Comments
I can reproduce using only the
|
Seeing the same in another Unity project. It appears that although the asset metadata is parsed correctly, the type/tree information and/or the actual object reading function is not functioning correctly, and the actual data of the object is not correctly understood. Haven't discovered the root cause yet, but I'm looking into it (very slowly). If anyone wants to get in touch to debug and discuss improvements, I'd love to get in touch so we can make some improvements to unitypack. |
I don't have knowledge of how Unity assets or unitypack works, but I'm willing to help debug if there is anything I can do |
Looks like this is probably the result of #8. In my case, I'm looking at format=17 objects, but the "built in" structure definitions that unitypack ships with appears to be format=15; and there are some discrepancies that cause issues. Appears to be a known thing. Unfortunately, my knowledge of Unity is kind of minimal, I just like to tinker with RE'ing formats. I'm not sure what a "good" solution here would look like, but I'm like 99% sure that any trace people are seeing that results from object.py read() can probably be fixed by focusing on #8. |
Good to know :) |
This looks solved now. So either one of the recent commits fixed it, or the last Hearthstone update did |
When running unityextract with
./bin/unityextract --audio -o out/audio2 /d/Games/Hearthstone/Data/Win/*.unity3d
, I have the following stack trace:This looked similar to #23, and I tried to re-clone unitypack and reinstall from scratch, but the issue still persists.
Do you have any idea how to fix this?
The text was updated successfully, but these errors were encountered: