Well, I have successfully loaded a collada model into the Desktop JPCT w/Bones. Everything is working great, and I am able to manipulate the skeleton procedurally.
Now, I want to load the same model into JPCT-AE (Android) w/Bones. I noticed, in the Android example with the ninja, you loaded a ninja.group.bones from the /raw/ directory.
In the desktop Jpct/Bones, I load my collada model, then use BonesIO.saveGroup(animatedGroup, output) to save my model to model.group.bones and then imported it into Android. The first time I did this, I got an out of memory error. After spending hours reducing the number of polygons in the model, I was finally able to get it to load in Android, but with very little memory to spare.. and my model looks quite ugly now due to the low poly count. I am wondering if the exported file is being serialized??
In Jpct-AE, it is recommended to first serialize the object on the desktop, then load the serialized object into Android. When I call BonesIO.saveGroup, does it perform this serialization step? Are there any other optimizations I should perform on the AnimatedGroup before I export it to the bones format to be loaded into Android?
Thank You