mariokart64n wrote:format is strange, as we don't get much of a header to work with.
it gives a few counts or sizes for the main vertex and index buffer but then thats it
then you jump past that and land at skeleton and material data blocks and some unknown data??? I'm also missing the skeleton hierarchy info :/
anyway after which you'll finally come to the mesh table, which in most games I see are at the top with the header.
In this format everything seems in reverse, which makes my implementation very UNSTABLE.
as the format does not supply an address to the mesh table I have to parse through the material table to get to it.
The material table is dynamic, so without picking apart the material calls in a disassembler I can only accommodate what I was provided with in the OP's sample.
In other words if there is a new material call the program will land at the wrong address and CRASH :'(
I have created a 3dsmax maxscript that imports the OP's provided sample file. Probably WILL NOT WORK on other files, so don't bother trying
surely had. I manually created an array containing the parent ids (face bones unresolved):mariokart64n wrote:Anyway here I've enabled the flag for you, having fun FIXING bones:
Code: Select all
BPar_ID = #(-1, 1, 2, 3, 4, 5, 6, 7, 8, -1,-1,-1, 3, 13, 14, 15, 16, 17, -1, 2, 20, 21, 22, --23
20, 24, 25, 9, 21, 28, 29, 30, 24, 32, 33, 34, -1, 9, 37, 38, 9, 40, 41, 9, 43, 44, 27, 46, -- 47
9, 48, 49, 18, 51, 52, 18, 54, 55, 18, 57, 58, 18, 60, 61, 18, 63, 64, --65
1,
66, 67, -1,-1,-1,-1,-1,-1,-1,-1,-1,-1, -- 78
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,
-1,-1,-1,-1,-1,-1,-1,-1)
