Introducing DynamicAnimControl


The physics specialist wants to drop both jme3-bullet and jme3-jbullet. Minie is the future of physics in JMonkeyEngine—unless @pspeed publishes a physics engine.


I guess we were given the link to the modified code that JME uses and then no one did anything with it. I’m asking if I can have the link again.

jbullet still works better for me. native bullet has a weird bug with the catch-up stuff that means I always have to run it single step. It’s weird because I’ve looked through the C++ code and I can’t spot the problem.


Source code for jbullet:


It’s great that you found the source code. You’re probably right that maintaining 3 libraries will be difficult for one person.

As for which libraries should be included in JME 3.3, I think that discussion belongs in a different Forum topic.


The pull request is integrated into jMonkeyEngine’s master branch!

Quazi reminded me that DynamicAnimControl (DAC) ought to have a page in the JME Wiki. To that end, I would like a few new users—alpha testers, in other words—to help me see the software with fresh eyes. The usual deal: as long as you’re using the software and providing feedback, I’ll support you as best I can. Send me a private message if you’re interested.

I expect the main hurdle to using DynamicAnimControl at the moment is configuring it for new models. In parallel with the documentation effort, I plan to write a configuration tool. The current tool (TuneDac) is an ugly hack, not worth documenting. And while I am gradually adding DAC tuning to Maud, Maud is a general-purpose editor, which makes it unnecessarily complex for this task. (Maud is also a long way from supporting the new animation system.) I foresee an immediate need for a tuning tool that’s simple and easy-to-use and can be made to work with the new animation system.


I hope not. Some of us cannot use jbullet.


Minie have updated/fixed bullet native library(same as JME have). No need drop, just update with Minie changes into it.

As i understand @sgold added jme3-bullet package classes for a DAC, but to have more features from Minie, why not just update [jme3-bullet-native] and state that all features from “some new minie related package” require use of jme3-bullet-native and will not work with jme3-jbullet.

its like “for android use android packages”, because also non android will not work… or “dont use both native and jbullet because it will not work correctly”. So same could be here “dont use minie package with jbullet”

Because as i see, jme3-bullet-native is not updated to required changes. In Minie there were not just changes to allow use of Minie, but there also were some fixes for physics. (that even if someone will not use Minei features, it will fix some problems for physics itself)

@sgold, i will check everything later myself, because what i need are ragdolls(half ragdolls, legs positioning and some nice features) as you already know, but after i will finish what i started.


Please take your discussion of physics libraries to another topic. This topic is about DynamicAnimControl.


A first draft of the DacWizard tuning tool is available from GitHub:

Current status: a cute toy. The “easy” parts are done: load a model from the filesystem, select which bones to link, configure the links, and write (Java) configuration code to a file.

Now comes the “interesting” part: automatically estimate range-of-motion from animation data…


I solved the interesting part. DacWizard is now ready for use.

I uploaded a walk-through video to YouTube. Take a look:

Puppet model was created by Nathan Vegdahl
and is © Copyright Blender Foundation

The Blender Foundation released Puppet under a Creative Commons Attribution 3.0