Identity V Assets (.npk) zlib compression

[TeaEffTeu]

34 minutes ago, Furaex said:

Hello, identity v has recently been updated with a new engine. After exporting, the file format is X-4. Is there any solution? Do you have a backup of the old version?

Please ensure that you are using v0.4.3 of the archive extraction script. Any earlier versions do not support the encryption that came with the NeoX 2 engine update.

[aarontaro]

On 6/10/2024 at 8:37 AM, vioywv said:

heya! were u able to find info ab this or eventually find emmas files?! i really want the model, but im encountering the same problem. 😞

unfortunately, i could never figure out the issue. i have reason to believe its something related to RMAViewer and not the bms script itself. we'll just have to wait and see if someone makes an alternative to RMAViewer and see if ripping becomes easier lol

i could only ninjarip the hello kitty emma sadly so you'll have to manually rig stuff

[Minako]

On 9/15/2024 at 2:59 AM, TeaEffTeu said:

Please ensure that you are using v0.4.3 of the archive extraction script. Any earlier versions do not support the encryption that came with the NeoX 2 engine update.

While the script does help extracting the npk files, the dat files inside are not loadable in RMA anymore. Maybe a few load, if at all. This goes for the CHR NPK files. Any idea how to open them or maybe a new bms script is needed?

[TeaEffTeu]

1 hour ago, Minako said:

While the script does help extracting the npk files, the dat files inside are not loadable in RMA anymore. Maybe a few load, if at all. This goes for the CHR NPK files. Any idea how to open them or maybe a new bms script is needed?

RMAViewer cannot load the new model version, you can try using https://github.com/zhouhang95/neox_tools to view the models.

[Minako]

5 minutes ago, TeaEffTeu said:

RMAViewer cannot load the new model version, you can try using https://github.com/zhouhang95/neox_tools to view the models.

Yes, I've already tried that before making my earlier post, and none of the dat files can be converted to iqe anymore either. I just keep getting errors, whereas before, it always worked. I'm guessing it's because that github tool is for the previous engine version and not for Neox2 unfortunately. In case I'm doing something wrong, are you able to open the new dat files with the github tool? Otherwise, I feel this is a lost cause unless someone makes a better RMA or an updated Neox2 tool 

[TeaEffTeu]

7 minutes ago, Minako said:

Yes, I've already tried that before making my earlier post, and none of the dat files can be converted to iqe anymore either. I just keep getting errors, whereas before, it always worked. I'm guessing it's because that github tool is for the previous engine version and not for Neox2 unfortunately. In case I'm doing something wrong, are you able to open the new dat files with the github tool? Otherwise, I feel this is a lost cause unless someone makes a better RMA or an updated Neox2 tool 

The tool is unstable. It works sometimes, but it crashes for reasons I don't understand. I don't think it's an issue with the new engine; I've opened models of the same version from other games, and they cause the tool to behave similarly.

[Minako]

14 minutes ago, TeaEffTeu said:

The tool is unstable. It works sometimes, but it crashes for reasons I don't understand. I don't think it's an issue with the new engine; I've opened models of the same version from other games, and they cause the tool to behave similarly.

Strange. I've never had issues with the tool. It has never crashed for me, and it has converted dat files perfectly on the previous Neox engine. Whenever I try the new dat files from Neox 2 though, every single one of them give me an error and just cannot be converted. I've tried dat files from two npk's and they're all impossible now. That's why I'm assuming this is due to Neox 2 engine because I've never had issues beforehand using python, but now suddenly every single new dat file just errors out and can't be converted.

[TeaEffTeu]

3 minutes ago, Minako said:

Strange. I've never had issues with the tool. It has never crashed for me, and it has converted dat files perfectly on the previous Neox engine. Whenever I try the new dat files from Neox 2 though, every single one of them give me an error and just cannot be converted. I've tried dat files from two npk's and they're all impossible now. That's why I'm assuming this is due to Neox 2 engine because I've never had issues beforehand using python, but now suddenly every single new dat file just errors out and can't be converted.

All existing models have been updated to use the new model version. The tool does not fully support it which is why you've been experiencing these problems. Unfortunately, you'll have to wait until the tool is updated to support the new models.

[wq223]

Currently when using the nxpk.bms script, the texture file (which I think is in astc format) is renamed to .dat
For the astc file renamed to .dat, you only need to check whether it meets the astc requirements and then modify the suffix to open it with a picture viewer.
There is also an astc file that is missing the file header, with the suffix .com, but it contains width and height metadata. I don’t know why, but the block size seems to default to 6x6. At least now, there are rarely undisplayable contents.
So I wrote a script to convert .com files to .astc, it's a bit weird but it works
Just type the command in the command line interface
python com.py Input folder Output folder

 

 

 

com.py

[TeaEffTeu]

7 minutes ago, wq223 said:

Currently when using the nxpk.bms script, the texture file (which I think is in astc format) is renamed to .dat
For the astc file renamed to .dat, you only need to check whether it meets the astc requirements and then modify the suffix to open it with a picture viewer.
There is also an astc file that is missing the file header, with the suffix .com, but it contains width and height metadata. I don’t know why, but the block size seems to default to 6x6. At least now, there are rarely undisplayable contents.
So I wrote a script to convert .com files to .astc, it's a bit weird but it works
Just type the command in the command line interface
python com.py Input folder Output folder

com.py 1.59 kB · 1 download

I was having trouble determining the CompBlks format by myself, thanks for figuring it out.

I can't really do anything interesting with the nxpk script other than add/change compression and encryption methods. I ran into limitations with QuickBMS while trying to implement a custom extension guesser. I'm currently developing a new experimental tool, but I suggest using NeoXtractor which was released recently.

[Zambies]

i tri the com.py and the quickbms 4.3 script but the images random pixels instead of images as shown when open in tacent view 1.0.46. did files change again? do i need another viewer? 😢 

thank u for help

[wq223]

2 hours ago, Zambies said:

我试用了 com.py 和 quickbms 4.3 脚本，但在 tacent view 1.0.46 中打开时，图像显示为随机像素，而不是图像。文件又变了吗？我需要另一个查看器吗？😢 

谢谢你的帮助

Is it all files like this or all the files have 1, 2 that may be unknown. If all pictures are like this, then I should consider updating the script.

[JohnSmith]

4 hours ago, wq223 said:

Is it all files like this or all the files have 1, 2 that may be unknown. If all pictures are like this, then I should consider updating the script.

Yes, all pictures are like this.I don't know where I went wrong, can you help me take a look?

sample_astc.zip

[wq223]

10 hours ago, JohnSmith said:

Yes, all pictures are like this.I don't know where I went wrong, can you help me take a look?

sample_astc.zip 11.26 kB · 2 downloads

I re -downloaded the fifth personality (formal version) and obtained the .com file. Try to use my script to analyze it. It still applies to the normally appear, but the files you provide cannot be applicable. If the downloaded version is not, it may be that the file type may change. You can provide the original .com file so that I can check if the format is really modified, or in special cases or in special cases.

[JohnSmith]

1 hour ago, wq223 said:

I re -downloaded the fifth personality (formal version) and obtained the .com file. Try to use my script to analyze it. It still applies to the normally appear, but the files you provide cannot be applicable. If the downloaded version is not, it may be that the file type may change. You can provide the original .com file so that I can check if the format is really modified, or in special cases or in special cases.

 

original.comfiles.zip

[wq223]

6 小时前，JohnSmith 说：

 

original.comfiles.zip 134.03 kB  ·  3 次下载

I tested your files, and it seems that they are not like ASTC format. After the conversion, ASTC metadata starts with two 00s. I think it seems a bit wrong, because I have never seen ASTC metadata starting with two 00s. The file type changes this is the only possibility
I updated the script. Now he has one more test. After reading the file header, he will continue to read whether the next byte is
B4930000 to determine whether it is a processed ASTC format
I have conducted some file testing in the fifth personality (formal version) and the fifth personality (common version)
Most of the .com files I got were B4930000, and what you posted became F3830000. This does not seem to meet expectations. It may be a new type. Now you need to wait for a big man to clarify what type of file he is.

程序库

Edited February 2 by wq223

[JohnSmith]

4 hours ago, wq223 said:

I tested your files, and it seems that they are not like ASTC format. After the conversion, ASTC metadata starts with two 00s. I think it seems a bit wrong, because I have never seen ASTC metadata starting with two 00s. The file type changes this is the only possibility
I updated the script. Now he has one more test. After reading the file header, he will continue to read whether the next byte is
B4930000 to determine whether it is a processed ASTC format
I have conducted some file testing in the fifth personality (formal version) and the fifth personality (common version)
Most of the .com files I got were B4930000, and what you posted became F3830000. This does not seem to meet expectations. It may be a new type. Now you need to wait for a big man to clarify what type of file he is.

程序库

I think I might have realized where the problem lies. If you don't mind me asking, is the .com file you extracted from the ui.part.a_0001.npk file? I've been extracting from ui.part.a_0001.npk, and the .com file that nxpk_v0.4.3 automatically identifies after extraction is the same one I uploaded to you.

[wq223]

15 hours ago, JohnSmith said:

我想我可能意识到问题出在哪里了。如果你不介意的话，请问一下，你提取的.com文件是从ui.part.a_0001.npk文件中提取的吗？我一直从ui.part.a_0001.npk中提取，提取后nxpk_v0.4.3自动识别的.com文件和我上传给你的那个是同一个。

Hello, I don’t play this game. Studying these is only my hobby, and I don’t know what documents I am an unpacking, but their names have a UI. I think they include pictures and adapt to my script normally. I mentioned the 0001 file you mentioned here, but I have found it here, but I did not solve this file. Other NPK packages I unlocked, most of the .com files were suitable for

[JohnSmith]

21 hours ago, wq223 said:

Hello, I don’t play this game. Studying these is only my hobby, and I don’t know what documents I am an unpacking, but their names have a UI. I think they include pictures and adapt to my script normally. I mentioned the 0001 file you mentioned here, but I have found it here, but I did not solve this file. Other NPK packages I unlocked, most of the .com files were suitable for

I am studying the NPK files of Identity V out of interest, and now I’ve figured out the key issue. When extracting NPK files of the same version of Identity V for PC (ui.part.a.npk) and Android (ui.mini.a.npk) using nxpk_v0.4.3.bms and NeoXtractor-1.2, I found that nxpk_v0.4.3.bms recognizes the files as .com, while NeoXtractor-1.2 recognizes them as .cbk. Additionally, the file structures for the PC version (dwrg2\Documents\res\ui.part.a.npk) and the Android version (ui.mini.a.npk) are different. When extracting the PC version (ui.part.a.npk) using NeoXtractor-1.2, only .cbk, .csb, and .atlas files are extracted, but no .astc files are found. However, when extracting the Android version (ui.mini.a.npk), .cbk and .astc files are extracted, and the images can be viewed correctly using tacentview_1.0.46. Therefore, your com.py script seems to be fine. What puzzles me is that when I try to extract the PC version file (dwrg2\Documents\res_reserved\ui.part.a_0001.npk) using NeoXtractor-1.2, I get an error message: "UnboundLocalError: cannot access local variable 'file_sign' where it is not associated with a value.

[TeaEffTeu]

2 hours ago, JohnSmith said:

I am studying the NPK files of Identity V out of interest, and now I’ve figured out the key issue. When extracting NPK files of the same version of Identity V for PC (ui.part.a.npk) and Android (ui.mini.a.npk) using nxpk_v0.4.3.bms and NeoXtractor-1.2, I found that nxpk_v0.4.3.bms recognizes the files as .com, while NeoXtractor-1.2 recognizes them as .cbk. Additionally, the file structures for the PC version (dwrg2\Documents\res\ui.part.a.npk) and the Android version (ui.mini.a.npk) are different. When extracting the PC version (ui.part.a.npk) using NeoXtractor-1.2, only .cbk, .csb, and .atlas files are extracted, but no .astc files are found. However, when extracting the Android version (ui.mini.a.npk), .cbk and .astc files are extracted, and the images can be viewed correctly using tacentview_1.0.46. Therefore, your com.py script seems to be fine. What puzzles me is that when I try to extract the PC version file (dwrg2\Documents\res_reserved\ui.part.a_0001.npk) using NeoXtractor-1.2, I get an error message: "UnboundLocalError: cannot access local variable 'file_sign' where it is not associated with a value.

The extensions .com and .cbk are fake, the real extension is .compblks. Both are just guesses by the extractors.

NeoXtractor has difficulty extracting certain res_reserved NPKs as they contain extra erroneous data.

[Zambies]

ones ui.part.b, ui.part.a, etc are different from the 0001 etc ones yes. extractors struggle with 0000 number ones as TeaEffTeu say. i try ui.part.b with new com and it say incorrect byte type. 😥 ui.part.a_0001 say same. both i extract with latest bms script. i try ui.part.b with neoxtractor and it also incorrect byte type. 😥

these are com i try to open (removed .dat and .png for smaller size when upload)

ui.part.b.7z

[ʚ Sarahtonin ɞ]

Lot of great work being done in this thread, I've done a Lot of IDV extracting with the old QuickBMS scripts initially shared around on Xentax, and thankfully was able to back up all the files from before the new engine update, and have been extracting from those. But there's quite a lot of skins I'd like to extract to use in animations, and the old script doesn't work obviously. Thanks to everyone for their hard work in here. I've not seen the NeoXtractor before, but it seems really good, and hella helpful! Thank you for sharing it! I'm hoping to see more updates to NeoXtractor though, as it seems a lot easier and better to use just one app, to view the .npk, rather than having to decompile the entire thing, and then blindly browsing via RMA, which is what I have been doing this entire time. (I don't know how most people here get their textures, but I just use Ninjaripper 2 to extract them from the game whenever I find a model to use, as the textures are All over the place when extracted from the .npks..)

Also, TeaEffTeu I've seen you around a few times and matched with you a few times recently on tha NA server! I always thought your name was fun, but I had no idea you were up to all this in the IDV community. Thanks for contributing to this, it's a huge thing for me, as someone who is a 3D animator and artist, being able to extract the models to use in Blender and such is not only fun, but just really cool. Thanks for contributing to that! Small world lol

I remember altering my old BMS script in the past to kinda work when they made the new-ish .npk format after Fools Gold came out, but a better edit came along from someone else soon after. I'll make sure to share any helpful info I can involving the BMS scripts, or just the file formats in general. Thanks once again to everyone helping with this process! ^^

Edited February 9 by ʚ Sarahtonin ɞ

[TeaEffTeu]

I've developed a solution for the CompBlks format, but I'll need to clean up my implementation before I release it.

[TeaEffTeu]

This tool replaces the need for my bms script. Any CompBlks files will be automatically converted to DDS files when exported.

[Zambies]

im sorry for question but when i run exe it show console flash then never does anything else 😥 do i put exe somewhere special or download other files? i put on desktop and ran 😥 sry