Blender 3ds import script would only work for one room file. You mean, one 3ds file; this one is for multiple 3ds, the problem, as I wrote, is that it creates its "own order" (path needs adapting): import os import bpy # http://blender.stackexchange.com/questions/5064/batch-import-wavefro...

The room skeleton and meshes are in the same order Nope. For me they're not! (3ds files created with bms script). That's the reason why I need your exact process of creating the meshes (sorry, when I was unclear). It takes way too long doing it that way, would prefer a import script. As soon as it ...

well, seems you got it! All I get is a mess, more or less. This is my nearest "hit":

I copied the skeleton translation data on to one of the room meshes

Can you exactly explain that process, please?

Steve666 wrote:Also can you upload your blender script so i can try it out?

I need to find out the problem before (wouldn't like to release or pm scripts with stupid bugs ).

Maybe you can send me your "best looking" room (blender screenshoot, *.amo and *.ahi file ) so that I can test the script?

use this list to find the suiting submesh in Make_log.obj : 101-txt-vert-face-counts.zip Looks like so: RENDERUNIT INDEX: 0 VERTEX: 12 Face: 39 RENDERUNIT INDEX: 1 VERTEX: 90 Face: 240 RENDERUNIT INDEX: 2 VERTEX: 307 Face: 798 RENDERUNIT INDEX: 3 VERTEX: 360 Face: 960 [...] RENDERUNIT INDEX: 489 VER...

After I realized that blender's script generated sorted filelist spoils the indices it looks a little bit better (maybe one index off or something like that?): (I'd need an ingame screenshoot from that room to tell more.)

I see; it's required to apply skeleton data (translation from the smd file) to the submeshes, for example 20 2925.000000 250.000000 5700.000000 0.000000 -0.000000 0.000000 (so x=2925.0 y=250.0 z=5700.0) 21 2925.000000 199.999939 5250.000000 0.000000 -0.000000 0.000000 Thanks shakotay2, that works. ...

I see; it's required to apply skeleton data (translation from the smd file) to the submeshes, for example 20 2925.000000 250.000000 5700.000000 0.000000 -0.000000 0.000000 (so x=2925.0 y=250.0 z=5700.0) 21 2925.000000 199.999939 5250.000000 0.000000 -0.000000 0.000000 to 20.3ds and 21.3ds (benches) ...

Its created by someone named "The dude" I found that script here https://pastebin.com/kp1RgZNx Thanks, but I really don't get it why you removed this line from the script: #Code is by TheDude I used Noesis to create an smd from the skeleton then imported it to blender: shakotay2 that meth...

so I'm looking for someone to help finish this noesis script. i.e. a Noesis script that can import .amo meshes? (Don't want to be mean but I don't think that someone will write it. Iirc Predator created a max script/tool to import Resident Evil 5 assets into 3dsmax. Maybe it supports amo, too.) Any...

We have mesh, we have UV and texture right now, So could we improve Make Obj tool to get full mesh with texture? The tool doesn't support texture/material but for any coder it should be possible to create a suiting material file (.mtl) for blender, I guess. You can insert a line mtllib my_materials...

I've updated the code (see previous post) to load 101_type2.YOM sucessfully, though there is 8 QNANs (not a number). The correction is simple but not logical, imho. In Make_log.obj replace the 504 vertices after the two lines below by 504 lines with: v 0.0 0.0 0.0 # error vertex counts (calc versa f...

Using hex2obj (view link in my sig): The tdin files contain texture names as you might have noticed simply viewing them in a hexeditor.

( ships mesh will include flag,body.. Where do you have that information from? Can we know which submesh linked together? I have no idea. There's MESH INDEX groups in 101.txt, maybe that helps? MESH INDEX: 152 MESH INDEX: 153 MESH INDEX: 3205 MESH INDEX: 3210 --------------------- But you can simpl...

tainhx wrote:And why is 0x16ee while that address in hex is 0x16e0

what does that mean "that address in hex"?

You need to understand (read tutorials) where a face indices block starts, here is a DWord facexIndexCount (0x27) before the first face index: