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

Collision detection with scaled spheres :(

4 posts in this topic

A quick question for you collision detection gurus:

 

How do you handle sphere vs triangle mesh collision detection when the mesh is scaled dis-proportionately?

 

i.e. a sphere vs a mesh with a scale of (1,0.5,1.25).

 

When scales are uniform it is easy to just transform the center of the sphere by inverse world matrix of the mesh then scale the radius by the inverse scale. But when the scales are out, I am not sure what to do.

 

What is the usual response here, ban scaling unless proportional? Or is the solution really simple but something I haven't thought of yet.

 

Cheers, and apologies if this is a really idiotic question.

0

Share this post


Link to post
Share on other sites

It's a very good question instead!

Last time I checked even Bullet appeared to have some different ideas about that, I think there was a "scaling object" of some sort... but I'm just taking it out of my memory and I haven't checked the documentation in a while.

Personally I re-scale everything at baking time. And if scaling happens at runtime... I am going to have a problem!

0

Share this post


Link to post
Share on other sites

Let me first make sure I understand the issue. Let's start with the solution you have when only uniform scaling is involved: You seem to be transforming the sphere to the model coordinates of the mesh and then computing the intersection there. If you were to do that in a situation where the mapping from model coordinates to world coordinates involves a non-uniform scaling, the sphere in model coordinates is now an ellipsoid, and the intersection test is harder.
 

Is that what you are talking about? If it is, you can compute the intersection between an ellipsoid and a mesh by first transforming both objects through an affine mapping that turns the ellipsoid into a sphere and then computing the intersection there. Of course, the model-to-world mapping is an example of such a transformation. So you can just compute the intersection in world coordinates instead of model coordinates.

 

Does that make sense? It feels like I must have missed something...

0

Share this post


Link to post
Share on other sites

Thanks for the replies guys,

 

Yes that does sound like a solution that would work but I wanted to avoid having to transform the meshes vertices to save time, i.e only every transform the sphere, I guess that means ellipsoid detection is the way to go :S although I don't like the idea of rotations here.

 

Maybe the best bet is check the scale, if uniform, move sphere into mesh space, if not move mesh into world space. Means I can at least re use the collision detection code. The downside that also comes with transforming the mesh into world space is I would also have to transform my "collisionData" too; I cache the triangle's plane and the plans of its edges for faster detection.

 

Shame there doesn't seem to be a catch all solution that reduces the need to transform the meshes vertices.

0

Share this post


Link to post
Share on other sites

Maybe you could transform the hit vector instead. I mean, the part of the hit vector which is inside the broadphase volume. I think I've seen something like that in Bullet source.

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