XeNTaX

RunaWhite wrote:Thank you raykingnihong! That fixed the issue, my bad!!

Btw I am testing the program now and so far the issues I'm finding are:

1) I too get that same error message about previews and thus I can't see the meshes into the model viewer

RunaWhite wrote:2) I can't extract textures for some reason. Sometimes they extract automatically in DDS, but only the diffuses. If I try to manually export in other formats, I get another error message which says the maps cannot be found (but it seems to work if I click on 'Export All As')

RunaWhite wrote:3) Normal maps appear damaged.
MDA, this happens with all the normal maps I am exporting. I think this issue also appeared in ArchiveX, but I'm not sure. The green ones look fine though, this issue appears only with the standard blue normals.

raykingnihong wrote:HI MichaelDarkAngel ，My good friend, I use ARchive_neXt.exe to test Assassins.Creed.Liberation.HD errors, caching textures cannot be extracted to the specified folder.

MichaelDarkAngel wrote:

raykingnihong wrote:HI MichaelDarkAngel ，My good friend, I use ARchive_neXt.exe to test Assassins.Creed.Liberation.HD errors, caching textures cannot be extracted to the specified folder.

I would be interested in seeing a screen shot of the full error window you are receiving with the textures you are having an issue with. Based on what I can see it looks as though a slash (/) is missing from in between the name of the directory and the name of the texture.

[EDIT]
That is exactly what the problem is. Something else for me to fix.

Thanks for all the bug-squashing

--MDA

raykingnihong wrote:Hi MichaelDarkAngel，I tested the Prince.of.Persia.The.Forgotten.Sands error.

And this is happening to you with all model files also?

By extract, do you mean along with a model file? If so, I'll explain how that works. There is a certain chain that I need to follow, in order to find the textures a model uses.
1. Find the Texture Set(s) referenced in the Mesh file.
2. Find the Material(s) referenced in the Texture Set(s).
3. Find the Texture Map(s) reference in the Material(s).

If any of those are missing from the Datafile the Mesh is located in you will not get exported textures, nor will you see textures in the model viewer.[

I only decompress the Datafile when it is opened (if some people think it takes long for certain datafiles to open now, imagine waiting for close to a thousand of them to decompress before you could do anything ). But as a semi-workaround, if the program can not find a piece to the puzzle it needs in the datafile it starts in, it will look through all datafiles in the forge file. If you happen to have already opened a datafile that has the piece, it will find it and use that. If you watch the video I posted, you'll see I open the "CN_C_FR_Student_Scholar_M_DiffuseMap" datafile prior to opening the "CN_C_FR_Mid_M" datafile. I did that so the model I was using would have textures. Sorry if that hadn't been made clear before, but that is the way every version has worked, from ForgeX until now.

The issue with ArchiveX was a red/purple tint to a lot of the diffuse maps starting with ACIII if I remember correctly. This is something new. I have tried a few different DDS formats with no luck. Much like trying to find that elusive trigger that will tell me how to read around the blocks of duplicate face indices, I need to find one for these normal maps as well.

Can you view any of the texture maps in the program?

MichaelDarkAngel wrote:Updated - ARchive_neXt - for now version remains the same v1.11.16.0

Tested and working on Windows 7 Professional 32-bit, Windows 8.1 Professional 64-bit.
One thing I have noticed with Windows 7. If you install the program into the root directory, you will be required to run the program as administrator (right-click on ARchive_neXt.exe, select Properties->Compatibility, check "Run this program as an administrator" under "Privilege Level"). While testing, if I did not do that it would not save my preferences file. I did not see this same behavior in Windows 8.1.

Changes:
Temp directory and preferences file have been moved to a folder in your "My Documents" (Win7/8), "Documents" (Win8.1) folder.
Fixed the missing slash(/) that was causing image export issues.
Fixed another image export issue that would cause images to be exported without a file extension.
Fixed HD Mesh missing export options. Forgot to change it to Hair Mesh.
Added "Export Raw Data" option to Models and Images.

To Do:
Still need to figure out duplicate face index issue.
Still need to figure out normal map issue.
Prince of Persia: The Forgotten Sands has some issues.

A host of other things I haven't even started on yet because getting the models and textures right has always been a top priority.

Happy Holidays to those who celebrate,

--MDA

I will not be able to continue working on this until Friday evening at the earliest.

RunaWhite wrote:Thank you again MDA! I tested the tool and works fine. I am not getting the exception error anymore when I load it, textures export fine, same as HD meshes. I still have the preview issue, I can't see any of the models and that would be useful also to see if all the needed textures are there. Btw take your time fixing the normals and all

EDIT: I have a question not really related to the tool itself (unless it really depends on that), but more about the models:

I usually export in OBJ format and I noticed that the hair (both standard LOD0 and HQ) appears as outlined 'strands'. The mesh looks invisible once loaded and I was wondering if there is a way to 'fill' it correctly?

Probably it depends on the way they worked on their next gen models? Since we never had this issue with characters from the previous AC games...

RunaWhite wrote:EDIT2: Some models are not extractable, such as the legacy ones (Altair costume, Ezio costume, etc) and some parts for the Marquis de Sade. I get an exception error for those. Just to let you know MDA

RunaWhite wrote:EDIT4: I just encountered the same problem showed by nav00811. Arno's body (CN_U_Arnaud_Civilian2_Body_LOD0) is still screwed for me if I load it in 3DS Max (OBJ), same for Elise's body (CN_U_FR_Elise_LOD0). However, I suppose that is related to the duplicate face index issue you are already trying to fix?