No I'm not talking here about rounding errors. What I'm talking here is about the scenario that you can see on next screen mock up. The paddle is moving downwards and the ball is traveling toward left an up.
Ponx_screenshot.png
In reality you could still bounce the ball in such scenario back to the game field but game registers that I lost the ball as soon as it crosses the left edge of the game field and thus doesn't give me a chance to bounce the ball back in such scenario.
Yeah I figured out that something like this might be the reason for the slowdown. It is a nice touch.
However the change between fast and slow speed is quite big and sudden so it feels a bit odd. Perhaps splitting the white areas to multiple smaller areas where each area would gradually reduce the speed of the ball might make this feel less odd.
In order to avoid performing multiple hit-tests against white areas for slowdowns you could instead you could just use the X distance from the middle of the gray area. Doing so even opens you the ability to go and for instance use logarithmic equation to calculate smooth speed transition.
Bookmarks