Dead Island 2

[AllEx]

I'm also having problems with extracting data.
I'm using umodel_acl_1.3 with game override option.
Error message:

Loading Material3 M_Fluid_PostProcess_UnderSurface from package /DeadIsland/Plugins/DSWater/Content/Materials/PostProcess/M_Fluid_PostProcess_UnderSurface.uasset
ByteProperty: unknown UMaterial3 MaterialDomain
BoolProperty: unknown UMaterial3 bCastRayTracedShadows
StructProperty: unknown FMaterialCachedParameters Data
WARNING: Unknown class "Texture2DArray" for object "TA_Default_Caustics_D"
WARNING: Unknown class "Texture2DArray" for object "TA_Default_WaveFoam_D"
WARNING: Unknown class "Texture2DArray" for object "TA_Default_WaveFoam_D"
WARNING: Unknown class "TextureRenderTarget2D" for object "RT_SimTarget0"
WARNING: Unknown class "Texture2DArray" for object "TA_Default_Caustics_D"
Loading Texture2D PT_Linear_Noise from package /Game/DIShared/Effects/Materials/Noise/PT_Linear_Noise.uasset
Loading Texture2D T_UnderwaterDistortion_N from package /DeadIsland/Plugins/DSWater/Content/Textures/T_UnderwaterDistortion_N.uasset
Loading Texture2D T_Black_D from package /Game/DIShared/Core/Materials/T_Black_D.uasset
******** Loading object Texture2D'T_Black_D.T_Black_D' ********
*** ERROR: Access violation (C0000005) at umodel_acl_1.3.exe+0x34DA0
CachedExpressionData <- UMaterial3::ScanMaterialExpressions <- UMaterial3::PostLoad <- PostLoad: M_Fluid_PostProcess_UnderSurface <- UObject::EndLoad <- LoadWholePackage: /DeadIsland/Plugins/DSWater/Content/Materials/PostProcess/M_Fluid_PostProcess_UnderSurface.uasset <- ExportPackages <- UIMenuItem::HandleCommand <- UIMenu::Popup <- UIBaseDialog::WndProc <- UIBaseDialog::CustomMessageLoop <- UIBaseDialog::ShowDialog: modal=1, title="Choose a package to open" <- CUmodelApp::ShowPackageUI <- Main: umodel_build=1579 based

[AllEx]

@AllEx: It should be fixed now in the updated build. Though such materials wouldn't be parsed properly anyway.

I used the latest build version, but it crashes in other places. Ex.
Loading Texture2D T_Black_D from package /Game/DIShared/Core/Materials/T_Black_D.uasset
******** Loading object Texture2D'T_Black_D.T_Black_D' ********
*** ERROR: TArray: index 0 is out of range (0)
CachedExpressionData <- UMaterial3::ScanMaterialExpressions <- UMaterial3::PostLoad <- PostLoad: M_Opaque <- UObject::EndLoad <- LoadWholePackage: /Game/DI2/Art/Environment/Architecture/MapSpecific/Sewers/SM_ARC_Sewer_T04A_Fatberg_01.uasset <- ExportPackages <- UIMenuItem::HandleCommand <- UIMenu::Popup <- UIBaseDialog::WndProc <- UIBaseDialog::CustomMessageLoop <- UIBaseDialog::ShowDialog: modal=1, title="Choose a package to open" <- CUmodelApp::ShowPackageUI <- Main: umodel_build=1590

Is it possible to run UModel in such a way that it would ignore those assets that it can not export? It is quite sad to wait for a long time and somewhere on 90% to see crash of tool. After that you should try to export assets from subfolders many times until you realize, what exactly is causing crash.

[AllEx]

make sure you re-downloaded updated build via link in the first post

OK, my mistake. I checked version 1.3 again and noticed that you updated it. This time I tried exporting in PSK, not in GLTF. It looks like it works more stable, but unfortunately it crashes again:
Loading MaterialInstanceConstant MI_VertAnim_Zombie_Reach_EyeLevel from package /Game/DI2/Effects/Vertex_Animation/Reach_EyeLevel/MI_VertAnim_Zombie_Reach_EyeLevel.uasset
ArrayProperty: unknown UMaterialInstanceConstant CachedReferencedTextures
Loading Material3 M_Zombie_Vertex_Animation from package /Game/DIShared/Effects/Master_Materials/M_Zombie_Vertex_Animation.uasset
ByteProperty: unknown UMaterial3 MaterialDecalResponse
StructProperty: unknown UMaterial3 MaterialAttributes
IntProperty: unknown UMaterial3 NumCustomizedUVs
BoolProperty: unknown UMaterial3 bTangentSpaceNormal
StructProperty: unknown FMaterialCachedParameters Data
Loading Texture2D PT_VertexAnim_Reach_EyeLevel_UV1 from package /Game/DI2/Effects/Vertex_Animation/Reach_EyeLevel/PT_VertexAnim_Reach_EyeLevel_UV1.uasset
******** Loading object Texture2D'PT_VertexAnim_Reach_EyeLevel_UV1.PT_VertexAnim_Reach_EyeLevel_UV1' ********
*** unknown member TC_VertexAnimPos of enum ETextureCompressionSettings
Loading Texture2D PT_VertexAnim_Reach_EyeLevel_UV1_Normals from package /Game/DI2/Effects/Vertex_Animation/Reach_EyeLevel/PT_VertexAnim_Reach_EyeLevel_UV1_Normals.uasset
******** Loading object Texture2D'PT_VertexAnim_Reach_EyeLevel_UV1_Normals.PT_VertexAnim_Reach_EyeLevel_UV1_Normals' ********
*** unknown member TC_VertexAnimPos of enum ETextureCompressionSettings
*** ERROR: Memory: bad allocation size -469776384 bytes
appMalloc: size=-469776384 (total=865 Mbytes) <- FArray::Empty: 1065352960 x 56 <- TArray::Serialize: 0/0 <- FTexturePlatformData<< <- UTexture2D::Serialize4 <- UTexture2D::Serialize <- LoadObject: Texture2D'PT_VertexAnim_Reach_EyeLevel_UV1_Normals.PT_VertexAnim_Reach_EyeLevel_UV1_Normals', pos=55E, ver=518/0, game=di2 <- UObject::EndLoad <- LoadWholePackage: /Game/DI2/Effects/Vertex_Animation/Reach_EyeLevel/MI_VertAnim_Zombie_Reach_EyeLevel.uasset <- ExportPackages <- UIMenuItem::HandleCommand <- UIMenu::Popup <- UIBaseDialog::WndProc <- UIBaseDialog::CustomMessageLoop <- UIBaseDialog::ShowDialog: modal=1, title="Choose a package to open" <- CUmodelApp::ShowPackageUI <- Main: umodel_build=1579 based

Anyway, having ability to ignore failing assets would help a lot! Yesterday I spent 3+ hours trying to get non-failing assets. With checkbox "ignore failing assets" I would not spend any extra time I know I can disable some type of resources. But imagine that crash happen only with some material and with all static meshes, which uses this texture. To avoid crash I would have to disable export of all meshes and materials. But if we would have that checkbox, we would be able to export all meshes and materials which are not leading to crash. So, this tool would bring much more benefit to users. But I don't want to be insistent, it is just my opinion

[AllEx]

it's not possible to bypass all possible errors by design, because most of them are caused by custom changes in the engine, which you don't expect while parsing binary data and all adjustments should be done manually on per game basis (mostly). There is no other way around. Also, you can copy only crash message, there is a button for this in the crash window.

Got it. Thanks for explaining!
I have few more questions:
1. Should I keep reporting here about other crashes while parsing game's data? Or it doesn't make sense?
2. I managed to get meshes and some material parameters as texture names, set of scalar/vector parameters, etc. But what I didn't find is how to extract materials/shaders themselves. Having material inputs is nice and sometimes we can recreate simple materials. But some materials seems really complicated. Ex M_Weapon - it has a looot of inputs. Without shader code we can only guess what is it doing. Game has access to shader, so in theory shader code should be accessible. Yes, may be it will need to be "disassembled" later, but it should be available. Am I wrong?
Question: is there any way to extract shader code (or materials themselves)? If not by UModel, may be someone can suggest any other tool for this?
3. Did anyone figure out how to apply "blood" texture to weapons? It actually look quite weird - it looks more like mask, not blood image. Moreover, 3 layers (R, G and B) if that textures differ a lot. I can only guess that different layers may correspond to different amount of blood on weapon, but how later blood is applied to weapon's mesh - no idea. Also if my assumption is correct and "blood" textures, which comes with weapon, are just masks, then I could not find real blood texture, applied on this mask. Did anyone find it?

[AllEx]

OK, then I will keep reporting about crashes. I know, that you are busy, so I will not expect fixes
"shaders are out of scope of the program in general" Oh, sad to hear that. Meshes without materials are not that attractive. Though, its better than nothing
"it's probably better to use graphic debuggers (like Nvidia Nsight or Intel GPA)" Thanks for the hint! I will dig into that direction.
"But that's also out of scope of this forum." Sure. I will not spoil it with offtopic. Just wanted to know direction, where to investigate. Thanks again!