Apparently nothing has been researched in terms of this game's file formats. Here we have what I believe to be the model and texture files. Not sure if they're archives or otherwise. Can someone see if these can be converted to something useful?
https://www.dropbox.com/s/w1krf1e27v43ovb/C_daemon.zip?dl=0
Warhammer 40K: Fire Warrior (*.geodx, *.tgdx)
-
- Posts: 376
- Joined: Sun May 31, 2015 2:23 am
-
- Posts: 706
- Joined: Fri Aug 08, 2014 1:06 am
Re: Warhammer 40K: Fire Warrior (*.geodx, *.tgdx)
first submesh of c_daemon.GeoDx with inverted normals

the face indices for each submesh are clearly separated by 00 00 01 00 02 00 so it looks like 47 or so
c_daemon.TgDx is an uncompressed archive of dxt3 textures. you can separate these by hand and add a proper header if there is no other way to extract them. each texture begins with a 24 byte custom header starting with ELEM that probably has the type, width, and height of the texture data that follows.
the 24 byte texture header looks like this to me
4 bytes - ELEM
4 bytes - length of data starting immediately after this
4 bytes - type?
4 bytes - width
4 bytes - height
4 bytes - ?


the face indices for each submesh are clearly separated by 00 00 01 00 02 00 so it looks like 47 or so

c_daemon.TgDx is an uncompressed archive of dxt3 textures. you can separate these by hand and add a proper header if there is no other way to extract them. each texture begins with a 24 byte custom header starting with ELEM that probably has the type, width, and height of the texture data that follows.
the 24 byte texture header looks like this to me
4 bytes - ELEM
4 bytes - length of data starting immediately after this
4 bytes - type?
4 bytes - width
4 bytes - height
4 bytes - ?