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

Deactivate a rigid body in Bullet

9 posts in this topic

Hiya,

 

I realize that this is a question best asked on the Bullet forums, but here goes anyway...

 

What is the correct way to deactivate an RB that is active? Ie. "put to sleep". There is an activate() method but no deactivate(). There is something called forceActivationState(), so I guess I could just pass ISLAND_SLEEPING to that, but it seems awfully hacky. Is there a cleaner way? Also, since it refers to islands, will it affect other nearby objects if I do it that way?

 

Some other engines have methods for putting objects to sleep regardless of their current state.

0

Share this post


Link to post
Share on other sites

I guess, you can use btRigidBody::setFlags method and set proper flags to configure behavior for your rigid body. Here is a list of all flags(line 117). 

0

Share this post


Link to post
Share on other sites

I have implemented this behaviour with bullet, but I can't look it up at the moment.

 

[quote name='GuyWithBeard' timestamp='1357731652' post='5019419']
Also, since it refers to islands, will it affect other nearby objects if I do it that way?
[/quote]

ISLAND_SLEEPING is set, when a group of nearby objects is deactivated, I believe that this is not the correct way, but I will look it up later.

 

 

[quote name='DgekGD' timestamp='1357732134' post='5019422']
I guess, you can use btRigidBody::setFlags method and set proper flags to configure behavior for your rigid body. Here is a list of all flags(line 117).
[/quote]

The flags at 117 affects the collision behavior of the object. In this case you want to keep the behaviour and just disable the active physical control by the physics engine until an other object triggers it again or you manually activate it again.

0

Share this post


Link to post
Share on other sites

Ashaman is right. I don't want to touch the collision flags. Anyway, if you get the chance to look up the "right way" and post it here I'd be grateful. :)

0

Share this post


Link to post
Share on other sites

Out of interest - why are you wanting to set this yourself rather than letting Bullet set it for you when it thinks the object is actually deactivated?

0

Share this post


Link to post
Share on other sites

I am doing networked physics. As long as the RB on the server is active it sends updated transforms to the client every x milliseconds. When it gets deactivated it sends a deactivated-message to the client and stops sending transforms. At this point the client RB needs to be moved to the last known server RB position, and get deactivated, so that the RBs are in sync across the network. If I don't do this there is a slight chance that the RB on the client is not deactivated when the server RB is, and it keeps moving around when it should stay in place.

0

Share this post


Link to post
Share on other sites

Ok, makes sense. just had a quick check through as I'd forgotten how this stuff worked exactly, but you should just be able to call :

 

setActivationState  rather then forceActivationState as the former will honour the disable deactivation /simulation states while the latter won't.

 

it sounds like you're running stepSimulation on the client as well ? (to allow local collision query calls) so the RB would be brought back to life anyway if it was required.

0

Share this post


Link to post
Share on other sites
Yes, I am simulating on both the client and the server since the server does not send updates across the network on every tick. Using setActivationState might be a good idea. I'll check that out, thanks!
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