collision detection

phil67rpg · 2012-12-05T02:56:13

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; } }

For Beginners

Started by phil67rpg December 02, 2012 11:08 PM

14 comments, last by phil67rpg 11 years, 4 months ago

Khatharr

8,814

December 04, 2012 03:02 AM

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 then draw the result.

void hurrrrrrrr() {__asm sub [ebp+4],5;}

There are ten kinds of people in this world: those who understand binary and those who don't.