Real-Time Physics Simulation Forum

Hello,

I have also done the same test with Bullet 2.56 ant it still do not work like GIMPACT 0.1.
But the collision looks different now!!!
I think there must be still another problem in new GIMPACT 0.2 integration...

Are you using GIMPACT 0.2 ?
May be this is source of my problme with it...

http://continuousphysics.com/Bullet/php ... php?t=1224

Thanks for you reply! Unfortunately commenting out #define BULLET_TRIANGLE_COLLISION 1 does not improve performance significantly. Bigger collision margin will only increase distance between meshes but not prevent inter penetration. I am using integration of Bullet in modeling software to create thi...

Oh nevermind. It certainly makes the simulation less stable...

Why does this happens?
I am also using you code in my Bullet integration and have not noticed it by now.

AddRigidBody will call internally AddCollisionObject but before it will set
collision groups for you.
Just look to the code of AddRigidBody how it works.

So if you want to change collision groups then just call AddCollisionObject with you own parameters.

Well then the problem is solved? Also may be you can look at new GIMPACT 0.2 compound shape. btGImpactCompoundShape * mycompound = new btGImpactCompoundShape(); btTransform localtransform; .... Setting transformation //add shapes with transformation btCollisionShape * subshape = creatingShape(0); my...

Hello,

can this be reproduced in the Bullet demos?

I am also using compound objects in my system too without any problems until now.

Hello, not sure if this is suitable for you but may be it is better us store just pointers in the btAlignedObjectArray? If the object is created with new then it can be big and scold be not copied at all, after the work it must always be destroyed with delete of course. But yes of course copy constr...

Hi, thank you very much!!! I have tested it a bit in my system and it works well. The only problem was Margin, it is set by default to 0.1 but in my system most object are 1.0 sized so this was too much. After adding this to btGImpactMeshShape all problems seems to be solved. virtual void setMargin(...

Hi, so you are using something like this on melax site? http://www.melax.com/volint.html There is also 3x3 Matrix Diagonalization may be something like this could be used? http://www.melax.com/diag.html I have done some test with it and got on alway good results, may be I used it in wrong way, not s...

Well Bullet uses now simple diagonal(vector) bounding box inertia for meshes and compound shape. Unfortunately simulation with this approximation looks not alway plausible. There is known way to calculate exact inertia for closed polygonal meshes and compound shapes, so I wanted to use it. But the r...

Thanks, all this sound very well!!!

I hope too this will be release soon!!!

Until some small problems this is (was) the most problem in my Bullet integration.

Nobody, any idea???

I am using now GIMPACTBullet connection. GIMPACT vs GIMPACT is really fast. But I and have noticed that collision of GIMPACT with simple Bullet convex shape like Box can be really slow. If btIDebugDraw::DBG_DrawWireframe is enabled the whole GIMPACT mesh will be yellow indicates that all triangles w...

Thanks you for for solving this problem Erwin!