XeNTaX

Kanbara wrote: ↑Wed Apr 15, 2020 11:27 am The trees are existing in the map, which leads to the whole map unreadable.
I don't know wheather i've make myself clear

daemon1 wrote: ↑Wed Apr 15, 2020 10:59 am

Kanbara wrote: ↑Wed Apr 15, 2020 6:51 am The updated tool extracts the models without giving the information "Unknow bones format 6" like the old tool.

This is because new tool now supports bone format 6, its used on PC for characters.
Trees use "bone" information to store additional UVs, which is not expected by the tool. So output files are not readable.
I didnt think anyone really need those trees, whats so special about them?

daemon1 wrote: ↑Fri Apr 17, 2020 6:34 pm its this:

detroit_anim.exe 1A0.anim D0F_553.nodes

kotn3l wrote: ↑Wed Sep 04, 2019 12:43 pm

gabz wrote: ↑Wed Sep 04, 2019 12:34 pm Thanks for the links, it was just a misread from me as I mentioned.

I’m not lazy, I have read all the 12 pages multiple times.

Video isn’t publicly accessible.

Thanks to all of you I know how to extract. But my question was more oriented on how to do with objects that are not mentioned in the files_list, such as map objects

I think all objects, sound, and etc memory addresses are stored in list.txt. Use those, not detroit_file_list.txt. They're not named, so its a guess game, but I managed to find the police department object, the whole city, and some houses.


I suggest importing the list.txt into some database management program (or even excel maybe), and sort them by size, and maybe delete the ones that are already in the detroit_files_list.txt so you won't accidentally extract something you already have. (Characters are pretty big in size!!) Cheers.
Some memory addresses will return an error (unknown files), these are probably the sounds/videos etc, skip them.
I'd still be interested how to extract sound though.
EDIT: I think I found a test-map, it is at the '5' memory address

set mypath=%cd%
for /F "tokens=*" %%A in (files.txt) do call :process %%A

:process
SET _modelname=%~1
START /WAIT "" /D %mypath% detroit.exe %_modelname%
IF EXIST %mypath%\textures (mkdir %_modelname% & move textures %_modelname% & move %_modelname%_* %_modelname%)

Bladers wrote: ↑Sat Apr 18, 2020 2:08 am So the output is .SMD
I ended up using a source engine plugin for smd.
But each animation i try to import looks like this and i get the error "SMD only supports 128 bones."

anahush wrote: ↑Mon Apr 20, 2020 10:58 am Actually, I've got the same problem with animations.

daemon1 wrote: ↑Mon Apr 20, 2020 11:19 am As you can see, this is a problem of 3dmax and/or its plugins.

anahush wrote: ↑Mon Apr 20, 2020 11:37 am The animation is exported correctly, yes, though it can't be only 3dmax problem as it also seems to be wrong in Blender.

daemon1 wrote: ↑Mon Apr 20, 2020 12:11 pm For blender i can tell you for sure, it works correct. You can see it on my screenshots and videos.

ProGamer wrote: ↑Mon Apr 20, 2020 8:59 pm First import the animation into Blender Before confirming, check this box
Make New Armature
Import the animation you will have the skeleton Then import your model Select the rotation of the skeleton X -90 So that it is positioned on the model Make a CTRL A Once everything is selected, make a CTRL P and choose Armature Deform Now your model and well animated I hope to have helped you

Thanks, worked like a charm! I had to scale my animation skeleton 100 times before doing Armature Deform part and now everything finally is correct.

ProGamer wrote: ↑Mon Apr 20, 2020 8:59 pm First import the animation into Blender Before confirming, check this box

Make New Armature

Import the animation you will have the skeleton Then import your model Select the rotation of the skeleton X -90 So that it is positioned on the model Make a CTRL A Once everything is selected, make a CTRL P and choose Armature Deform Now your model and well animated I hope to have helped you

anahush wrote: ↑Tue Apr 21, 2020 8:32 am Thanks, worked like a charm! I had to scale my animation skeleton 100 times before doing Armature Deform part and now everything finally is correct.