OpenArena Message Boards

If you've still got Preach's blender MDL exporter then stick it on speedyshare or commit it to OQ+ svn and I'll try to get it working properly, but no guarantees.

hard drive search commenced

p.s. You should really base it on the md3 exporter, as the mdl exporter was based off the very broken md2 exporter shipped with Blender. Some specs:
http://tfc.duke.free.fr/coding/mdl-specs-en.html

Current MD3 exporter:
http://openarena.ws/board/index.php?topic=2139.0

2/12/2008

Cheers.

Yes I'll base it off the MD3 converter, but having the MDL export code will save A LOT of time.

Does blender let you assign properties (name/value pairs) to a whole model?  This would be useful for various things (model flags, synctype, whether to use fullbright pixels).

afaik no
also mdl stores images inside dunno how to do it in python
2-step process might do it
1) export blah.mdl without textures and flags
2) use "mdlBlah.exe blah.mdl blah.cfg" where blah.cfg contains images paths and flags per surface, and mdlBlah.exe pushes them inside the blah.mdl

skin width and height would need to be explicitly defined in the mdl as well for the uv maps to be consistent

I've been considering that, mainly because processing of the skin texture by Python code is really slow.

But I'd prefer to keep it as simple as the MD3 exporter.

I have learned that you add Empty objects to a scene and give them arbitrary names.  So I'll use them to control those niggly little things.

Menu -> Help -> ID Property Browser, you can set custom values for objects, materials and other things
then in the python script you can use object.properties or material.properties etc
those give http://www.blender.org/documentation/246PythonDoc/IDProp.IDGroup-class.html

They put this in the Help menu?
WHAT ON EARTH WERE THEY SMOKING???
(That goes for the whole crazy blender UI)

Anyway now I've got that out of my system, thanks f0rqu3!

Getting there......

(http://glbsp.sourceforge.net/shots/ajmdl_boss.jpg)

lol
is it gargoyle?

He's a CHTHON replacement in the OQ+ tree.

His face got messed up by poly reducer (too many verts in the original).

MDL should support lots of verts
you could also test a model that doesn't have a fullbright skin, like a weapon model

No more than 1024 in id's GLQuake.

Weapons seem OK:

(http://glbsp.sourceforge.net/shots/ajmdl_vrock2.jpg)

that is cool, i can see goraud shading (!!!!)

How does it look in software though? Software is a target too

Try it yourself, here is pak2.pak with progs/boss.mdl and progs/v_rock2.mdl:
http://glbsp.sourceforge.net/files/pak2.zip (http://glbsp.sourceforge.net/files/pak2.zip)

There's a rocket launcher near the start of E1M5, and CHTHON is E1M7.

Also included is the unfinished export script.
Target gamma is hard-coded as 0.5, and fullbrights are OFF.
Works just like the MD3 exporter.

holy crap this script saves a lot of time
is it possible to make it read a palette from a palette.lmp file, if available in the same folder of the model or so?

Which palette?  If just Hexen II then I'll add it directly into the script.

BTW I think the normals are not right, when I find a good way to test them I can fix it.

I think fromhell mean a generic palette (maybe you can have more than one palette)

Oh and I hate normal packing of q1/q2/q3
it is the worst in q1 You need <float float float> to index[ int ]
(I read your code and it should work. dunno. Check md2 exporter[probably you did ])
I was lucky because there is r_shownormals in q3

in the future i might make mini-games on the base engine using completely new palettes from scratch (for competitions) due to the recently reworked pipelines

A seperate version with the Haktoria palette integrated could be great

OK will do that soon.

It will only be useful for quick prototyping since I haven't added a
gamma setting yet (still hard-coded at 0.5).

Haktoria Palette Transplant complete, but not tested in-game.

Edit the script and search for 'DEFAULT' if you want to change
the hard-coded target gamma and/or fullbright mode.

After re-exporting fired guns weapons I've noticed the UVs shift 1 pixel to the left
this is a bug

anything on the fact its vertically flipped along with the skin? that's unnecessary
the whole gamma thing can go too

Noted.  I'll be working on the exporter again soon.

Also one pixel upward too.

Blender is unusable on my currrent hardware (menus are not drawn).
Time to upgrade heh.

Blender no longer runs on my G4 macs either.

do you mind if I post this exporter with a page somewhere?

no prob.

Try this one, no gamma fiddling, inverted the skin, did something about the off-by-one UV coords (dunno if it worked or not, let know).