Here's my updated application that displays information to quickly compare with other car sections. Just load either an lod0 or cabin .carbin file and click through the treeview. It might require you to install xna framework redistributable 3.1 since I started adding basic render code. The source is...

The header has two suspicious floats located at 0x2B0 which I suspect are probably related to the two unknown lists that follow. There are other floats in the header, but I haven't noticed any changes in the dozen or so files I've compared with. Then in the beginning of each main section there are 1...

You could possibly be rendering different permutations of the same section. Also, there are lots of unknown float values that I haven't really done much with so maybe the vertices are bounded and/or scaled for extra precision too?

The index data is separated from the vertex data, and is in the form of a list of 0xFFFFFF delimited triangle strips. Each segment piece has it's own indices that reference the bigger vertex block of data for each main segment. The image he showed just might not be rendering all of the parts of the ...

Much appreciated . I'm at work right now so I won't be playing with this to later but the other information might be related to the Granny 3D library as I've found references to it in the .xex

Been busy lately, so I haven't been able to work on this as much as I'd like, but I know enough to fully parse through lod0 and cockpit .carbin files so here's a little stubbed out application written in c# where you can experiment with decoding vertices or other information... http://67.176.205.173...

It's actually quite common for programs to pack floats into 16-bit integers. When relative to a bounding box, they can be just as precise. The extra processing power is also pretty negligible compared to the amount of time saved from cutting disk access in half. Now this might not be the case here, ...

Yes, I've obviously analyzed it enough to determine that they aren't using the standard floating point format. I've scanned for singles and doubles in either endian format on every byte boundary. It is probably fair to assume the first values are xyz coordinates, but I'm not sure if they are 4-byte ...

You'll need to read the "Extraction" section and download Aluigi's QuickBMS and the zip.bms script in order to extract the archive. The good news is I've been able to figure out most of the .carbin layout since my last posting, with exception to everything before encountering the first car...

The contents of this post was deleted because of possible forum rules violation.