• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
ic0de

Collision filtering problem

4 posts in this topic

In my game using bullet physics I have a btGhostObject, a bunch of btRigidBodys and a static btCollisionObject. The btCollisionObject should collide with the btRigidBodys all the time and the btGhostObject should collide with every object except for one of the btRigidBodys. Right now I have my code set up like this:
 
//add the ghostobject which should collide with everything except rigbody1
dynamicsWorld->addCollisionObject(ghostObj, btBroadphaseProxy::KinematicFilter, btBroadphaseProxy::AllFilter ^ btBroadphaseProxy::KinematicFilter);
//add the btRigidBody which should collide with other btRigidBodys
dynamicsWorld->addRigidBody(rigbody1, btBroadphaseProxy::KinematicFilter, btBroadphaseProxy::DefaultFilter);
//add the btRigidBody which should collide with everything
dynamicsWorld->addRigidBody(rigbody);
//add the btCollisionObject which should collide with everything
dynamicsWorld->addRigidBody(collObj);
As far as I know this should work but it doesn't, ghostObj is still detecting collisions with rigbody1. As far as I know I'm using the mask system properly, perhaps I'm not using bitwise operations correctly? Edited by ic0de
0

Share this post


Link to post
Share on other sites
Anyone?

anyways I figured out something that I think might be wrong with bullet and was wondering if I was wrong:

when I change the mask for ghostObj to btBroadphaseProxy::DefaultFilter|btBroadphaseProxy::StaticFilter it still doesn't work and seems to be detecting collision with something that doesn't exist because collObj is he only thing marked as static and they surely aren't touching.
0

Share this post


Link to post
Share on other sites
Ok, let me take a look at the masks...
Kinematic=4
All=-1
Default=1

[font='courier new', courier, monospace]ghostObj group=0000 0000 0000 0100 against=1111 1111 1111 10111[/font]
[font='courier new', courier, monospace]rigidBody1 group=0000 0000 0000 0100 against=0000 0000 0000 00001[/font]

(edit: whoops I messed up the bits)
They should not be colliding. Take a look at manifold pointers

Notes.
  • Don't use [font='courier new', courier, monospace]btCollisionObject [/font]and [font='courier new', courier, monospace]btRigidBody[/font] in the same simulation. It's not forbidden but I don't think it's good practice. Use static rigidbodies instead.
  • When needing to filter against a specific object, I suggest to NOT use a specific collision group. It would make everything run short of bits quite fast. Either extend [font='courier new', courier, monospace]btGhostObject [/font]to ignore a specific collision object, or just let it work the same way and ignore its manifolds.

when I change the mask for ghostObj to btBroadphaseProxy::DefaultFilter|btBroadphaseProxy::StaticFilter it still doesn't work and seems to be detecting collision with something that doesn't exist because collObj is he only thing marked as static and they surely aren't touching

Not sure what you mean there. A collision manifold will get reported as long as their AABBs overlap in broadphase tests. Edited by Krohm
0

Share this post


Link to post
Share on other sites

Not sure what you mean there. A collision manifold will get reported as long as their AABBs overlap in broadphase tests.

Oh I see. In that case I must be detecting collisions wrong. I had assumed that ghostObj->getNumOverlappingObjects() would return the number of objects that the ghost object was actually colliding with, I had no idea that it only took into account the AABB. Does anyone know how to actually check if there is an actual collision using a ghost object?
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0