ti99iuc Posted May 12 Share Posted May 12 happy to be appreciated with the feedback. I am not into the developing so it is just a stupid question i am afraid but, could maybe use a closed racket helps? :p or it is another kind of problem? Quote Link to comment Share on other sites More sharing options...
+TheBF Posted May 12 Author Share Posted May 12 Someone told me a long time ago, the only "stupid questions" are the one we don't ask. The racket is a sprite to the computer so the shape we see does not matter. Only the dimensions of the racket which is a square made of 4 characters. It all has to do with how you detect "coincidence" between the ball and the racket and then how make sure that the ball has moved away from the racket before you test for coincidence again. The "devil is in the details" as we say in English. It looks like I am detecting again before the ball has been moved far enough away. It means I will have to test some different methods. I think I have a better method now but will play with it more before releasing another version. 1 1 Quote Link to comment Share on other sites More sharing options...
+TheBF Posted May 13 Author Share Posted May 13 Ok I think I made it better. Now the ball takes over after a collision and moves itself clear of the thing it hit before we re-enter the primary game loop. New files are at the top of the thread. Seems to play more reliably. I actually won 1 game at "gamer speed". That's a first. Updated source is here CAMEL99-ITC/BREAKOUT.FTH at master · bfox9900/CAMEL99-ITC · GitHub Big changes are in the words WALL-CLR and PADDLE-CLR which move the ball several pixels after a collision. 5 Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.