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

Corner Collision Detection Problems in a 2D Platformer

2 posts in this topic

Hey guys, I am working on a 2D-Platformer and I having some troubles with 2D collision detection and response. The problem is with happens when the player collides with a corner, the result being the player sticks to the corners for a brief amount of time. He also snaps to corners as well. 

 

The player is one tile in size, which means he can only collide with 4 tiles at one time. I check the four tiles within his vicinity minus the one he started in, then we change his position to the closest possible tile without making a collision. Here is the code:

void update(float dt)
	{
		float tempx = x + velx * dt;//The player's temporary X
		float tempy = y + vely * dt;//The player's temporary y
		int xdir = velx > 0 ? 1 : 0; // get x-sign using ternary operator
		int ydir = vely < 0 ? 1 : 0; // get y-sign using ternary operator
		velx *= 0.995;
		vely += 4.9*dt;

		bool q1 = world->tiles[int(tempx + xdir) + int(tempy + ydir) * 20] != 0;//Where the first quadrant is
		bool q2 = world->tiles[int(tempx + xdir) + int(tempy + 1 - ydir) * 20] != 0;//Where the second quadrant is
		bool q3 = world->tiles[int(tempx + 1 - xdir) + int(tempy + 1 - ydir) * 20] != 0;//Where the third quadrant is

		float ttempx = tempx, ttempy = tempy;

		if(velx)
		{
			if(q1 || (q2 && !q3)) //Checks for collision in the first quadrant
			{
				ttempx = xdir ? floor(tempx) : ceil(tempx);
			}
		}

		if(vely)
		{
			if(q3 || (q2 && !q1))//Checks for collision in the third quadrant
			{
				vely = 0;
				ttempy = ydir ? ceil(tempy) : floor(tempy);
			}
		}

		float xpen = abs(ttempx - tempx); 
		float ypen = abs(ttempy - tempy);

		if(ypen > xpen)
		{
			tempy = ttempy;
		}
		else if(ypen < xpen)
		{
			tempx = ttempx;
		}

		x = tempx;
		y = tempy;
	}

Can someone please tell me what is wrong with this code. Thank you.

0

Share this post


Link to post
Share on other sites

I'm not sure what's the problem (maybe it's easier to understand with an image), but there are suspicious parts...

 

First, you have xdir and ydir that, for your comment, store the sign of the velocity. The sign should be + or - (or +1 and -1 respectively), but your code set it as 1 or 0. Also, this is minor, but velx = 0 is being considered as negative in your code, while it makes more sense to count 0 as a positive number. And ydir stores exactly the opposite as the velocity's sign.

 

Later on you use xdir and ydir to access the tiles of your world, but the sums you make look weird too (the " + 1 - xdir" part). What tiles should you get while moving only right for example? Are you getting the 3 tiles correctly for every combination of x and y direction?

 

For the stick and snap to the corners... you're checking for collisions in every update call, but you're objects move from one tile to another (correct me if I'm wrong). Shouldn't you check for collisions only when you try to move to a tile instead of checkin during all the transition? I guess you're detecting a collision before it actually happens (it snaps) or you're detecting one even when you shouldn't (it sticks).

 

Sorry if this doesn't make much sense, I'm making a lot of assumptions.

Edited by DiegoSLTS
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