Battlezone Forums

MSH parser is pretty good, though I could refactor it a bit.
Writing the XSI is a massive pain in the ass.

The MSH data is optimized for rendering, which means lots of unrolling data, etc.
If anyone has some code/structures that represents an in-memory XSI style model layout, pass it on. I am getting a bit tired of working on this after a week.
(Ken has helped a lot in understanding the render optimizations in place in the MSH. Having never done programming for 3D that required speed, it was a bit weird to me.)

I think I can resolve the broken mesh problem OM's exporter had, though I currently have it myself (the verts/faces are in two places, I am using the flawed (for MSHs made 1.2 and earlier) data in this case). Oddly I can't find the cockpit mesh in either, but its probably an issue with how I am unrolling the data or stepping the tree or otherwise linking the different data-sets.

that looks nice, n1.

Ah, so it no longer crashes 3Dex? Progress

Also, will you be keeping this closed and to yourself? I liked the way Overmind did it; I realise it's a little less than necessary now but it still feels like the right thing to do.

Never crashed 3Dex, still crashes DEEPex.

I will distribute the compiled program and its source-code to specific individuals.