Just trying out the CVS version. Demos seem to crash...

Hi! Just wanted to try out the look'n'feel of Bullet, so dled the CVS version, then the 2.63 of Bullet, compiled everything. So far got 2 questions:

1) Demo, when launched gives error at the following line. Since I didn't have a hance yet to look into the code, perhaps in there a hotfix for this?
worldTrans.setOrigin(OgreBtConverter::to(mObject->getWorldPosition()));

2) I've noticed, that upon compiling OgreBullet compiles into a fully static library. Just wondering, if the licensing supports that?

Thnx in advance!

That's the price to pay for having a physic lib frequently updated

1) yep. I'll fix that in CVS. meanwhile you have

in RigidBody::setStaticShape change

mState = new ObjectState(this);

mShape = shape;
btRigidBody *body = new btRigidBody(0.0, mState, mShape->getBulletShape ());


to


mState = 0;

mShape = shape;
btRigidBody *body = new btRigidBody(0.0, 0, mShape->getBulletShape


2) yes. it will

Whoops, been a while since I checked the demos (I am using ogrebullet extensively in my own project and it works fine). I'll fix that bug.

I think it's fine for OgreBullet to be a static library since it is not part of Ogre itself - it's an add-on. If you modify Ogre itself, you need to release source or dynamic link instead of static, but since OgreBullet doesn't modify Ogre, it's okay as a static library.

*EDIT* Oh cool Tuan Kuranes - glad you are still around to maintain. I was kinda feeling like I was suddenly the designated maintainer and I'm not comfortable with that responsibility...

Chaster

Fix in CVS. (But I think I have Bullet 2.64 here, as it's latest Bullet SVN...beware)

@Chaster: you're the main contributor and I would say that you can take design decision too (I'm keeping an eye on it anyway). And I have not much time nowadays, so...

Btw, did you see the ogre bullet terrain code in bullet forum ?

Wow! So quick! Thanks, Tuan!
Updated my files and compiled like a breeze. And I got Bullet 2.64 (its RC2 so far, according to them, right?).

Hmm, so they are discussing Ogre's code on their forum as well? Why not to discuss it here? (btw, OGRES, *lol*)
So, as I get it Heightfields aren't supported by OgreBullet, or?

Yep, and just an afterthought - while compiling Bullet itself, there are 2 options: StandardRelease/Debug and DoublePrecision Release/Debug
Just a guess, but are they talking about using doubles over floats, and that's all? And which one did you use?

- No heightfield, but if one already did it and release source, that shouldn't be hard to add it ?

- It's single precision float. But switching shouldn't be hard. A matter of using Ogre in double precision too, and link to double precision bullet.