Xaymar
This difference is not present in the other variant of the same model, which does not have this offset. Not related to the datatype?
 This dword is different at the end.
That same dword is different in every model, so probably not that?
Oh, there appears to be a lot more data for meshes that is currently ignored. Not quite sure how to parse it at all...
This may be a possible BMS export error, and not actually caused by my tool.
We've had the mesh structure all wrong, and didn't notice it until now. 1. The "offsets" entry is not relative to count, but relative to the list. 2. Each mesh...
0xA1AD36AF446FCB7D = 0x7DCB6F44AF36ADA1. Original BMS script had this set to BigEndian, but it's all LittleEndian. There are three copies of this file throughout the various data files, and only one...
Original BMS script is correct, it's easier to work with when it's big endian since the file name matches the bytes in the file. It's more like the id is...
Hashes appear to be MurmurHash(2) 64bit version. Not quite sure how to implement it, but I'll focus on proper exports for now.
When Type 6 or 7 is encountered, the data does not fit into the vertex stride anymore. They cannot reasonably exist in the same space as everything else.