[...]and saves a bit of time a bit? :D Seems you've got a faster method for these corrections by Make_H2O: 0. -32, last addrFI (act.): 5700 (5700), vStart: 14c0 CORRECTION vertex count (944->937)! 1. 196496, last addrFI (act.): 3c580 (3c580), vStart: 6c80 -- 2. 173312, last addrFI (act.): 3c580 (3e...

the sample from the first post: H2O files:
http://www.uploadmb.com/dw.php?id=1433708887

use them with hex2obj as explained in attachment of previous post.
(rename .objx to .obj)

cool colors! Like it. Here's a Make_H2O.exe for Wipeout - tested with Feisar only. (As you know you'll need Hex2obj_0.24 x .exe for correct uvs.) Make_H2O-Wipeout.zip Four H2Os are corrected by Hex2obj and the resulting obj files renamed to .objx . Simply rename them back to .obj . (Too tired to che...

yeah, data alignment is a feature of Make_H2O, but it doesn't work here. I calculated (where FVFsize is former VBsize, and next_FIaddr is reduced back to address with first non zero byte) vertexCount= (next_FIaddr - addrVerts) / FVFsize but works for a few H2Os only: 0: CORRECTION vertex count (344-...

i'm glad no one was able to help as going trough all of the process to extract it learned a lot That's great, really. :) (Most users lack of such attitude but we wouldn't need forums like this one if everyone did as you did.) supposed that if you need something to be done do it yourself. This sound...

yep. When it's zero I used the previous type in Make_H2O
It creates 33 H2Os automatically.

Sadly the vertex counts differ by 3 or 4 from the correct ones (which are in your uploaded H2Os).
Any ideas?

I managed myself thanks for no help :wink: Welcome to the forum and first of all: please change your attitude! From your opening post with no sample attached, no further hints you can't really expect someone to deal with this. Maybe there was no interest in the subject. (But I guess it's not help y...

Maybe i'm wrong and it means something else. Don't think so. Great find! From the table at 0x500 it looks like there are 14 objects: 0 v: 344, FI. 702, 1230 1 v: 344, FI. 702, 3610 2 v: 232, FI. 714, 5a10 3 v: 472, FI. 1056, 7130 4 v: 1264, FI. 4455, 9c50 v: 496, FI. 1083, f530 6 v: 1256, FI. 4749,...

Feisar has 17 objects. thx! (I'll look at this after "the game is over" - Barca versa Juve) Edit: Seems i was wrong about the data a couple posts ago? The more I look at it the more I get confused. In Feisar's ship model it says that there are only 14 objects but I found 17? Who is "...

Thanks, it works great. yeah, that's true. :D Tried out your Feisar H2Os with File/SaveAs M mesh (version 0.24 x required) then used load_multi_obj_blender2.49.py from the Make_H2O project to load all created obj files at once. An object and it's submeshes will all fit together, but the next object...

The messes don't import at the proper places so those need manual adjusting yeah, that's "messing" :D Does it apply to all submeshes of a spaceship? the meshes are ShortAll with HF UVs so manually fixing about 30+ objs is very time consuming. I've PMed you a quickhacked version that shoul...

using hex2obj (view link in my sig): (two submeshes, 2 left?)

same result as with hex2obj ver 0.22c, 'cut' on (obsolete):

the mesh is very likely to be found in the block from 0x0 to 0x3CBF. Try shorts, not half floats: sword.JPG To get rid of the squared structures try subtracting/adding half value of the bounding box values. (that's how I did it in former versions of hex2obj using the 'cut' feature, iirc) (some fidde...

thx! Seems I've a bug with the uv's blocksize in uv preview of hex2obj.

(so with a VBsize=8 and UVB=4 it skips the 2nd (identical) t-verts what it shouldn't)