Real-Time Physics Simulation Forum

TriangleCallback takes a partId and triangleIndex which if I remember correctly are populated as part of the normal processing, that might give you what you need.

btTriangleCallback.h
virtual void processTriangle(btVector3* triangle, int partId, int triangleIndex) = 0;

Also how big is the ball in relation to the terrain, and how quickly does it move? TerrainMeshShape basically works by testing each triangle within the projected rectangle of the balls movement on the terrain. This post might be of help : http://www.bulletphysics.org/Bullet/phpBB3/viewtopic.php?f=9&...

There are also the GImpact shapes / extensions which should also provide a moving concave mesh. Not sure how well supported it is at the moment though,

I've had a look through the btGjkEpaSolver2::Penetration and there's very little (anything?) in the function itself that I can see that would cause an access violation, the shape0 and shape1 objects are really the only pointers provided and I don't see why they would get corrupted when it reaches a ...

Are you running in debug mode, and if so do you have a stack trace for the segfault?

It used to be hosted at http://bullet.googlecode.com/svn/trunk and I guess I haven't updated for a while. It does look as though sometime during it's move over to GitHub that demo got broken slightly.

Hmm, just looked at my RayTestDemo.cpp from the svn repository(rev 2689( and it has the ray test in the first hit block : ///first hit { btVector3 from(-30,1.2,0); btVector3 to(30,1.2,0); sDebugDraw.drawLine(from,to,btVector4(0,0,1,1)); btCollisionWorld::ClosestRayResultCallback closestResults(from,...

I could be missing something but it looks like in your first hit block of code you're not actually calling m_dynamicsWorld->rayTest ?

Nope , there shouldn't be any offset.. Are the collisions happening where you expect them to, or are they offset as well?

You could try a simple change and add an implementation of updateAabbs in btDiscreteDynamicsWorld (it's a virtual method) that only iterates over the m_nonStaticRigidBodies set. I'm sure I've looked into why static object aabb's are recalculated before but I can't remember the result of that, possib...

Heh, np. good luck with the rest of your project.

Thanks. I've had a quick run through. with position at 1.27 then the broadphase is generating a provisional overlap (probably down to the way the floats are quantized), with 1.30 then there is no overlap generated. to get round this issue, you can change your checkCollision function as follows : for...

May be a dumb question, but you're not doing any console output anywhere are you?

Have you tried the very simple case of one dynamic body and one static body and breakpointing the broadphase collision?

If you're using debug drawer you can include : DBG_DrawAabb in your draw mask .
If your project can be packaged up at all, i'd be happy to try and debug why you're getting those results.