Doom3world

We have an improved version of der_ton's MD5 exporter for Blender. It features a new interface that lets you export multiple animations.



I think there is a similar version in Blender 2.46 by Andreas 'BlackHC' Kirsch.
However it exported empty bounding boxes for the .md5anim files and I fixed that.

The fixed version can be found in our subversion repository: https://xreal.svn.sourceforge.net/svnroot/xreal/trunk/xreal/blender/blender2md5.py

nice,
will try it

That...totally rules. I wonder what the difference in code is, and if der_ton will implement it in the next version.

I'll take a look, the screenshot looks great and the usability is greatly improved for artists that do alot of exporting cycles. If it's ok for the authors I will try to bring those improvements into my next version, with proper credits ofcourse.
This was branched off at an earlier version than my current version so it will involve some careful merging there.

Does anyone know where I might find this exporter so I might hack it together with the version of the exporter I currently have?

The name apparently was changed to md5_export.py
https://xreal.svn.sourceforge.net/svnro ... l/blender/

Almost awesome, except the multi-export script seems to take whatever frames are playing on the screen and export them, meaning that you can only really export what's selected in the action editor. The animations all show up in the game as the one that was currently displayed.

Can't seem to get anything out of blender into the AF editor properly, either. Sometimes the bones are compressed in scale, or rotated the wrong direction, in odd, inconsistent ways. This is mind boggling.

My walker doesn't move when I spawn it, and I think it's because the AFs aren't set up properly, but I can't set up the AFs because of this.

Awesome.

you don't need working AF's for monsters to walk (AF's are used for some collisions I think though), you just need them for working ragdolls. But you need SOMETHING. I know I had this issue before & someone else did too, with the md5 messed up so it won't work in the AF editor properly. I forget what we did & I forget the exact thread it was discussed in, but I *KNOW* it was solved because in my doom 3 edit folder I replaced my "bumble bee" with the messed up model we fixed & I saw it last week.

Okay. I suspected as much. This morning I tried every possible way to break ETQW's cyclops and keep it from walking, but I couldn't. I always figured it was something to do with DEFs and not AFs, since making the movement based on the IK physics and not the other way around would seem to hog a ton of processing.

Uhhh, the mesh animates and runs properly, with the only issues being that it doesn't actually move in the game, and the bones rotate improperly in the AF editor.
The bodies I set up in the AF editor look completely wrong, but they latch onto the bones properly in the game.

My main issue right now is getting it to walk. Do you have anyone I can contact frequently that could help me through this? Or any def files that I could look at?

Also, what controls how vehicles collide with eachother?

I think ETQW just uses the collision models/boxes for all collision. The vehicles use a CM that's a lower-res for per-poly detection I believe.

For a quick test, try putting the model in doom 3. Replace a simple monster with the model & see if it works. If it works it's something particular to etqw.

Awesome. The movement has nothing to do with def files. It's entirely within the md5anim file. I've never seen this done before, what the hell?

If that's still an issue, does my unmodified exporter produce the same problem? Did you use scaling on the bones?