Gildor's Forums

Author Topic: [Switch] Ninjala  (Read 1834 times)
titriclahu
Newbie
*
Posts: 3


View Profile
Re: [Switch] Ninjala
« Reply #15 on: November 08, 2021, 13:28 »

Versions above 1.0 (Tested 5.3 and 7.0) fail to load most meshes and textures with the following error message:
Code:
ERROR: zlib uncompress(2433,6211) returned -3
appDecompress: CompSize=2433 UncompSize=6211 Flags=0x1 Bytes=C05C <- SerializeCompressed <- FPakFile::Serialize: file=/Game/Asset/Common/Character/Avatar/Meshes/Body/Msh_Chr_Pl00010000_Body_Sk.uasset <- CopyStream <- SaveFile: /Game/Asset/Common/Character/Avatar/Meshes/Body/Msh_Chr_Pl00010000_Body_Sk.uasset <- SavePackages <- UIPackageDialog::SavePackages <- UIMenuItem::HandleCommand <- UIMenu::Popup <- UIMulticolumnListbox::HandleCommand <- UIBaseDialog::WndProc <- UIBaseDialog::CustomMessageLoop <- UIBaseDialog::ShowDialog: modal=1, title="Choose a package to open" <- CUmodelApp::ShowPackageUI <- Main: umodel_build=1576
Logged
spiritovod
Global Moderator
Hero Member
*****
Posts: 1929


View Profile
Re: [Switch] Ninjala
« Reply #16 on: November 08, 2021, 16:42 »

@titriclahu: It's hard to tell anything without some samples - at least try newest umodel build (version 1576 or above) and different engine versions. If it will not work, provide some sample paks here or via PM (since you can't extract problematic assets as-is due to the error).
Logged
titriclahu
Newbie
*
Posts: 3


View Profile
Re: [Switch] Ninjala
« Reply #17 on: November 08, 2021, 18:07 »

@titriclahu: It's hard to tell anything without some samples - at least try newest umodel build (version 1576 or above) and different engine versions. If it will not work, provide some sample paks here or via PM (since you can't extract problematic assets as-is due to the error).
Already using uModel 1576 on Engine version 4.24, tried loading the offending assets in isolation (All other object types disabled) with Engine versions 4.23, 4.25, 4.26 and 4.27.
PMing a sample pak.
Examples of offending assets are:
Code:
/Game/Asset/Common/Character/Avatar/Meshes/Body/Msh_Chr_Pl00010000_Body_Sk.uasset
/Game/Asset/Common/Character/Avatar/Textures/Cloth/T_Chr_Pl00010000_Cloth_Bas.uasset
/Game/Asset/Collaboration_HIME/Character/Avatar/Meshes/Body/Msh_Chr_Pl00090001_Body_Sk.uasset
Logged
spiritovod
Global Moderator
Hero Member
*****
Posts: 1929


View Profile
Re: [Switch] Ninjala
« Reply #18 on: November 09, 2021, 00:34 »

@titriclahu: Thanks for the sample. It looks like a problem with extracting pak from romfs. I'm not quite familiar with NSW stuff, but files from base package and patches are being merged in certain cases and the provided pak looks like a corrupted result of such merging. At least some entries doesn't make any sense both encryption-wise and package format-wise, compared to the rest of entries.
Logged
titriclahu
Newbie
*
Posts: 3


View Profile
Re: [Switch] Ninjala
« Reply #19 on: November 12, 2021, 10:36 »

@titriclahu: Thanks for the sample. It looks like a problem with extracting pak from romfs. I'm not quite familiar with NSW stuff, but files from base package and patches are being merged in certain cases and the provided pak looks like a corrupted result of such merging. At least some entries doesn't make any sense both encryption-wise and package format-wise, compared to the rest of entries.
That's strange, the working v0 romfs dump was made the same way as the v13 one with the appropriate hactool flags and keys.
Considering there's files that only exist in the update data that do and don't load in uModel (Meshes from the collaboration_ folders except the ones in the Body folder, as long as they're being loaded with Texture autoloading disabled) would indicate that some files were packed differently, for some reason.
Logged
spiritovod
Global Moderator
Hero Member
*****
Posts: 1929


View Profile
Re: [Switch] Ninjala
« Reply #20 on: November 12, 2021, 16:41 »

...that some files were packed differently, for some reason.
It's not possible. UE4 file system is not so complex for being able to handle separate entries differently within a single package (especially to that extent) - and in case if you're customizing format or adding custom encryption/obfuscation, those changes will be applied to all entries in the same way. Currently "broken" entries are addressing offsets in the middle of totally encrypted non-UE4 chunks, which can be only caused by external merging - like when you're applying an xdelta patch or something like that. I can't help you with that, so it's better to ask in related NSW communities for possible solution.
Logged
Jump to:  

Powered by SMF | SMF © 2006-2009, Simple Machines LLC
Leviathan design by Bloc | XHTML | CSS