Topic: Blender to .mod scripts are there any working?

[Bonk]

Check my edits above. I think I have it sorted.

"VTX header" (actually, whole block):

Code: [Select]

    modVtxTag, \
    modVtxSize \
    = struct.unpack("<4si", file.read(8))
    modVtxStart = file.tell() 
    print ("modVtxTag: " + modVtxTag.decode("ascii"))
    print ("modVtxSize: %d" % modVtxSize)
   
    modVtx = list()
    while (file.tell() - modVtxStart < modModVerticesNum*12):
        modVtx.append(struct.unpack("<fff", file.read(12)))
    print ("modVtx: ")
    print (modVtx)


[Bonk]

Lol, see, I still have the vertices*12 in there when it can just be the size read from the same VTXS block instead of the number of verts stored in the parent geometry block. Lots of redundancy in this file format.

[marstone]

'tis looks right to me.  does this seem to read it all or missing some still?

[marstone]

Lol, see, I still have the vertices*12 in there when it can just be the size read from the same VTXS block instead of the number of verts stored in the parent geometry block. Lots of redundancy in this file format.

it has redundancies but it also allows the skipping of any part you want because it store the size of each block.  Thus you can just skip over if you don't want that information now.

[marstone]

now myself, instead of checking where in the file I am to see if I read anough, I might have gone with a counter and counted the number of verts read in instead.

[marstone]

Have fun Bonk, I'm off to work (2nd job).  Looking forward to seeing how you have done.

[Bonk]

I'm more of a "start at the beginning and when you come to the end, stop" kind of guy... (very procedural and not so o.o)

I have the all the blocks sorted out, now just to loop through each LOD properly and I'll have all the data to build the model.

[Bonk]

now myself, instead of checking where in the file I am to see if I read anough, I might have gone with a counter and counted the number of verts read in instead.

I went with this option oddly only to avoid the inadequacies of the for control structure in python (or until I grasp what they call.. umm "List Comprehensions"... yeah that's it... possibly where I will end up for a control structure)

Oh right I suppose I  can count manually in each loop, I suppose that would be more efficient than calling back the file position? (maybe not though, as the var is already there, why create another to store the same info...? - as I expect the file.tell function just returns the position value, nothing more...)

[Bonk]

Almost got all the data in... I am having to count manually in places as I loop through because of variable object sizes.   Just the LOD loop left.

Though after the trouble I went to to parse the strings out, they're probably best left as a bytestring blob since the named points and polies reference them by hex offset. Easy enough.

[marstone]

would agree with the byteblob thingie.  Would probably be easier to reference that way.

Now also, add in a check to make sure that each block is actually there.  Since you can't be sure if each block will be used (that way you don't just eat the head of the block and assume it is the one you want, never want to assume)

[FoaS_XC]

Alrighty Bonk + Marstone,

Here is a basic no-nonsense MOD file. It has a single object in it - a cube. I have listed up the XYZ, UVW, and Material data that is involved in it.

Code: [Select]

XYZ coordinates
------------------
[-50,-50,0]
[50,-50,0]
[-50,50,0]
[50,50,0]
[-50,-50,100]
[50,-50,100]
[-50,50,100]
[50,50,100]

UVW coordinates
-----------------
[33.9291,66.0709,0]
[66.0709,66.0709,0]
[33.9291,33.9291,0]
[66.0709,33.9291,0]
[1,66.8582,0]
[33.1418,66.8582,0]
[1,99,0]
[33.1418,99,0]
[33.9291,1,0]
[66.0709,1,0]
[33.9291,33.1418,0]
[66.0709,33.1418,0]
[66.8582,1,0]
[99,1,0]
[66.8582,33.1418,0]
[99,33.1418,0]
[33.1418,33.9291,0]
[1,33.9291,0]
[33.1418,66.0709,0]
[1,66.0709,0]
[33.1418,1,0]
[1,1,0]
[33.1418,33.1418,0]
[1,33.1418,0]

Face 1, 2, and 3 use MatID 1
Face 4, 5, and 6 use MatID 2

Material = Super_Mat
 - Submaterial 1 = Material_Able
 - - Diffuse Map = Map_Yankee
 - Submaterial 2 = Material_Baker
 - - Diffuse Map = Map_Zulu
 - - Self-Illumination Map = Map_Whiskey

Let me know if there is more information you need or if you want a specific criteria in another MOD file.

[marstone]

could you save it in a 3DS format also for a comparing how to import it?

[FoaS_XC]

You're going to have to fix the texture name, but here it is

[Bonk]

Now also, add in a check to make sure that each block is actually there.  Since you can't be sure if each block will be used (that way you don't just eat the head of the block and assume it is the one you want, never want to assume)

Right. I think the only block that could be missing from a model is the named points block? Or how about a model with no textures? A few samples of those kind of variations would be good.

[FoaS_XC]

Forgive the ignorance, but what is a Named Points block?

[Bonk]

Thanks FoaS!

5 LOD transitions but only one mesh? (are those 3ds max exporter defaults perhaps) LOD count is right though

My decoding choked on the materials flags... (not sure why, the file is probably fine) I think because I'm not adding the flags up right...

[FoaS_XC]

No LODs in that model.

[marstone]

the named points are the hardpoints and hit locations on the ship. IIRC

[FoaS_XC]

k, rgr that. That MOD also does not have hardpoints or hit locations - Tried to keep it as simple as possible. I can add or remove stuff as you'd like. Want a no-texture version?

[Bonk]

the named points are the hardpoints and hit locations on the ship. IIRC

Yes.

k, rgr that. That MOD also does not have hardpoints or hit locations - Tried to keep it as simple as possible. I can add or remove stuff as you'd like. Want a no-texture version?

A whole buncha variations would be awesome if it is not too much trouble. With this... without that...