Hello. So I got my collision to work, however I think my screen is very messed up. When i test for collision on 0,0, it will not let me go past the middle. When i set the collision for the bottom of the screen to move the paddle to 0,0, it went to the middle of the screen. Also the enemy is not even shown on the screen anymore, but when I comment the collision for the top right corner, it comes back. I googled it, but I got nowhere. I looked on the SFML board, nothing.

Here is a link to the project: https://docs.google.com/file/d/0BzAXLewFU0RnLW5UWlVNamMya1E/edit?usp=sharing

I have no idea what I did or why It is acting so strange. Thank you in advance for any help.

Hello Mathew,

Would you be able to point specifically where you make use of your collision method? There are a lot of files in your project directory and it will be time consuming to locate the exact point where the error occurs, and the help we can provide, unless we created the project ourselves.

Regards,

Stitchs.

Oh, sorry. The Collision.h and .cpp handle the Collision. And all the screen managing stuff is in the System.h and .cpp. There error might also be in IEntity.h and .cpp. That is where I get and set the position of the paddles.Those are the only files that I believe the error would be.

I thought I don't need to check the X axies because the paddles are only moving on the Y axies and they would never go < the width.

Now I am super confused. I played around with the code and I set the ball to start at 0,0 and it started at the top left corner. I believe the problem is with the getting and setting the values with the vectors.

I figured it out. This dastardly line here

shape.y = Shape.GetPosition().x;

Now I am super confused. I played around with the code and I set the ball to start at 0,0 and it started at the top left corner. I believe the problem is with the getting and setting the values with the vectors.

Isn't that the desired effect? Sprites in SFML should start with 0,0 equal to the top left corner of the screen, unless you override this behaviour, which you can do.