Kneesnap wrote:Could someone help me fill in the rest of the data to get a complete model?

This is what I get: Seems to use quads for faces and needs face indices offset (74).
hex2obj uses both but not together, that's the problem.

for 12.skn it works like this:
from the vertex start address search for FFFFFFFF

After thousands of finds you'll experience a gap: Subtract the start address from the gap address; divide the result by the stride (48) and your done.

i`m sorry, can u please point me to the address where i need to add zero bytes. really struggling to find the address of the known block (vertex or face indices) You could use hex2obj to get an idea of the start/stop addresses: ( PC18Body.vkm ) PC18body_vkm.JPG vertex start 0x78: 0x78 + 44 x 307 = ...

I just hard time for the wipers, and there is sometimes some parts missing in the dashboard (for example impossible to find a part in the dashboard of the camaro zl1 2017, the back or bottom of the thing blowing the air, and the speakers). if you sent me the concerning modelbin files I could check ...

It's 0.811206, -0.740454, 0.601394 for the doorHandleLF , works like a charm, then, door position ok. And you don't have a problem ( mentioned here ) with RF door parts position in Blender?.. well, from a sideview it looks ok; apart from that frayed edge (caused by the parenting, I guess?). But yes...

@shakotay2 are you shure that you haven't accedntily used the apex one again? Because they both have the same filename very unsure :D ; fixed with -jm9; thanks for reporting! sure man sure still waiting for the final "automatic positioning" feature :-) This will not become part of the Make_H2O-Forz...

well, stupid me forgot to swap y and z for blender, how poor :cry: It's 0.811206, -0.740454, 0.601394 for the doorHandleLF , works like a charm, then, door position ok. (rmh, seems noone is really interested in automatic positioning any more, well I leave you alone with this, since I gave the idea h...

I'm not sure if anyone took care for the positions of movable parts seriously; the problem I see is that the bone's tail position (boneDoorRF here) and the doorHandleRF location don't fit exactly when placing manually. (other than the mesh the bones aren't un-mirrored so far, so LF and RF are swappe...

could there not be made a script that applies and generates the materials wich are listed at the line where the material name is listed? For FH3 this is not as easy as you may think of. Have a look at Andrakann's post: http://forum.xentax.com/viewtopic.php?f=16&t=4256&p=126817&hilit=+pretty#p126817...

very simple format:

blacksuit, after some manual erasing:

I can't show something for Noesis, but the playerGoblin:

Make_obj-SPMan3.zip I've updated the source code for extracting an obj model from [CITY_PARAMEDIC-] dbd91b3e.36 which you need to extract from CITY_PARAMEDIC.PCPACK using chrrox' quickbms script. The code can handle this one model only atm. (Feel free to expand it for other .36 models.) This is a s...

Generally I show how it works for one submesh of one model then leave the rest to the customers.
(In this case I might add it to my MakeObj project. Without getting the textures automatically.)
For coders only:
viewtopic.php?f=29&t=15955

had to put a threshold into the uv pos routine to get better results; still very ugly: (since I'm not too familiar with textures, mipmaps, etc)