Aloush154 / bullet

Automatically exported from code.google.com/p/bullet
Other
0 stars 0 forks source link

Debug Drawings cannot be turned off for individual soft body objects #795

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Set up a bullet world with wireframe debug drawing enabled.
2. Call
softBody->setCollisionFlags(softBody->getCollisionFlags() | 
btCollisionObject::CF_DISABLE_VISUALIZE_OBJECT);
on a btSoftBody object.

What is the expected output? What do you see instead?
I shouldn't be able to see a wireframe of the soft body but I do.

What version of the product are you using? On what operating system?
Bullet 2.8 (specifically svn revision 2531) on Arch Linux 64 bit. 

Please provide any additional information below.
Sorry but I don't have a test case for this. I've only ever used bullet through 
the Python interface of Panda3D. The only test case I have is the one on this 
Panda3D bug: https://bugs.launchpad.net/panda3d/+bug/1282729
A potential fix has been suggest on the bug as well.

Original issue reported on code.google.com by Ashley.W...@gmail.com on 21 Feb 2014 at 2:17

GoogleCodeExporter commented 8 years ago
btCollisionWorld::debugDrawWorld() checks the CF_DISABLE_VISUALIZE_OBJECT flag 
for each collision object befor calling the Draw method for the collision 
object.

For me it seems reasonable to do such a check in 
btSoftRigidDynamicsWorld::debugDrawWorld() too, before calling the Draw method 
for the soft body object. After all btSoftBody is a btCollisionObject 
(inheritance).

Original comment by ralf.pfr...@googlemail.com on 23 Feb 2014 at 10:21

GoogleCodeExporter commented 8 years ago
moved to github https://github.com/bulletphysics/bullet3/issues/54

Original comment by erwin.coumans on 30 Mar 2014 at 4:49