Crash in Game Engine collision detection #30630

New Issue

Yan · 2012-03-22T00:19:24+01:00

Yan commented

2012-03-22 00:19:24 +01:00

Category: Physics

%%%Attached .blend crashes after falling object (Cylinder) goes out of view.

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
0 btQuantizedBvh::reportAabbOverlappingNodex(btNodeOverlapCallback*, btVector3 const&, btVector3 const&) const + 4
1 btBvhTriangleMeshShape::processAllTriangles(btTriangleCallback*, btVector3 const&, btVector3 const&) const + 41
2 btScaledBvhTriangleMeshShape::processAllTriangles(btTriangleCallback*, btVector3 const&, btVector3 const&) const + 259
3 btGImpactCollisionAlgorithm::gimpact_vs_concave(btCollisionObject*, btCollisionObject*, btGImpactShapeInterface*, btConca
4 btGImpactCollisionAlgorithm::gimpact_vs_shape(btCollisionObject*, btCollisionObject*, btGImpactShapeInterface*, btCollisi
5 0 + 4798760640

blend and full crash report attached.

If "Compound" under Physics->CollisionBounds for the Cube is turned off, it does not crash.
Triangle Mesh is set.%%%

**Category**: Physics %%%Attached .blend crashes after falling object (Cylinder) goes out of view. Exception Type: EXC_BAD_ACCESS (SIGSEGV) 0 btQuantizedBvh::reportAabbOverlappingNodex(btNodeOverlapCallback*, btVector3 const&, btVector3 const&) const + 4 1 btBvhTriangleMeshShape::processAllTriangles(btTriangleCallback*, btVector3 const&, btVector3 const&) const + 41 2 btScaledBvhTriangleMeshShape::processAllTriangles(btTriangleCallback*, btVector3 const&, btVector3 const&) const + 259 3 btGImpactCollisionAlgorithm::gimpact_vs_concave(btCollisionObject*, btCollisionObject*, btGImpactShapeInterface*, btConca 4 btGImpactCollisionAlgorithm::gimpact_vs_shape(btCollisionObject*, btCollisionObject*, btGImpactShapeInterface*, btCollisi 5 0 + 4798760640 blend and full crash report attached. If "Compound" under Physics->CollisionBounds for the Cube is turned off, it does not crash. Triangle Mesh is set.%%%

Yan commented

2012-03-22 00:19:24 +01:00

Changed status to: 'Open'

Sergej Reich commented

2012-07-08 11:00:30 +02:00

%%%A simpler way to reproduce the crash is to turn on physics visualization when a soft body is marked as compound.
I'm pretty sure compound shapes aren't supported for soft bodies, it doesn't really make sense.

I've attached a patch that checks for rigid body type when building compound shapes and also grays out the compound option for soft bodies.
The behavior is still a little strange mainly because if compound is checked for a soft body that is parented to a rigid body, the soft body behaves like a rigid body.
It seems to be consistent with the way object types are treated in the game engine though .

%%%

%%%A simpler way to reproduce the crash is to turn on physics visualization when a soft body is marked as compound. I'm pretty sure compound shapes aren't supported for soft bodies, it doesn't really make sense. I've attached a patch that checks for rigid body type when building compound shapes and also grays out the compound option for soft bodies. The behavior is still a little strange mainly because if compound is checked for a soft body that is parented to a rigid body, the soft body behaves like a rigid body. It seems to be consistent with the way object types are treated in the game engine though . %%%

Mitchell Stokes commented

2012-07-08 21:52:25 +02:00

%%%I took a look at the patch, and I would change:
sub.active = not game.physics_type == 'SOFT_BODY'

to:
sub.active = game.physics_type != 'SOFT_BODY'

I'm assigning this report to Benoit to double-check the physics part of the patch.%%%

%%%I took a look at the patch, and I would change: sub.active = not game.physics_type == 'SOFT_BODY' to: sub.active = game.physics_type != 'SOFT_BODY' I'm assigning this report to Benoit to double-check the physics part of the patch.%%%

Inês Almeida commented

2014-06-19 20:21:18 +02:00

Added subscriber: @brita

Inês Almeida commented

2014-06-19 20:21:18 +02:00

@Moguri no Benoit to double check...
I have reapplied the patch and tested: D610
I don't see a difference in your proposed changes (not a==b vs a!=b), maybe because I don't know enough of python.

@Moguri no Benoit to double check... I have reapplied the patch and tested: [D610](https://archive.blender.org/developer/D610) I don't see a difference in your proposed changes (not a==b vs a!=b), maybe because I don't know enough of python.

Sergej Reich commented

2014-06-21 12:52:02 +02:00

@brita moguri's suggestion is just a style nitpick :)