inZOI

[TXKBOY]

I don't know why, it feels like the ue view hasn't updated the inZOI patch, and I can't extract anything.

[GDL]

I don't know why, it feels like the ue view hasn't updated the inZOI patch, and I can't extract anything.

I had some issues with the command line for this game so I used the script and the gui, just point the script to the Paks folder as the input and the same as the output and choose to overwrite all the files it ask you to and after that delete the .orig file and umodel should work.

[spiritovod]

@GDL: If you'll remove backup of original package, you will not be able to launch the game afterwards without redownloading it or verifying installation. Please don't suggest such things, backup is created for a purpose.

@lanmao: Virtual textures are not supported at the moment, it's explained in the topic with current limitations and possible issues, mentioned in the first post.

[spiritovod]

@lanmao: I guess fmodel should work fine with textures, but it has its own specifics for UE5 games, which is out of scope of this forum.

@TXKBOY: Please address all quickbms or keys related issues to the topic with keys, not here. If you don't know how to launch programs with arguments, you can simply choose to overwrite files when asked after using the script on compatible package.

[spiritovod]

@Kryptedbbkick: The game is using signature checks and some integrity checks. You should bypass them before applying mods or make the game able to sideload assets, but it's out of scope of this forum. It's better to address such things to modding communities.

[spiritovod]

@mark2580: According to your logs, all game packages are loaded properly, otherwise there would be some warnings. You can find most things in usual way, by performing full scan and sorting assets in flat view mode.

Though default handling of paths in umodel can be confusing. I've disabled compact paths in updated UE5 build by default and exposed it as additional option at startup screen and command line. Normally it may affect processing of some extracted assets and packages, but for UE5 games it shouldn't be an issue in most cases.

[spiritovod]

@mark2580: For games with io store packages (utoc/ucas), like this one, all native assets supported by umodel are stored there, while normal packages (pak) contains only third-party assets like wwise audio, ini configs, shaders cache and things like that. Some packages can be dummy ones without any files stored within - they're required for the engine (and umodel) to recognize paired io store packages. Those things with unknown format are not game packages, but CEF files, recognized by umodel due to the same extension, you can simply ignore them. Successful loading of io store packages is not logged like for usual packages, but in case of issues with them you would see at least some warnings or even crash. I can add such logging if needed, though not sure the result will be more convenient without people reading explanations like this.

As for static meshes, the game is using nanites (like many UE5 games), and umodel can parse only base geometry for them like explained in the topic with current limitations. I guess the game is also using other ways for creating generic items, like mutable/customizable objects, blueprint generated classes and such, which is out of scope of umodel. Some meshes are stored in umaps as well.