2d pong movement

Is the problem that you dont know how to handle the graphical movement, or that you dont know how to do the physics?

I'm assuming that the question is graphical since you do have the collision detection up and running.

I'm sure you can find some good samples on the SDL site, I myself dont know SDL, but basically what you want is a "Render function" in your game loop that draws the bats and ball sprites (at their current position) to a backbuffer and the swaps them to the primary.

I wouldn't have a ball angle. Instead, create a two-D vertex for its X and Y velocities. This will make it much more intuitive to change the direction and position of the ball. You will also need to store its position (another two-D vertex), and radius (for collision detection).

You need to make some sort of timer (SDL_GetTicks() returns the current time in milliseconds) for the purposes of updating the speed of the ball and paddles. For Pong, you can just multiply the speed of the ball by the number of milliseconds that have passed, and add this value to its position, like this:

position_x += speed_x * time_passed
position_y += speed_y * time_passed

When the ball hits a wall, generally (if the paddles are on the left and right sides of the screen) you reverse its Y velocity and keep the X velocity the same. Do the reverse when it hits a paddle. However, you might want to randomly add or substract from its Y velocity when it hits a paddle, to make it look like the ball is bouncing off in a different direction.

Collision detection can be as simple as seeing if the ball's position plus its radius is within the bounds of the paddles, and then moving it in the opposite direction of the paddle to a position where they are no longer touching, and then changing its speed so it's moving away from the paddle.

If you're wondering about graphics movement, you simply render the ball at an offset equal to its x and y position.

Hope this helps, otherwise clarify the questions you have further.

Quote:

Original post by silverphyre673 Instead, create a two-D vertex for its X and Y velocities.

READ: Vector. ;)

Oops! I meant vector! That's what you get for posting at 2:30 in the morning. Yeah...