Zay-ES and Bullet physics best practices

[Ali_RS]

Here is my solution

To entity or not to entity?

Here is how I am doing physic in server side : Pretty mush similar to SimplePhysic system in sim-eth-es example. Here I am having one PhysicSpace, you can have multiple physic spaces. (They can be run multi-threaded) /** * Bullet physics system. * * @author Ali-RS <ali_codmw@yahoo.com> */ public class BulletPhysicsState extends AbstractGameSystem implements PhysicsSystem<PhysicsControlDriver> { static Logger log = LoggerFactory.getLogger(BulletPhysicsState.class); private Ph…

To entity or not to entity?

In answering another post: I did a little digging and discovered that JME’s PhysicsSpace is really the wrapper for native bullet (or in the case of JBullet the bullet engine). So it’s hard to avoid using it. @Ali_RS you might consider reposting your response over there and/or continuing that conversation. You have way more experience with bullet and Zay-ES than I do. It seems like you may have taken the final option in my suggestion on that other thread. I’d be interested to know more abo…

Yes, I took your suggestion. Thanks for your help.

Body class is same as yours

*  @author    Paul Speed
 */
public class Body {
    public final EntityId bodyId;
    
    public Vec3d pos = new Vec3d();
    public Vec3d velocity = new Vec3d();
    public Vec3d acceleration = new Vec3d();
    public double radius = 1;
    public double invMass = 1;
    public AaBBox bounds = new AaBBox(radius);
    
    public Quatd orientation = new Quatd();
    public volatile ControlDriver driver;
 
    
    public Body( EntityId bodyId ) {
        this.bodyId = bodyId;
        this.bounds = new AaBBox(radius);
    }
    
    public Body( EntityId bodyId, double x, double y, double z ) {
        this.bodyId = bodyId;
        this.pos.set(x, y, z);
    }
    
    public void setPosition( Vec3d position ) {
        this.pos.set(position);
    }
    
    public void setRotation( Quatd rotation ) {
        this.orientation.set(rotation);
    }
 
    public void integrate( double stepTime ) {
        
        // Update the bounds since it's easy to do here and helps
        // other things know where the object is for real
        bounds.setCenter(pos);   
    }

}

Are you effectively keeping a physics-only set of spatials?

Only if we want some kind of mesh accurate collision shapes.
No needs for primitive ones.