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

collision detection

15 posts in this topic

I am using the following code to implement collision detection between a ball and bricks in a breakout game. My problem is that when I run the program the ball instantly vanishes from the screen. I have been working on this problem for quite some time. I have also been doing a lot of studying on c++ and collision detection.
[code}
void brick_collision()
{
if(x>3.0f && x<5.0f)
{
brick=3.0f;
bricks[3][5]=false;
}

else if(x>1.0f && x<3.0f)
{
brick=1.0f;
bricks[3][4]=false;
}

else if(x>-1.0f && x<1.0f)
{
brick=-1.0f;
bricks[3][3]=false;
}

else if(x>-3.0f && x<-1.0f)
{
brick=-3.0f;
bricks[3][2]=false;
}

else if(x>-5.0f && x<-3.0f)
{
brick=-5.0f;
bricks[3][1]=false;
}

SPRITE object3;
SPRITE object4;

object3.x=x;
object3.y=y;
object3.width=0.1f;
object3.height=0.1f;

object4.x=brick;
object4.y=3.5f;
object4.width=2.0f;
object4.height=1.0f;

if(Sprite_Collide(&object3,&object4)==1)
{
xstep=-xstep;
ystep=-ystep;
}
}
[/code]
1

Share this post


Link to post
Share on other sites
Am gonna provide rectangle on rectangle collision
[CODE]
//X = starting position X
//Y = starting position Y
//W = Width of the rectangle
//H = Height of the rectangle
rec1;//x y w h
rec2;//x y w h
//The way we gonna check collision is
//From left
//From right
//From top
//From bottom
if(rec1.x + rec1.w > rec2.x &amp;&amp;
rec1.x < rec2.x + rec2.w &amp;&amp;
rec1.y + rec1.h > rec2.y &amp;&amp;
rec1.y < rec2.y + rec2.w )
[/CODE]

EDIT::
I have noticed there is a tag for OpenGL? your checking collision in 3D? Edited by BaneTrapper
0

Share this post


Link to post
Share on other sites
Hi, Phil. [img]http://public.gamedev.net//public/style_emoticons/default/rolleyes.gif[/img]

Edit: Okay, I can see you tried, so I'll help you out some.[list=1]
[*]Hit edit on your first post there.
[*]Delete all the code.
[*]Copy the code (with formatting) from the original file.
[*]In the edit window, place the keyboard cursor where the code you deleted used to be.
[*]At the top of the edit window there are two rows of buttons. Press the red button at the end of the second row:
[img]http://s15.postimage.org/3lnyd14xj/srcbutt.png[/img]
[*]Select your language from the drop-down list.
[*]Past your code into the open space.
[*]Click 'OK'.
[*]Click 'Save Changes'.
[/list]

Typically I use something like the following for rect vs rect:
[source lang="cpp"]//using Microsoft RECT (left, top, right, bottom)

bool rectCollideTest(RECT& thisRect, RECT& thatRect) {
if(thisRect.left > thatRect.right) {return false;}
if(thisRect.right < thatRect.left) {return false;}
if(thisRect.top > thatRect.bottom) {return false;}
if(thisRect.bottom < thatRect.top) {return false;}
return true;
}[/source]

This can also be accelerated slightly if you know which exclusion is most likely and move it to the top. That's not something to worry about unless you're doing more collisions than you should though. Edited by Khatharr
0

Share this post


Link to post
Share on other sites
The [ code ] tags aren't working correctly anyway, so make sure to use the button. [img]http://public.gamedev.net//public/style_emoticons/default/wink.png[/img]
0

Share this post


Link to post
Share on other sites
[source lang="cpp"]void check_collision()
{
if(x>=3.0f && x<=5.0f && y>=3.5f && y<=4.0f)
{
bricks[3][5]=false;
glRectf(3.0f,4.0f,5.0f,3.5f);
ystep=-ystep;
}
well here is the code I am using so far.

if(x>=1.0f && x<=3.0f && y>=3.5f && y<=4.0f)
{
bricks[3][4]=false;
glRectf(1.0f,4.0f,3.0f,3.5f);
ystep=-ystep;
}

if(x>=-1.0f && x<=1.0f && y>=3.5f && y<=4.0f)
{
bricks[3][3]=false;
glRectf(-1.0f,4.0f,1.0f,3.5f);
ystep=-ystep;
}

if(x>=-3.0f && x<=-1.0f && y>=3.5f && y<=4.0f)
{
bricks[3][2]=false;
glRectf(-3.0f,4.0f,-1.0f,3.5f);
ystep=-ystep;
}

if(x>=-5.0f && x<=-3.0f && y>=3.5f && y<=4.0f)
{
bricks[3][1]=false;
glRectf(-5.0f,4.0f,-3.0f,3.5f);
ystep=-ystep;
}
}
[/source]
0

Share this post


Link to post
Share on other sites
The 'code' button actually uses 'source' tags to wrap your code.

Looking over what you posted, I still don't know what's representing a brick in your code.

Looking at your first post it seems like you're just using sprites and treating them like objects. If you want bricks that do things then you should make a class for bricks that encapsulates their behavior.

Separate your drawing from your logic: Do the logic for the frame and [i]then[/i] draw the result. Edited by Khatharr
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