XeNTaX

Is this model broken or the way it's supposed to be? EDIT: Wrong link, fixed

snowboundmage wrote:Is this model broken or the way it's supposed to be?

Code: Select all

http://www.mediafire.com/file/129gymmfkzyp0f3/000000000002ad2b.dat

EDIT: Wrong link, fixed

Congrats, you found a completely new vertex/UV format.

Added support.

Edit: newer version below.

In archive that I already post were some mistakes in models - see picture above. I'm completely forgot about it...
Here link to archive (again), filenames Adam_hand and Adam_suit (overlapping/incorrect scaled UV's, missed geometry(?) and "separate mesh layer" not import some parts of model)

P.S. Now it's crush with enabled "separate mesh layer" (model AlexV.dat from this archieve)

Thanks for letting me know. I'll take a look and see what I can do.

Ok, as for Adam_suit. there's nothing wrong. That's simply all that's in the file. I suspect either the Trenchoat is in another file (since you can change trenchcoats from settings), or because it's flexible cloth, is generated on the GPU. But there's nothing wrong with the file import.

As for Alex_V, the error "Context is Incorrect" indicates you weren't in Object mode when importing the model. Maybe Edit mode, or Weighting mode, or Posing mode. My script is dumb on that, and expects Object Mode. Next version i'll add code to Force Object mode for cases like this where people forget. Model imports fine when in object mode.

Lastly the hand UVs. I see the same you see. I'll investigate it further, but I suspect this is how it's supposed to be.

If you look ingame:





Those parts are a high shine metal only, no real texture. They use varying sizes of UV to vary the scale of a scratch-map and that type of thing. It's a common technique. However, I want to be double sure, so I'll verify this model is coming out right. It's also possible this model uses multi-material (which would be the first I've seen for Deus Ex:MD, I've seen it in Hitman 2016 a lot.) if there is a texture for this part of the hand, it would be helpful it you can point me to it.

Edit: yes I've verified, the UVs are correct. There's only one scaling factor and one block of UVs for that whole object. That's how the Devs made it. (for better or worse )

Minor update to importer.
- Ensure Object mode is active before attempting import
- Validated functionality back to Blender version 2.70 (oldest supported)

Edit: newer version below.

Found Alex. Anyone know where her hair is?

Hi folks, noob here, anyone know where the audio, or more specifically music files are?

Chiff wrote:Hi folks, noob here, anyone know where the audio, or more specifically music files are?

Seems like music is contained within the .pc_fsb files within the runtime directory, not sure if they're encrypted.

Dawn engine is built on the Absolution version of G² engine, and seems to be using FMOD.
[assembly:/sound/localization/dialogue/french/barks/ai/uniques/slaw/slaw_civalert.wavebank].pc_fsb

On that note, has anyone seen the Helle / Eliza Cassan's model? Apparently it's in the game.

Hey, another noob here. So, maybe I'm missing something obvious and/or am just stupid, but... could somebody tell me the step-by-step process of extracting all models and textures from the game? I'm still fairly new to all this, but I'm eager to get my hands on (and make use of) some of the models.

(On that note, I don't suppose anyone's thrown together a pack with all the weapon models and textures yet? Because that's my #1 priority.)

SmiffinWeffin wrote:Hey, another noob here. So, maybe I'm missing something obvious and/or am just stupid, but... could somebody tell me the step-by-step process of extracting all models and textures from the game? I'm still fairly new to all this, but I'm eager to get my hands on (and make use of) some of the models.

(On that note, I don't suppose anyone's thrown together a pack with all the weapon models and textures yet? Because that's my #1 priority.)

Here's a super quick breakdown.

Step 1. Extract the Game_Layer Archive using QuickBMS & the QuickBMS script, it should be the biggest file.

Step 2.
* Find all models using the model finder tool posted in this thread. They're normally .dat files.
* Convert all the .vap files extracted to .dds files using the texture tool posted in this thread.

Step 3. Open the models in blender using the blender addon.

https://sktest.aruarose.com/DXMDExtract_v002.7z

Due to the nature of the asset names, it produces filenames like "00BB10BBA81D424A.bin".
The actual names and their matching hashes go into NameMap.txt.

hhchunter wrote:

SmiffinWeffin wrote:Hey, another noob here. So, maybe I'm missing something obvious and/or am just stupid, but... could somebody tell me the step-by-step process of extracting all models and textures from the game? I'm still fairly new to all this, but I'm eager to get my hands on (and make use of) some of the models.

(On that note, I don't suppose anyone's thrown together a pack with all the weapon models and textures yet? Because that's my #1 priority.)

Here's a super quick breakdown.

Step 1. Extract the Game_Layer Archive using QuickBMS & the QuickBMS script, it should be the biggest file.

Step 2.
* Find all models using the model finder tool posted in this thread. They're normally .dat files.
* Convert all the .vap files extracted to .dds files using the texture tool posted in this thread.

Step 3. Open the models in blender using the blender addon.

Exactly what I needed, thanks!

Sir Kane wrote:http://sktest.aruarose.com/DXMDExtract.7z

Due to the nature of the asset names, it produces filenames like "00BB10BBA81D424A.bin".
The actual names and their matching hashes go into NameMap.txt.

Where was this 6 months ago?
But seriously, how is it determining the original filenames?

If you mean the asset names in NameMap.txt, those come from the pc_headerlib files.

I also figured most of it out a while ago, but never got around to make a fully functional tool.