small suggest
-
snowcat
- Posts: 9
- Joined: Thu Jan 10, 2008 3:53 am
small suggest
btCollisionWorld::addCollisionObject default collisionFilterMask is "1", why not "-1"?
-
Erwin Coumans
- Site Admin
- Posts: 4221
- Joined: Sun Jun 26, 2005 6:43 pm
- Location: California, USA
Re: small suggest
Can you give some more information how this change would improve the situation?
If there is a good reason, we can document it and make the change.
Thanks,
Erwin
If there is a good reason, we can document it and make the change.
Thanks,
Erwin
-
snowcat
- Posts: 9
- Joined: Thu Jan 10, 2008 3:53 am
Re: small suggest
It is not a realy problem when I read the manual document.
I'm a newbie of Bullet. When I add some scene node with btBroadphaseProxy::StaticFilter and add character with btBroadphaseProxy::DefaultFilter as their collisionFilterGroup, leave collisionFilterMask as default. The character can't collision with the scene. I debug the program and read the manual document and got the answer.
But for most time in my program, the collisionFilterMask is set to btBroadphaseProxy::AllFilter.
The only reason for change is: For a lazy man, shorter is better
btw: Not only to bullet. I'm a newbie to English too.
I'm a newbie of Bullet. When I add some scene node with btBroadphaseProxy::StaticFilter and add character with btBroadphaseProxy::DefaultFilter as their collisionFilterGroup, leave collisionFilterMask as default. The character can't collision with the scene. I debug the program and read the manual document and got the answer.
But for most time in my program, the collisionFilterMask is set to btBroadphaseProxy::AllFilter.
The only reason for change is: For a lazy man, shorter is better
btw: Not only to bullet. I'm a newbie to English too.