This is the code that I use, minus some inspection infrastructure to find the conrtols:
System.out.println("**** Run animation:" + animationName);
// Go through all of the controls that have the animation
for( AnimControl control : animControls.get(animationName) ) {
int count = control.getNumChannels();
AnimChannel channel;
if( count > 0 ) {
// Reuse the channel from before
channel = control.getChannel(0);
} else {
channel = control.createChannel();
}
channel.setAnim(animationName);
}
Unzip it inside your Models directory to have textures import correctly. so the directory path should look like: assets\Models\Models\Players\Jo Sang\cadnav.com_model\Jo Sang
1-I also tried with this release : SDK alpha 4-SNAPSHOT
it also did not play animation in scene composer. So the problem is not related to me using nightly version of netbeans (3/30/2016).
2- The model above contains .blend and .j3o with textures also license file(from cadnav.com). it is rigged and animated with Mixamo Auto Rigger.
3- meshes do not use shared material.
4- .blend converted to .j3o in alpha 4.
5- the animations plays OK in SDK scene composer for versions previous than SDK alpha 4.
6-Also animation plays OK inside game in alpha 4.
7- Have any question yet ?
Well, there was a cloning issue⌠but it would have thrown a big nasty exception. So unless the SDK code is hiding some exceptions when cloning then this was maybe not the issue here.
Iâve just committed a fix for the cloning issue that I saw. Basically, the clone of SkeletonControl was getting confused and think the materials were shared when they werenât. (Mostly because Material is not yet cloned with the Cloner.)
Well that would require a huge refactoring and the idea currently is that the code manually logs exceptions where needed and sucks up the other ones.
Other ones would be for example an multiple-lines-long Exception for each not found Asset, small Bugs in the SDK etc, so itâs best to hide them and properly implement Error Logging.
On the Other hand when you run the SDK in Netbeans, every Exception is logged, so itâs good for Debugging Purposes.