SOLVED Problem colision with walls sometimes bugged.

[Luquemeister]

Hello every one I'm trying to recreate the Breakthrough game in a mobile version, making some testing in the game I found a kind of strange bug and I dont know how to fix it. The ball in the game should bounce properly without staying in one bordermoving up and down.

 

[rytan451]

Hi, kindly put the code within code boxes, not screenshots. It's a real pain if I have to type out your code to test.

That aside, the symptoms of the bug seem familiar. After the ball hits the boundary, you should move it such that it no longer hits the boundary. Otherwise, the hspeed or vspeed will negate again, moving the ball further out, then on the next step negate again, going further in, and over time making no net progress.

 

[Luquemeister]

Hi, kindly put the code within code boxes, not screenshots. It's a real pain if I have to type out your code to test.

That aside, the symptoms of the bug seem familiar. After the ball hits the boundary, you should move it such that it no longer hits the boundary. Otherwise, the hspeed or vspee

Hi, kindly put the code within code boxes, not screenshots. It's a real pain if I have to type out your code to test.

That aside, the symptoms of the bug seem familiar. After the ball hits the boundary, you should move it such that it no longer hits the boundary. Otherwise, the hspeed or vspeed will negate again, moving the ball further out, then on the next step negate again, going further in, and over time making no net progress.

First of all, sorry, I'm new in the forum and I don't know how to put the code in any other way yet, sorry for that

Yes i think is what you said about that vspeed and hspeed is going from 1 to -1 al the time when the bug occours, how can I make the ball no longer hit the boundary?

 

[LunaNightshade]

An easy way would be to simply adjust the position slightly, so that it is guaranteed out of the border.

 

[Greenblizzard]

Alerternatively, you could handle the boundary intersection differently for the left and right side:

if (bbox_left < 0) {
    hspeed = abs(hspeed);
} else if (box_right > room_width) {
    hspeed = -abs(hspeed);
}
// Or in one line like this:
if (bbox_left < 0 or bbox_right> room_width) {
    hspeed = abs(hspeed)*sign(room_width/2 - x);
}

To explain what happens here:
With abs() you remove the sign of the hspeed, and then you can set it specifically depending on which side of the room the ball is located.
sign(room_width/2 - x) evaluates to either -1 or 1, depending on which side of the middle of the room the ball is (or 0 if it's exactly in the middle).

 

[Luquemeister]

Alerternatively, you could handle the boundary intersection differently for the left and right side:

if (bbox_left < 0) {
    hspeed = abs(hspeed);
} else if (box_right > room_width) {
    hspeed = -abs(hspeed);
}
// Or in one line like this:
if (bbox_left < 0 or bbox_right> room_width) {
    hspeed = abs(hspeed)*sign(room_width/2 - x);
}

To explain what happens here:
With abs() you remove the sign of the hspeed, and then you can set it specifically depending on which side of the room the ball is located.
sign(room_width/2 - x) evaluates to either -1 or 1, depending on which side of the middle of the room the ball is (or 0 if it's exactly in the middle).

okay I will try to implement this and check if the bug stills up thank you very much!!

 

[Luquemeister]

I have been trying to bug the game with @Greenblizzard's code , in some certain situation where in the past the bug came easyly now works porperly, Thank you very much for your help @Greenblizzard