Miss F Mexzoo Added Upd Direct
I should start the text by stating that Miss F Mexzoo has added an update. Then detail what the update includes. It's important to mention specific improvements or changes, even if hypothetical. Maybe add some benefits of the update and perhaps a note for users to check the latest version.
First, I should determine the context. Maybe Miss F Mexzoo is a team leader or contributor to a project. The update could be a new feature, a patch, or documentation changes. The text should reflect the impact of this update. miss f mexzoo added upd
I need to consider possible scenarios where someone named Miss F Mexzoo is adding an update. This could be in the context of a project, a website, a software application, or even a personal blog. Since the user didn't specify, I should make some educated guesses. I should start the text by stating that
Finally, wrap it up with an invitation for feedback or further questions. Keep the tone professional yet approachable. Let me structure this step by step to ensure all points are covered without missing any key elements the user expects. Maybe add some benefits of the update and
I need to make sure the language is clear and positive, highlighting the value of the update. Also, check for any possible typos in the original query, like "mexzoo" which might be "mexico" or another term. But since it's likely a name or handle, I'll keep it as is.

Cool, Good Job!
#2 posted by
kalango on 2020/01/14 15:15:32
I'll probably maintain my fork still, but I'll probably get some queues from this, thanks!
Btw I'm not really doing anything for QuakeForge, just forking their initial code. I have my own roadmap for this, which might be more Hexen II focused.
#3 posted by
misc_ftl on 2020/01/15 17:42:39
Does this generate the bunch of QC code necessary to map frames? :D

Not Really
#4 posted by
kalango on 2020/01/17 16:09:41
But thats a good idea. When exporting is done I might add that in eventually.

Exporter Released
#5 posted by
kalango on 2020/02/18 01:52:45
Alright, just in time for the Blender 2.82 export is done. Big thanks to @Khreator for giving a great insight into exporting issues.
List of features:
+ Export support
+ Support for importing/exporting multiple skins
+ Better scaling adjustments, eyeposition follows scale factor
This is still considered an alpha release. But it should be good enough.
For info, roadmap and download you can visit
https://github.com/victorfeitosa/quake-hexen2-mdl-export-import

What Is Ask Myself
#7 posted by
wakey on 2020/03/04 00:36:49
for a long time now: Would it be possible to save a blender physics simulation as frame animated .mdl/.md3?

#7
#8 posted by
chedap on 2020/03/04 03:28:44
Enable MDD export addon. Export your simulation to MDD. Remove the sim from the object. Import MDD back into your object. You now have all of your sim frames as separate shape keys, ready to export to .mdl

Actually
#9 posted by
chedap on 2020/03/04 04:19:34
Disregard that. It works fine without any of that extra voodoo, just export whatever straight to .mdl

Niiiice
#10 posted by
wakey on 2020/03/15 18:45:39
Then let's think about practical use cases.
First think that comes to my mind are death animations, sagging bodies.
Explosion debrie might also work out.
I guess anything fluidic is out of question, like a tiling wave simulation anim.
What else comes to mind?
#11 posted by
misc_ftl on 2020/03/16 16:21:57
Flags, fire, chains, breaking doors, breaking walls, etc.