• 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
CastorX

BulletPhysics Question

2 posts in this topic

Hello everyone,
Recently I've started my new small game project. During the desing I've decided to use BulletPhysics as the game's physical engine. But now I'm in a big truoble. I want to do the followings:
When two objects collide the specified sound has to be played. This depends on the material applied on the colloding trinagles of the objects. The sound sould be played (so the collision should be reported) only once (when the real collision happens, not on continous contact), depending on the impact speed and angle.
Alternatively if the above method is not possible it is also ok just to report if two "kind" of objects collide without reporting the material.
Any idea how to do this? I googled my problem and turned out that there are many methods to report object-object collision via callbacks but I can't find any correct sample code on the internet. It looks that the BulletPhysics is relly fast, but there are only a very few good tutorial. At least I was not able to find one I need to do this. If anyone knows how to do that or has a link to a good tutorial please help.
Thanks in advance!
0

Share this post


Link to post
Share on other sites
Hi!

When using Bullet Physics in your game you implement some[b] BulletInternalTickCallback( btDynamicsWorld * const world, btScalar const timeStep )[/b] method bullet uses as internal callback.
[CODE]
dynamicsWorld->setInternalTickCallback( BulletInternalTickCallback );
[/CODE]
dynamicsWorld declared as [b]btDynamicsWorld*[/b]
In this method you want to make loop like that:
[CODE]

// look at all contacts
btDispatcher * const pDispatcher = world->getDispatcher();
for ( int manifoldInd=0; manifoldIdx<pDispatcher->getNumManifolds(); manifoldInd++ )
{
//get manifold
btPersistentManifold const * const pManifold = pDispatcher->getManifoldByIndexInternal( manifoldInd );
assert( manifold );

// get colliding bodies
btRigidBody const * const pBody0 = static_cast<btRigidBody const *>(pManifold->getBody0());
btRigidBody const * const pBody1 = static_cast<btRigidBody const *>(pManifold->getBody1());

...

[/CODE]

So you acquired pointers to your colliding bodies. The next thing you want to do is: make an external list of colliding pairs of objects and update it every frame. So you can compare if the pair of colliding objects is already in the list, so you have continuous contact, otherwise they are just collided. Other data about collision you can get from [url="http://bulletphysics.com/Bullet/BulletFull/classbtPersistentManifold.html"]btPersistentManifold [/url]object. For keeping material data of the object you can create external wrapper for every physics body like:

[CODE]
struct PhysicsBody
{
btRigidBody const * const pBody;
enum Material m_Mat;
};
[/CODE] Edited by DgekGD
1

Share this post


Link to post
Share on other sites
Those are probably the most over-engineered solutions ever. I'm not sure BulletInternalTickCallback is supposed to be overriden for this reason. While it offers extra precision WRT an explicit check at the end of the tick I have doubts it's going to produce a different result as long as frame latency is low enough.
Manifold checking occurs in two ways: either check the manifolds manually or use a Ghost Object, with the latter being the recommended solution.[quote name='DgekGD' timestamp='1355166238' post='5009152']
So you can compare if the pair of colliding objects is already in the list, so you have continuous contact, otherwise they are just collided
[/quote]This is a bit of an over-approximation, as pairs are generated by broadphase, manifold distance is key here (as well as "direction"). Two objects will collide only if manifold distance is <=0 assuming pair (objA, objB) in correct order.
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