Closed PwaDesu closed 1 year ago
I unpacked the whole WarThunder/cache/binary.2.21.1
ver 2.21.1.30 tree using the v0.2.2.10 build and got no error.
Looks like a mismatch in the name map for the file. Please provide a sample of the data that is causing the error.
I am not unpacking the .vromfs in the cache directory as those are not the latest, I unpack those directly in the WarThunder
directory. In this case, it was trying to unpack blks from the newly created aces.vromfs.bin_u
folder.
I just tried redoing the same process, but targeting the cache directory instead, and that just completed without errors. I take it the aces.vromfs.bin in the normal directory somehow is slightly different than the one in the cache directory, and thus some of the files it extracted out of it got corrupted? Here's the vromfs I had extracted and was trying to unpack the .blk
's of. It's the most up to date one, the one in my cache directory is still on yesterday's patch.
aces.vromfs.zip
I again failed to reproduce the error.
sha1sum aces.vromfs.bin
7108f1c1730991f2e783ec177ab9bf13561d2fdd aces.vromfs.bin
python -m wt_tools.vromfs_unpacker aces.vromfs.bin
Unpacking files [####################################] 100%
[OK] /tmp/dds/aces.vromfs.bin => /tmp/dds/aces.vromfs.bin_u
python -m wt_tools.blk_unpack_ng --format=strict_blk aces.vromfs.bin_u/ > aces.log
grep -Hn Error aces.log
Right, I'm very sorry for wasting your time, the reason unpacking the cache directory worked was that I had never unpacked it before, so all of the files were from this update and this update only. I had unpacked the main directory many times before however and kept unpacking into the same folders, so I assume there were leftover, now deleted files from previous updates and those were the ones causing the error because they didn't come from the current .vromfs
I deleted the folders in order to unpack into clean, brand-new folders, and it worked as expected
I think this started happening after the latest Fire & Ice WT update, it was working as intended before. The .vromfs unpacked do work. It doesn't immediately fail as soon as
blk_unpack_ng
starts, it seems to be working fine until after a dozen or so of seconds it encounters a hurdle and this happens.