READ THE RULES: Click here

Follow us on Facebook: https://www.facebook.com/xentax/ :)

ACExplorer - An Assassin's Creed .forge extractor and framework

The Original Forum. Game archives, full of resources. How to open them? Get help here.
mono24
ultra-veteran
ultra-veteran
Posts: 441
Joined: Sat Nov 06, 2010 12:27 am
Has thanked: 143 times
Been thanked: 81 times

Re: ACExplorer - An Assassin's Creed .forge extractor and framework

Post by mono24 » Sun May 26, 2019 11:55 pm

gentlegiantJGC wrote:
Sun May 26, 2019 9:12 pm
If you know anything about python you could add it. The COLLADA handler has been written so it should just be a case of hooking it up to the plugin.
Nope, not a clue about reversing/python and stuff alike at that level :(
gentlegiantJGC wrote:
Sun May 26, 2019 9:12 pm
You will note that a number of the data blocks with data in them appear twice in the list. Generally one contains all the data and another one contains some of the data (I still need to work out why this is the case). You will need to play around and find the ones with all the data. You have probably exported some of the ones with only part.
Ah, alright, because in beginning I was confused as to why they seem different in size, the files simply get overwritten, so all I have to try next and test, first row in one location and second row in another location to then compare and see what is going on.

PS: thank you for your responses, much appreciated.

mono24
ultra-veteran
ultra-veteran
Posts: 441
Joined: Sat Nov 06, 2010 12:27 am
Has thanked: 143 times
Been thanked: 81 times

Re: ACExplorer - An Assassin's Creed .forge extractor and framework

Post by mono24 » Mon May 27, 2019 5:31 am

Ok, more tests, they all give same result in every software I have tried so far.
Such as, 3dsMax versions between 2009-2020, Blender, UU3D, Daz3D, Poser even Noesis.
Something must go wrong with initial export from ACExplorer, because if we take as example Cell08018_DataBlock 2nd row obj size 317MB.
In the center of the scene there are 40909verts/107601edges/35867polys with the following messed up elements:

Code: Select all

FRV_LM_NotreDame_BackGroundBottom_01_LOD0_2
FRV_LM_NotreDame_BackGroundBottom_01_LOD0_0
FRV_LM_NotreDame_BackGroundBottom_01_LOD0_4
FRV_LM_NotreDame_BackGroundBottom_01_LOD0_4
FRV_LM_NotreDame_BackGroundBottom_01_LOD0_2
FRV_LM_NotreDame_BackGroundBottom_01_LOD0_6
FRV_LM_SEW_WL_6x_14_LOD0_1
FRV_LM_SEW_WL_6x_06_LOD0_2
FRV_LM_SEW_WL_6x_03_LOD0_2
FRV_LM_SEW_WL_6x_03_LOD0_6
FRV_LM_SEW_WL_6x_03_LOD0_12
FRV_LM_SEW_WL_6x_03_LOD0_16
FRV_LM_SEW_WL_6x_03_LOD0_22
FRV_LM_SEW_WL_6x_03_LOD0_26
FRV_LM_SEW_WL_6x_03_LOD0_32
FRV_LM_SEW_WL_6x_15_LOD0_2
FRV_LM_NotreDame_BackGroundBottom_01_LOD0_0
FRV_LM_SEW_WL_1x_01_LOD0_0
FRV_LM_SEW_WL_1x_01_LOD0_2
FRV_LM_SEW_WL_90_LOD0_4
FRV_LM_SEW_WL_1x_01_LOD0_5
LargeMesh_IC_NotreDameCemetary_01_LOD1_Chunk_0018_0
FRV_LM_SEW_WL_6x_06_LOD0_0
FRV_LM_SEW_WL_6x_03_LOD0_0
FRV_LM_SEW_WL_6x_03_LOD0_4
FRV_LM_SEW_WL_6x_03_LOD0_10
FRV_LM_SEW_WL_6x_03_LOD0_14
FRV_LM_SEW_WL_6x_03_LOD0_20
FRV_LM_SEW_WL_6x_03_LOD0_24
FRV_LM_SEW_WL_6x_03_LOD0_30
FRV_LM_SEW_WL_6x_15_LOD0_0
FRV_LM_SEW_WL_1x_01_LOD0_0
FRV_LM_SEW_WL_1x_01_LOD0_2
FRV_LM_SEW_WL_1x_01_LOD0_5
FRV_LM_SEW_WL_1x_01_LOD0_7
FRV_LM_SEW_WL_6x_14_LOD0_1
FRV_LM_SEW_WL_6x_06_LOD0_0
FRV_LM_SEW_WL_6x_03_LOD0_0
FRV_LM_SEW_WL_6x_03_LOD0_6
FRV_LM_SEW_WL_6x_03_LOD0_10
FRV_LM_SEW_WL_6x_03_LOD0_16
FRV_LM_SEW_WL_6x_03_LOD0_20
FRV_LM_SEW_WL_6x_03_LOD0_26
FRV_LM_SEW_WL_6x_03_LOD0_30
FRV_LM_SEW_WL_6x_15_LOD0_0
FRV_LM_SEW_WL_6x_14_LOD0_3
FRV_LM_SEW_WL_6x_06_LOD0_2
FRV_LM_SEW_WL_6x_03_LOD0_2
FRV_LM_SEW_WL_6x_03_LOD0_8
FRV_LM_SEW_WL_6x_03_LOD0_12
FRV_LM_SEW_WL_6x_03_LOD0_18
FRV_LM_SEW_WL_6x_03_LOD0_22
FRV_LM_SEW_WL_6x_03_LOD0_28
FRV_LM_SEW_WL_6x_03_LOD0_32
FRV_LM_SEW_WL_6x_15_LOD0_2
FRV_LM_SEW_WL_6x_14_LOD0_3
FRV_LM_SEW_WL_6x_06_LOD0_4
FRV_LM_SEW_WL_6x_03_LOD0_4
FRV_LM_SEW_WL_6x_03_LOD0_8
FRV_LM_SEW_WL_6x_03_LOD0_14
FRV_LM_SEW_WL_6x_03_LOD0_18
FRV_LM_SEW_WL_6x_03_LOD0_24
FRV_LM_SEW_WL_6x_03_LOD0_28
FRV_LM_SEW_WL_6x_03_LOD0_34
FRV_LM_SEW_WL_6x_15_LOD0_4
FRV_LM_SEW_WL_6x_06_LOD0_4
FRV_LM_Crypte_AR_01_LOD0_0
FRV_LM_Crypte_AR_01_LOD0_2
FRV_LM_Crypte_AR_01_LOD0_4
FRV_LM_Crypte_AR_01_LOD0_6
FRV_LM_Crypte_AR_01_LOD0_8
FRV_LM_Crypte_AR_01_LOD0_10
FRV_LM_Crypte_AR_01_LOD0_12
FRV_LM_Crypte_AR_01_LOD0_14
FRV_LM_Crypte_AR_01_LOD0_16
FRV_LM_Crypte_WL_01_LOD0_1
FRV_LM_Crypte_WL_01_LOD0_3
FRV_LM_Crypte_WL_01_LOD0_5
FRV_LM_Crypte_WL_01_LOD0_7
FRV_LM_Crypte_WL_01_LOD0_9
FRV_LM_Crypte_AR_01_LOD0_0
FRV_LM_Crypte_AR_01_LOD0_2
FRV_LM_Crypte_AR_01_LOD0_4
FRV_LM_Crypte_AR_01_LOD0_6
FRV_LM_Crypte_AR_01_LOD0_8
FRV_LM_Crypte_AR_01_LOD0_10
FRV_LM_Crypte_AR_01_LOD0_12
FRV_LM_Crypte_AR_01_LOD0_14
FRV_LM_Crypte_AR_01_LOD0_16
while the rest of the geometry 3298881verts/8525625edges/2841875polys is nicely placed where belongs in the 3d map with its coordinates.
Please do check again and maybe it can somehow be fixed, if possible :)

Also are normals supported? some meshes seem highly broken/unwelded.

PS: Was thinking maybe support for individual elements to be exported instead of the whole CellBlock might be better? I know that means thousands up on thousands of exported geometry elements, but its easy to import in a batch only desired ones, what do you think?

potatosenpai
ultra-n00b
Posts: 1
Joined: Thu Jun 27, 2019 3:05 am

Re: ACExplorer - An Assassin's Creed .forge extractor and framework

Post by potatosenpai » Thu Jun 27, 2019 5:00 am

Hi, I cant get it to work in blender although I import all obj

PlatZ
ultra-n00b
Posts: 4
Joined: Mon Nov 06, 2017 5:46 pm

Re: ACExplorer - An Assassin's Creed .forge extractor and framework

Post by PlatZ » Sat Jun 29, 2019 7:10 pm

Hi ! When running ACExplorer.exe, programm don't open and close immediatly. I tried multiple time and it don't work.

User avatar
gentlegiantJGC
n00b
Posts: 10
Joined: Fri Nov 10, 2017 1:49 pm
Has thanked: 1 time
Been thanked: 13 times

Re: ACExplorer - An Assassin's Creed .forge extractor and framework

Post by gentlegiantJGC » Tue Jul 02, 2019 1:15 pm

PlatZ wrote:
Sat Jun 29, 2019 7:10 pm
Hi ! When running ACExplorer.exe, programm don't open and close immediatly. I tried multiple time and it don't work.
When extracting the zip file you need to extract every file together not just the exe file. Most likely you have just taken out the exe file. If you have done that there may be more information in the acexplorer.log file
Donate to support ACExplorer: https://www.paypal.me/gentlegiantJGC

User avatar
gentlegiantJGC
n00b
Posts: 10
Joined: Fri Nov 10, 2017 1:49 pm
Has thanked: 1 time
Been thanked: 13 times

Re: ACExplorer - An Assassin's Creed .forge extractor and framework

Post by gentlegiantJGC » Tue Jul 02, 2019 1:21 pm

ACExplorer V1.0.2 is now available
  • More work on the connection files - ACExplorer can now export most of the models pieced together for ACU
  • Project restructuring to makes plugins more powerful and clean up the project a little
  • Made pyUbiForge a true library that is imported and used correctly (this also means it can be used as a library outside the program)
https://github.com/gentlegiantJGC/ACExplorer/releases
Donate to support ACExplorer: https://www.paypal.me/gentlegiantJGC

Mathew1
ultra-n00b
Posts: 7
Joined: Tue Nov 11, 2014 11:30 am
Has thanked: 4 times
Been thanked: 1 time

Re: ACExplorer - An Assassin's Creed .forge extractor and framework

Post by Mathew1 » Sat Jul 27, 2019 12:53 am

Thank you for this great exporter. I looked at almost all the Data Blocks and this is what I noticed:
Invalides, Villa Arno, Bastilia, Temple, Notre Dame - blocks are exported entirely with external walls and internal walls
Pantheon, Luxembourg palace, Sante-Chapelle, Hotel de Ville, Grand Chatelet, Halle aux Bles, Palais Royale, Louve (Tuileries), Versailles palace - blocks are exported only with external walls. The internal walls are lost.
As for Saint Denis, Abbey has the opposite situation - internal walls are exported, external walls are lost. Basilica not exported at all, only empty land.
I hope this information will be useful. :)

LordMustang
ultra-n00b
Posts: 3
Joined: Tue Jan 08, 2019 7:43 pm

Re: ACExplorer - An Assassin's Creed .forge extractor and framework

Post by LordMustang » Thu Sep 19, 2019 12:03 pm

Is there a way to identify which datablock to export for specific buildings? Or does this have to be done by trial and error?

derinhalil2015
ultra-n00b
Posts: 3
Joined: Tue Sep 10, 2019 9:23 pm

Re: ACExplorer - An Assassin's Creed .forge extractor and framework

Post by derinhalil2015 » Mon Oct 07, 2019 7:59 pm

It says in the first post that it's very easy to add support for new games. How could I, an end user, help with that? I own all the AC games except Origins, Odyssey or the Chronicles games, and I really do want to help.

EDIT: I know some Python, if that helps.

Post Reply