LB, you speak the truth. The ball's position should be predicted to suit the player about to hit the ball, with little adjustment on the paddles, not that that matters anyway.
Printable View
LB, you speak the truth. The ball's position should be predicted to suit the player about to hit the ball, with little adjustment on the paddles, not that that matters anyway.
I am on my iPod at the moment, so I can't look at the example, but try this:
If you are always sending the balls X and Y positions, try just sending the direction when the ball collides with a wall or bat. That way you have the smallest amount of data to send.
Due to varying amounts of lag that is a pretty bad decision to make, Game_Master.
That's what I do usually, and then I also send 'correcting' coordinates every second, to correct the position of the object.
Only every second? That could be enough time for it to go wrong, you know.
LB quit yapping and make GwerdyPong and show these fools how its done U__ U
lol jk