• 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
Felipe M

Questions about Polygon Intersection

4 posts in this topic

Hi. I'm trying to implement polygon intersection using SAT (Separating Axis Algorithm). There is plenty of nice material on the internet, but there is one particular part of the algorithm that I couldn't understand.

 

Here are three of the articles I've been reading, just If you wanna take a glance to be sure what I'm talking about:

http://www.phailed.me/2011/02/polygonal-collision-detection/

http://www.codezealot.org/archives/55

http://www.sevenson.com.au/actionscript/sat/

 

The part I don't understand, is the projection part. You have a normal vector pointing outwards, perpendicular to each edge, and based on that normal, you have to project the shadow of the polygon. But when I read these articles, this shadow seems to be represented by only two values, a min and a max value. This is the part I don't understand.

 

To clarify. This is an Image of a projection from the third article:

 

step2.jpg

 

 

This magenta line is the line I understand is the projection, or the shadow. But how can It be represented by two values? the min an the max? This is a line, and a line as far as I know can only be represented by two points, that is, four values: x1, y1, x2, y2.

 

So my question is, how is this projection represented by two values and not two points?

Edited by L i n c k
0

Share this post


Link to post
Share on other sites

The two values don't represent the line: They represent the two pink dots in some coordinate system for points in the line. Since the line is a 1D object, you only need one number per dot.

0

Share this post


Link to post
Share on other sites

So these values represent like a magnitude of the axis vector? As if the the axis vector would be transformed in a vector that would go to the first pink dot, and than in another vector that would go to the second one, and the two numbers are the magnitude of both vectors?

 

I have already Implemented my SAT in my code and it's working, but I made It looking to the tutorial codes and not fully understanding. So in my code the values of min and max come as for instance "-338578" and "49700". Really high numbers, and I don't understand why. My shapes are no more than 700 pixels in size.

Edited by L i n c k
0

Share this post


Link to post
Share on other sites

Those values are probably obtained by taking the dot product between a vector along the line you are projecting on and the vector from some reference point (the origin?) to a vertex. You probably started by computing the normal vector to an edge by reversing the coordinates of the edge and flipping one sign. If you normalize that vector (divide it by its length, so it has length 1), the resulting values from the dot product will be in pixels, and you won't get the large numbers you are seeing.

0

Share this post


Link to post
Share on other sites

The numbers are correct now. Thanks. Actually, I was thinking that I was already normalizing my axis vector, but then I looked again at this part, and I realized I was calling a method to normalize the vector, but the method was returning another vector, and not normalizing the vector that was calling. Just a simple mistake.

 

Thank you for your answers. I think I fully understand the concept and the code now.

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