unable to read the bundle file invalid file or unknown version что делать
Decompression of 2018.4.4 file fails «Unable to decompress the bundle file!» #299
Comments
neobenedict commented Sep 18, 2019 •
Decompression of a unity 2018.4.4f1 file fails with the not so helpful error message «Unable to decompress the bundle file!».
This file can be decompressed and extracted just fine in other unity tools like AssetStudio and uTinyRipper, but I need the repacking functionality of UABE.
Please fix, thank you.
The text was updated successfully, but these errors were encountered:
nesrak1 commented Sep 18, 2019
Not sure why UABE isn’t able to extract it but if all you need is an uncompressed bundle to open in UABE, this should do it:
broken.unity3d.unpacked.zip
neobenedict commented Sep 18, 2019
Not sure why UABE isn’t able to extract it but if all you need is an uncompressed bundle to open in UABE, this should do it:
broken.unity3d.unpacked.zip
Thanks, what tool did you use to do this?
nesrak1 commented Sep 18, 2019
The c# version of uabe here https://github.com/nesrak1/AssetsTools.NET. I’m not working on it anymore though.
neobenedict commented Sep 19, 2019
Hmm, thanks
Unfortunately I can’t seem to repack it properly in UABE, the game keeps crashing. Is the decompression/unpacking symmetric, do you know? Can I code something to ensure the file is put back together in the same format?
nesrak1 commented Sep 19, 2019
As far as I know, the game shouldn’t be able to be able to detect compression, but it might be able to hash the file. If it opens fine in other tools, most likely it’s that and you’d have to look in the game code. If it doesn’t open in other tools, uabe may have corrupted the bundle or something.
neobenedict commented Sep 19, 2019
OK, it errors out in uTinyRipper with Import: System.Exception: Read 140 but expected 91, so UABE is corrupting the file.
nesrak1 commented Sep 19, 2019
If you can send the bundle, I can try to debug it
neobenedict commented Sep 19, 2019 •
If you can send the bundle, I can try to debug it
Here’s a working bundle:
If you simply open and resave the file with UABE, some bits in the header change and the game crashes trying to parse it.
If I manually edit the file in a text editor (I’m just changing those base 64’d strings) the patch is applied to the game fine, but I have to have the same length exactly I think. Will test.
Basically I’m just looking for a way to change those b64’d strings with another b64’d string of variable length.
nesrak1 commented Sep 19, 2019 •
When I opened both working and broken in UABE and saved (no changes), the files contents didn’t change for me at all. They seem to be the same before and after saving.
On the other hand, both working and broken won’t open in utinyripper but I think it might be a bug where it won’t correctly read non-compressed bundles. It tries to compare the length of the whole header to decompressed size which is wrong (at least it is to uabe). With the lengths changed, the files open in utr now but won’t open in either uabe.
neobenedict commented Sep 19, 2019
When I opened both working and broken in UABE and saved (no changes), the files contents didn’t change for me at all. They seem to be the same before and after saving.
On the other hand, both working and broken won’t open in utinyripper but I think it might be a bug where it won’t correctly read non-compressed bundles. It tries to compare the length of the whole header to decompressed size which is wrong (at least it is to uabe). With the lengths changed, the files open in utr now but won’t open in either uabe.
What version of UABE? There are some clear changes for me.
neobenedict commented Sep 19, 2019
OK, by some miracle, it’s working properly after saving.
The initial bug still remains though.
neobenedict commented Jan 13, 2020
I’m closing this as I wasn’t calling flush final block on the decryption so a bit of the end of the file was missing (and I never noticed because everything extracted fine), strange how other tools worked fine but this one didn’t, but it was a mistake on my end.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
РЕШЕНО | Ошибки при попытке построить проект в Unity, что делать?
(Я новичок в Unity)
(Версия юнити: 2020.3.5f1)
При попытке построить проект в Unity появляются следующие ошибки:
FAILURE: Build failed with an exception.
* Where:
Build file ‘C:\Users\Слава\Circle Game\Temp\gradleOut\launcher\build.gradle’ line: 3
* What went wrong:
A problem occurred evaluating project ‘:launcher’.
> Failed to apply plugin [id ‘com.android.internal.application’]
> Your project path contains non-ASCII characters. This will most likely cause the build to fail on Windows. Please move your project to a different directory. See b.android.com/95744 for details. This warning can be disabled by adding the line ‘android.overridePathCheck=true’ to gradle.properties file in the project directory.
BUILD FAILED in 13s
FAILURE: Build failed with an exception.
* Where:
Build file ‘C:\Users\Слава\Circle Game\Temp\gradleOut\launcher\build.gradle’ line: 3
* What went wrong:
A problem occurred evaluating project ‘:launcher’.
> Failed to apply plugin [id ‘com.android.internal.application’]
> Your project path contains non-ASCII characters. This will most likely cause the build to fail on Windows. Please move your project to a different directory. See b.android.com/95744 for details. This warning can be disabled by adding the line ‘android.overridePathCheck=true’ to gradle.properties file in the project directory.