Little update since the last one (of Feb 15).
I fixed a issue with joint finalizing, this took me a lot of time to figured it out.
I have a question about the serialization of a PhysicsSoftBody.
Why serialization isn't easy : because the whole softbody structure need to be saved.
For example imagine an elastic rope attached to two walls. First we need to save positions of the rope, then we also need to save it's "elastic" propriety. But we also need to save its forces that prevent the rope from touching the ground, and maybe also it's masses, velocities, ect ...
I see three options :
- pro : easy, serialize only the "initial" state by the user code.
- cons : no serialization
do it in jme
- pro : yeah serialization, and access on the saved data
- cons : huge amount of work, some values are not used on the jme side but still need to be saved.
use bullet internal serialization
- pro : yeah serialization
- cons : only binary saves, can be problematic if bullet's serialization change, have to deal with joints.
IMO it is ok to not serialize a PhysicsSoftBody, and to just save a "initial" state. For the elastic rope example this would a straight line. And maybe this can be by default implemented in the SoftBodyControler.