No, I didn't use MR - some C coding on the fly using floats. But obviously I'm missing something - the vertices need a special treatment, I guess. Maybe sort them by those "indices", 0x20, 0x40, 0x80...? Or use a threshold (that worked for a 3D format with a similar problem), at no avail h...

Guess, you'll need to use Bigchillghost's AMR. . 116_hex.png This is for "hanging platform", black rectangles contain the first vertex (doubles). edit : had to correct this from "floats" to "doubles" (big thanx to Bigchillghost for the hint!) Face indices start at 0x31B...

4000-4500

Nice script! Position offsets would be nice, too, to not have the meshes clumped:
.

Using hex2obj (view link in my sig)
. (One submesh only.)

Getting some vertices (search for "array/vertex") from 116 file ("hanging platform"): . hanging_platform.png Seems there's an issue with the faces or - more likely- I accidentally used vertex colors for scaling (per vertex!, hahaha). Without this it looks different (right part of...

Several smaller submeshes, no time for fiddling.

Here you go: . birdhouse_point_cloud.png Hex2obj will give you a point cloud only. Getting the face indices requires additional coding which I did "on the fly": # f 1 5 4 f 2 3 6 f 2 6 5 f 3 2 1 f 6 4 5 f 7 8 12 f 12 11 7 f 8 10 14 f 14 12 8 f 10 9 13 f 13 14 10 f 9 7 11 f 11 13 9 f 15 17 ...

"birdhouse" looks like a birdhouse using faked face indices - don't have the time to get the correct ones:
. (FIs seem to be contained in the "3DMa" blocks. Well, couldn't resist... see right part of picture)

No. I don't have the time for fiddling any more - just working on models when there's sufficient infos.

Here "I only have that wheel file mrstyx extracted" where he said it's modified then vanished (for ever?).

Bad base to keep my interest, sorry.

No, you are not. (Contents of extracted files is different. Same size, though.)
. Small submeshes, much fiddling required...

that's weird but if you look at the test.obj, it's not surprising: # 0xd73275: verts= 1756 v 0.527344 1.035156 1.232422 v 0.559082 1.032227 1.224609 v 0.552246 1.058594 1.142578 v 0.274902 1.058594 1.283203 v 0.408691 1.047852 1.262695 v 0.274902 1.086914 1.200195 v 0.406494 1.075195 1.179688 v 0.14...

yeah, there's spoiler bytes in the FIs' block, what the heck. Here's the missing sub mesh I spoke of in the post before: . kluns_FIs_spoilerbytes.png So you have to make two corrections to the FI count here! From car_template.kluns_17.h2o, FIs start address and (assumed) count: 0xf5c6da 29664 spoile...