Yes exactly, thankyou sir.

Its my dream to be a game programmer, and this opportunity means a lot to me, got just 3 days left!
Sadly though, here in, we do not get much resources or motivation for Game Programming, so gets stiff.

Ok, for the triangles: check the variables defining the positions of the triangles before you draw them.

Anyway, if game programming skills are crucial for the career opening, something says me you should wait for the opening 2 or 3 years and meanwhile improve your skills.

The London Symphony Orchestra has an opening in the Oboe section! I just got an Oboe! Quick, what do the buttons to!?

Guys, look at this, everything seems to be ohkay, except the Ball hangs in the air, when Jump key is pressed. Before i made Ball Struct & functions for Ball Movement, ball was jumping fine. But now, there is this weird error with the same code.
It has something to do with the Draw function of the Ball, but i am not able to figure it out.
Looking to put in collision detection and spritesheets, so need functions for ball movement, such as MoveRightBall/Left/Jump.

This is the code i have changed

The ball hangs in the air you say. Then you should ask yourself, what is the condition for the ball to fall. Could it be gravity? What is the condition for gravity to be applied? Is it ever true?

Oh God, he's shouting now.

We'll never make the London Symphony.

With your education, you should have no trouble figuring out a formula for each type of detection; even if it's inefficient, it will do.

Once you come up with some formulas, we will gladly guide you on how to turn that formula into C++ code.

If you can figure out if a point is in a circle, if a point is in a triangle, and if a point is in a rectangle, you should be able to figure out a way to do it.

You might find it easier to treat a circle as a rectangle because if the circle's radius is less than the box's height, you'll have to check if the circle collides with its edge.

Also, he is not spamming, this is the atmosphere at a.cc .

varynoob, without trying to sound demeaning, it's very obvious that you are out of your depth here. If you do manage to get the help you need from people here in order to get the job, then what? It won't take long before your employer realizes that you don't have the necessary experience.

I have learnt from my mistakes sir, as everybody had told here, to try and try, and come up with things, i did the same.

Used Bounding box for circle, and bounding box of triangle to check collisions between the two, while the rectangle itself, has sides, so it is easy for that.

But what i am facing is, the collision comes out to be ok at times and weird at other times. So asked you of the flaw.

Here is the code.

PS : SO I HAVE BEEN TRYING, AND HAVE COME UP WITH THE COLLISION TECHNIQUES AS WELL.

IT IS ALL ABOUT MORE UP THAN BOTTOM, MORE BOTTOM THAN UP, MORE LEFT THAN RIGHT & MORE RIGHT THAN LEFT.

Dizzy Egg : Typo sir! It was meant to be 'bound_triangle_y'.

I have been trying out different things, but havnt really landed into any good one, as in i want to achieve if Circle hits Left of square, everything freezes except the ball, which if made to bounce, should make things back normal and scrolling.

What i did is, checked the collision with the sides of square i.e Right of circle more right than square's left & Left of circle more left than Square's right.

If the condition is true, Leftcollision is true.

If Leftcollision is true, All the update functions are skipped, thus screen is freezed.

But this stuff doesnt do well for me. Code below :

if((shapeS[i].pos_rect_x1 -5 < shapeB.pos_X + shapeB.boundx)
&&(shapeS[i].pos_rect_x1+ 40 > shapeB.pos_X - shapeB.boundx)

But then, this condition also has an && thus if 1st is always true, the 2nd will only be true, if the left of the ball is less than the right of the square!!

boundx = 23.

So for shapeS[i].pos_rect_x1 = 20, and shapeB.pos_X = 50

it will be : (15<73) && (60 >27> | TRUE

For shapeS[i].pos_rect_x1 = 20, and shapeB.pos_X = 90

it will be : (15<113) && (60 > 67 ) | FALSE

So, it should be correct?? What's wrong?

Oh yes, sorry, i mean it collides with some squares while it doesnt with others! All random, it is something to do with my Update and Draw functions of square!

How do i check, that only if there is not square already on (x,y) position, next square should be drawn else, neither drawn nor updated(coz sometimes, invisible squares are coming up, i.e which are not drawn, but updated!)

THE SQUARE FUNCTIONS ARE AS :

Awesome videos, 23.