Gildor's Forums

English Forum => Unreal engine 4 => Topic started by: whiteknight on May 23, 2018, 03:11



Title: State of Decay 2
Post by: whiteknight on May 23, 2018, 03:11
Hi there,

Everything (animations, textures, sound, static) are working except for skeletal meshes. Might need a tweak in Umodel.

Here are some test skeletal meshes in .uasset with the issue.

Error print out:
SerializeBulkArray <- FSkeletalMeshVertexBuffer4<< <- FStaticLODModel4<< <- TArray::Serialize:0/3 <- USkeletalMesh4::Serialize <- LoadObject:SkeletalMesh4'MaleStandard.MaleStandard', pos=10F1F, ver=505/0 (unversioned), game=ue4.13 <- UObject::EndLoad <- CUmodelApp::ShowPackageUI <- Main:umodel_build=754

Dropbox: https://www.dropbox.com/s/ztxroi9qlmbwg07/SOD2.zip?dl=1

Thanks and if you need any other files just let me know.


Title: Re: State of Decay 2
Post by: Gildor on May 23, 2018, 03:31
Hi,
Typical user's mistake here is when only one UE4 version is being checked, and not tried any other version. I'd suggest you to try all versions which umodel will supply in "unreal engine 4 version" dialog window. May be you already tried, I don't know - you didn't tell anything except "it crashes with 4.13".


Title: Re: State of Decay 2
Post by: whiteknight on May 23, 2018, 04:15
Hi Gildor,

Sorry should have been more clear,

Yes I have already run through all the engine versions to check,the animations / static/ etc.... work with v4.13 however the skeletal meshes don’t seem to open with any version.

Hope that information helps.

Thanks


Title: Re: State of Decay 2
Post by: whiteknight on May 23, 2018, 14:58
Just an update- I have tried absolutely all combinations to get the Skeletal Meshes exporting - no version of unreal engine currently works with them.

It definitely needs a look at and to make a change in Umodel to support it.

Thanks  :)


Title: Re: State of Decay 2
Post by: Xplodin on June 01, 2018, 11:05
Would love support for this as i have the paks unpacked but cant open uasset.
Uses 13.2


Title: Re: State of Decay 2
Post by: charlesberg on June 04, 2018, 04:49
Any update on skeleton mesh support for this game?


Title: Re: State of Decay 2
Post by: Gildor on June 04, 2018, 11:48
If there would be updates, they'd be in this thread. No messages here - no updates.


Title: Re: State of Decay 2
Post by: Gildor on June 04, 2018, 13:34
Well, I've take a look at provided files. Added a quick fix to let those 2 skeletal meshes to load.

-game=sod2 or overriding to "State of Decay 2" is required.

As I said, I have only 2 sample meshes, so I can not guarantee that UModel will not crash with anything else. The game requires intense testing.


Title: Re: State of Decay 2
Post by: Juso3D on June 05, 2018, 18:37
Downloading now, will report tomorrow sometime :)


Title: Re: State of Decay 2
Post by: charlesberg on June 06, 2018, 04:13
Well, I've take a look at provided files. Added a quick fix to let those 2 skeletal meshes to load.

-game=sod2 or overriding to "State of Decay 2" is required.

As I said, I have only 2 sample meshes, so I can not guarantee that UModel will not crash with anything else. The game requires intense testing.

Skeletal meshes work great, have had no crashes related to them yet. Thanks.


Title: Re: State of Decay 2
Post by: Juso3D on June 06, 2018, 21:23
Yeah everything works fine, only minor issues is most models have no textures viewing in uModel, due to some custom material setup I believe, nothing major, textures are in same folder has mesh.

(http://i.imgur.com/1dipJXFl.png) (https://imgur.com/1dipJXF)
(http://i.imgur.com/j3cBLibl.png) (https://imgur.com/j3cBLib)


Title: Re: State of Decay 2
Post by: FuzeTek on June 07, 2018, 00:59
Out of curiosity, What version of the game are you using? I bought it through the Microsoft store and it looks like the files are encrypted and no amount of permission settings will let me access the Paks.


Title: Re: State of Decay 2
Post by: Gildor on June 07, 2018, 01:16
This is usual situation with Microsoft's games. I think it has standard solution, check Gears of War 4 and Sea of Thieves threads.


Title: Re: State of Decay 2
Post by: Juso3D on June 07, 2018, 07:06
Out of curiosity, What version of the game are you using? I bought it through the Microsoft store and it looks like the files are encrypted and no amount of permission settings will let me access the Paks.
Got it from the store also with Windows Game Pass, you need to use this UWPDumper (https://github.com/Wunkolo/UWPDumper) to decrypt the files, same has Sea of Thieves in the other thread has Gildor mention..


Title: Re: State of Decay 2
Post by: ebross67 on June 12, 2018, 06:38
Do I have to compile UWPDumper from Github? I can't find an exe file.


Title: Re: State of Decay 2
Post by: ebross67 on June 12, 2018, 06:57
I'm completely lost. I found the uwpinjector.exe, but what do I do with it?


Title: Re: State of Decay 2
Post by: Juso3D on June 12, 2018, 07:27
I'm completely lost. I found the uwpinjector.exe, but what do I do with it?
Run the game, then run the injector, type the ID that matches the game, then it will start unlocking the files, then you want to navigate to the following,

Quote
X:\WpSystem\S-1-5-21-50246372-3526001978-2445386389-1001\AppData\Local\Packages\Microsoft.Dayton_8wekyb3d8bbwe\TempState\

Change the X: directory to what drive you installed the game on like C: for default etc....


Title: Re: State of Decay 2
Post by: ebross67 on June 13, 2018, 07:04
Thanks Blenux, - the key was starting the game. It dumped!


Title: Re: State of Decay 2
Post by: loongers on August 17, 2018, 15:08
With the latest UE Viewer (build 863), I choosed game override State of Decay 2, but I found that
the texture does not shown correctly, and the debug log shows that there are some warnings as follows,
so how do I fix this, is threr anything wrong?
Thanks a lot.
(https://s1.ax1x.com/2018/08/17/PW2wEq.png)
(https://s1.ax1x.com/2018/08/17/PW20U0.jpg)
(https://s1.ax1x.com/2018/08/17/PW2abn.png)

and if I press 'M', it seems that could show some materials, as follows
(https://s1.ax1x.com/2018/08/17/PWfevF.png)


Title: Re: State of Decay 2
Post by: Juso3D on August 17, 2018, 17:08
It's the way the developers setup their materials and the game that for reasons unknown the materials won't be cooked right, can't do much about it except just look for the model in game and recreate the material setup that way.


Title: Re: State of Decay 2
Post by: loongers on August 23, 2018, 08:41
thanks for your reply.
But the game runs always without any texture problem. I don't know why the game running is ok, but view by Umodel can't show the texture correctly.
Is the UE version does not match the games?


Title: Re: State of Decay 2
Post by: Gildor on August 23, 2018, 09:35
Because game assigns textures in some different way, which is not seen by UModel. UModel can't support everything what UE can do, it's too small for that.


Title: Re: State of Decay 2
Post by: loongers on August 24, 2018, 11:31
Got it. Thanks for your replay.
Is there any possiblity to support this kind of texture assignment or the possible reason for this result.
Or I can do some research on this problem.


Title: Re: State of Decay 2
Post by: Gildor on August 24, 2018, 11:33
This material assignment is custom for this game (i.e. not exists in original UE4), so it won't be supported. Sorry.


Title: Re: State of Decay 2
Post by: dantesai on December 17, 2018, 07:14
Memory:bad allocation size -536870912 bytes
Call stack:
appMalloc:size=-536870912 (total=186 Mbytes) <- FArray::Empty:1065353216 x 64 <- TArray::Serialize:0/0 <- FStaticLODModel4<< <- TArray::Serialize:1/3 <- USkeletalMesh4::Serialize <- LoadObject:SkeletalMesh4'MaleFeral.MaleFeral', pos=CCDE2, ver=505/0 (unversioned), game=sod2 <- UObject::EndLoad <- LoadWholePackage:MaleFeral <- ExportPackages <- UIMenuItem::HandleCommand <- UIMenu::Popup <- UIBaseDialog::WndProc


Title: Re: State of Decay 2
Post by: Gildor on December 17, 2018, 09:15
1. Which umodel version do you use? Build from this site, custom build, which version?
2. Does this error happen with any skeletal mesh, or just with a single one?


Title: Re: State of Decay 2
Post by: dantesai on December 17, 2018, 11:11
1. Which umodel version do you use? Build from this site, custom build, which version?
2. Does this error happen with any skeletal mesh, or just with a single one?
1. download the last version "Updated 9 December, 2018 - 10:04"
2.this error just with a named "shirt_01a", locate it in "Game/StateOfDecay2/Art/Feral/Male/Torso/shirt_01_a.uasset"

and found animation export miss all the time.
Loading Skeleton Human_Skeleton from package /StateOfDecay2/Content/Art/Characters/Human/Skeletons/MaleStandard/Human_Skeleton.uasset
WARNING: ArrayProperty "USkeleton::Sockets" was not found
WARNING: ArrayProperty "USkeleton::BlendProfiles" was not found
WARNING: ArrayProperty "USkeleton::SlotGroups" was not found
Loaded in 0.003 sec, 172 allocs, 0.04 MBytes serialized in 9 calls.
Exporting objects ...
Memory: allocated 70767550 bytes in 501674 blocks


Title: Re: State of Decay 2
Post by: dantesai on December 17, 2018, 11:27
exporting Vehicle Mesh crash
Loading SkeletalMesh4 SUV_Modern_Apoc from package /StateOfDecay2/Content/Art/Driveables/SUV_Modern_Apoc/SUV_Modern_Apoc.uasset
WARNING: BoolProperty "USkeletalMesh4::bHasBeenSimplified" was not found
WARNING: ObjectProperty "USkeletalMesh4::PhysicsAsset" was not found
WARNING: ArrayProperty "USkeletalMesh4::MorphTargets" was not found
WARNING: ArrayProperty "USkeletalMesh4::AssetUserData" was not found
WARNING: Unknown class "ULAssignMaterialInfo" for object "m_suv_modern_red_talon_interior_01_inst"
WARNING: Unknown class "ULAssignMaterialInfo" for object "m_suv_modern_red_talon_glass_01_inst"
WARNING: Unknown class "ULAssignMaterialInfo" for object "m_suv_modern_red_talon_wheels_01_inst"
WARNING: Unknown class "ULAssignMaterialInfo" for object "m_suv_modern_red_talon_exterior_01_inst"
WARNING: Unknown class "ULAssignMaterialInfo" for object "m_suv_modern_apoc_armor_01_inst"
WARNING: SkeletalMesh SUV_Modern_Apoc has vertex colors

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.


Title: Re: State of Decay 2
Post by: Gildor on December 17, 2018, 11:34
Was the game updated? May be game received some changes making it not working with umodel?


Title: Re: State of Decay 2
Post by: dantesai on December 17, 2018, 13:13
Was the game updated? May be game received some changes making it not working with umodel?
State of Decay 2 version 316034
it is small problem, I can ignore


Title: Re: State of Decay 2
Post by: dantesai on December 18, 2018, 06:11
a new problem
serializing being stopper (4EAB12+1>4EAB13)
FPakFile::Serialize:file=/StateOfDecay2/Content/Art/Driveables/SUV_Modern_Apoc/SUV_Modern_Apoc.uasset <- TArray::Serialize:42244/196608 <- FSkelMeshSection4<< <- TArray::Serialize:0/65536 <- FStaticLODModel4<< <- TArray::Serialize:1/3 <- USkeletalMesh4::Serialize <- LoadObject:SkeletalMesh4'SUV_Modern_Apoc.SUV_Modern_Apoc', pos=4EAB13, ver=505/0 (unversioned), game=sod2 <- UObject::EndLoad <- LoadWholePackage:SUV_Modern_Apoc <- ExportPackages <- UIMenuItem::HandleCommand <- UIMenu::Popup <- UIBaseDialog::WndProc


Title: Re: State of Decay 2
Post by: Gildor on December 18, 2018, 08:24
I've asked a few questions and didn't get an answer. I don't have the game to try it myself, so I'm asking to be able to understand what could be wrong - game update, lose of compatibility with umodel's update, etc.


Title: Re: State of Decay 2
Post by: Gildor on December 19, 2018, 08:49
I'll repeat my questions.
1. Was the game updated? Did umodel work well before game's update?
2. Does error happen with ANY assets, or just with several of them?


Title: Re: State of Decay 2
Post by: Juso3D on December 19, 2018, 12:54
I've notice if one doesn't have the original Microsoft main folder which at the time I had (Microsoft.Dayton_1.3160.34.2_x64__8wekyb3d8bbwe), the shotgun_breacher mesh or any other weapon/characters/vehicles will fail to open, however vehicles (SUV_Modern_Avoc) will fail to open regardless of having this, seems it could be a corrupted mesh

Static Mesh/Textures are unaffected and work fine, without material assigned though.

(http://i.imgur.com/7H1ZKfAm.png) (https://imgur.com/7H1ZKfA)
(http://i.imgur.com/vOXQPTkm.png) (https://imgur.com/vOXQPTk)
(http://i.imgur.com/K4SBjmhm.png) (https://imgur.com/K4SBjmh)

Animations work also*
(http://i.imgur.com/sNW2KiSm.png) (https://imgur.com/sNW2KiS)

So to get it working with skeletons is like so,

From this, (or what ever you may have it has)
X:\Games\Installed Games\StateOfDecay2\Content\Paks

To this, (X:\Games\Installed Games\ is my preferred game install location, you don't need to put this)
X:\Games\Installed Games\Microsoft.Dayton_1.3xxxx.xx.x_x64__8wekyb3d8bbwe\StateOfDecay2\Content\Paks


Title: Re: State of Decay 2
Post by: Gildor on December 19, 2018, 15:08
This makes sense. The game may have multiple pak files, and those paks may have assets made for older engine version. Umodel "hides" older assets when another pak overrides them, pak with "larger" name (ex. "assets_10.pak" vs "assets_1.pak"). So, if Blenux right, then if assets_10.pak is missing, then some assets will be picked from assets_1.pak, and umodel will fail them to load because the engine differs. Honestly, the GAME itself will fail to load them too, because there's no way to identify which version is used, so such older assets are rather garbage and wasting disk space.

I've noticed such things with Gears of War 4 - it also had assets with different versions, and I had to download all pak files in order to make game working.


Title: Re: State of Decay 2
Post by: Juso3D on December 19, 2018, 15:48
Yeah even there pak file names are confusing lol, but probably reasons why.

(http://i.imgur.com/2PKyOYum.png) (https://imgur.com/2PKyOYu)

They seem to be using this with their Materials also, which is like 99% of the models come with no materials applied perhaps?, besides from a few that use some form of UE4 standard Materials found in most UE4 games.

UassetImportData UE4 Doc (https://api.unrealengine.com/INT/API/Runtime/Engine/EditorFramework/UAssetImportData/index.html)

(http://i.imgur.com/8lUH4Gnm.png) (https://imgur.com/8lUH4Gn)



Title: Re: State of Decay 2
Post by: Pepper on July 24, 2020, 04:42
The game (or at least, the steam release) has a newer version engine now? Build.version info still says 4.13, but it seems something has changed with the steam release.  

consistent error: ERROR: Unable to read 1 bytes at pos=0x18D3203B6 on all pak files.

files are not UWP encrypted as far as I can tell, game is not a UWP app for steam, and other files in the directories of the steam version are plaintext readable/viewable.

I can supply samples if needed.

edit:
https://gofile.io/d/uaACB5

Can provide more if needed, I appreciate it even if this goes unsolved, this isn't a particularly popular or relevant game today, so people's time might not be worth fixing it.



Title: Re: State of Decay 2
Post by: Gildor on July 24, 2020, 11:04
I've made some research and updates for this game. You can open pak file now. However, UModel will crash on every second file decompression, at the very end of LZ4 compressed block - when just ~10 bytes left till the end of compressed block. I've updated LZ4 library to the recent release, this didn't help: still crashing. It seems compressed data are intentionally corrupted to prevent extraction.

I can only suppose the game has some protection against digging into the data, especially taking into account other changes I had to make to open pak files. In other words, developers says: "keep away from our data".


Title: Re: State of Decay 2
Post by: spiritovod on July 24, 2020, 16:12
You can extract the game with the corresponding quickbms script from specific scripts bundle, available here (https://cs.rin.ru/forum/viewtopic.php?f=10&t=100672) (tested on the archive above, the format is still the same). For more info read sticked topic (/smf/index.php/topic,7304.0.html).

Can't remember my thoughts about the problem (it was about 3 months ago), but aside from bloated pak version and compression type flags, I also forced chunk offset calculation method (relative one, when chunk offset += offset), despite suggested absolute offset approach. Kind of blind fix, but at least it works ._.


Title: State of decay 2 juggernaut edition
Post by: DivyaMeena on January 07, 2021, 15:49
Hey guys! i am new here so please i am sorry if I am in the wrong section, but I wanted to extract a few models from state of decay 2 juggernaut edition, i opened it in umodel viewer i found the models i wanted too but when i try to extract them it gives me random error, can someone please help me about this? what version should i put in there when i try to extract models from this game??
currently i used State of decay 2 as the option to open it and view the files
Thanks!


Title: Re: State of Decay 2
Post by: spiritovod on January 07, 2021, 19:15
@DivyaMeena: Read two posts above yours. In short, you should extract all assets from paks with quickbms script, then open extracted files in umodel and use override game detection option. Also, you're using outdated umodel build, which may bring you some problems eventually (not in this case though).


Title: Re: State of Decay 2
Post by: DivyaMeena on January 08, 2021, 07:27
@DivyaMeena: Read two posts above yours. In short, you should extract all assets from paks with quickbms script, then open extracted files in umodel and use override game detection option. Also, you're using outdated umodel build, which may bring you some problems eventually (not in this case though).

Hey! thanks for the reply! i updated umodel and now that error is gone, i used the quickbms script and extracted all of the files from both SOD2 and SOD2JE
 
and now i have those .uassets files in two seperate folders

Now when i try to use umodel to extract files from SOD2 it gives me this error[in attachment]

and when i try to extract from SOD2JE it gives me this error[second attachment]
i am trying to rip this sword model, echo-1 wraith from the game but just cant extract all these files
can someone help please D:


Title: Re: State of Decay 2
Post by: spiritovod on January 09, 2021, 03:30
@DivyaMeena: It seems not all assets are supported properly. If you need some specific model, you better try to find it manually without exporting all assets at ones, and then export only that required model.

It's kind of strange though, that asset with error seems like skeletal mesh, but common skeletal meshes are working fine even with  latest game version, but this particular mesh is not. I'll upload it and some working mesh for future references: link (https://drive.google.com/file/d/1WBiM35SEZW2WkRl9PIg-ocnceaC3ueMr/view?usp=sharing)


Title: Re: State of Decay 2
Post by: DivyaMeena on January 09, 2021, 06:15
@DivyaMeena: It seems not all assets are supported properly. If you need some specific model, you better try to find it manually without exporting all assets at ones, and then export only that required model.

It's kind of strange though, that asset with error seems like skeletal mesh, but common skeletal meshes are working fine even with  latest game version, but this particular mesh is not. I'll upload it and some working mesh for future references: link (https://drive.google.com/file/d/1WBiM35SEZW2WkRl9PIg-ocnceaC3ueMr/view?usp=sharing)

i actually wanted to just export the ones i needed only but as i couldn't find them i tried to export all and was stuck here, THO! right now i randomly searched for the keyword *sword* and a few new category appeared named DLC_theName i exported them just to see mayeb they're the one and omg they were the one, once again tysm for your help! finally done with this project :D


Title: Re: State of Decay 2
Post by: spiritovod on November 07, 2023, 03:45
The following issues should be fixed in specific build from this topic (/smf/index.php/topic,7906.0.html) with existing override option (tested only on steam version of the game):
- Loading assets from packages without extracting them, including full scan / batch export
- Some skeletal meshes, which previously crashed
- Proper loading of hi-res textures and some materials