Jumping for AI in my platform game

I'm really getting frustrated here guys :C
Doesn't anyone have any idea? :/

Cheers, TheCalm

Just add a boolean variables to your waypoint-edges. like this:
struct Waypoint
{
vec pos;
}
struct edge
{
Waypoint w1,w2;
float distance;
bool jumpNeeded;
}

I hope this helped you

Thx for the reply!
Though i'm afraid that's not my problem. I already have a class for the waypoints who contains a position-vector and a bool that keeps track if i need to jump.

The problem is the get a formula to get Sarah to jump and land exactly on the position :/

Cheers!

I don't have time to write code for you, but here are some ideas for getting more information into your equation and simplifying the problem.

1) Keep in mind that there may be many jump angles/velocities that land you in the same spot. You can simplify by locking your angle to 45 degrees. (or whatever angle works best for you)

2) If you know the maximum height of your arc, and your acceleration due to gravity, then you also know the time it takes to rise to that point.


3) You posted a lot of formulas you're looking at, but i find diagrams and descriptions a little easier to convert into code:
http://www.physicsclassroom.com/Class/vectors/u3l2c2.cfm


I'll post more when I have time if this was too cryptic :-)

Your problem looks hard,hope someone who have professional experience can really help you.
Good luck!

I don't have time to write code for you, but here are some ideas for getting more information into your equation and simplifying the problem.

1) Keep in mind that there may be many jump angles/velocities that land you in the same spot. You can simplify by locking your angle to 45 degrees. (or whatever angle works best for you)

2) If you know the maximum height of your arc, and your acceleration due to gravity, then you also know the time it takes to rise to that point.


3) You posted a lot of formulas you're looking at, but i find diagrams and descriptions a little easier to convert into code:
http://www.physicscl...tors/u3l2c2.cfm


I'll post more when I have time if this was too cryptic :-)

Thanks!
I've been trying to get a good formula from what i know. But i cant get it to be exact. The problem is that it seem to be dependent on to many variables.

For instance we have one formula that says that the speed in the x-axis is the same, it never changes. So if we have that in mind we know that:
X (a distance) is equal to V0 * cos(a) * t
Where V0 is the starting velocity, the cos(a) i the cos for the angle at the start and t is the time it takes to travel the distance in x.

Okey, so we can rewrite cos(a) to be V0x / V0 which leads to "x = V0 * (V0x / V0) * t". We see that we can take away the "V0" part leading us to get:
"x = V0x * t". This is good, since I know my velocity in x to be the same all the time which means that the v0x is the same.

So we know x, since we have a waypoint that keeps track of the points we want Sarah to go. Perfect you might think! But it is here that it gets tricky. Why?

I'll try to explain.


So say that x is 200. That means Sarah is supposed to jump 200 pixels from her place here. Her speed in the x-axis must be atleast 11 (since my character im steering has 10 in speed, and i want Sarah to be faster then my character).
So this will give us the time for the jump.
In this case this means that the distance of 200 pixels with a speed of 11 pixels per update (i will refer the time as how many updates something will take. And my FPS is locked at 60 FPS, giving us 60 updates per seond. If you would rather count it as pixels per second or something).
Anyhow! This means that the jump will take 200/11 = 18.18181818... ~18.2 updates.


We also know that "y = V0 * sin(a) * t - ((g * t^2) / 2)
Where y represents the point at any time in the jump in the y-axis, the g is the gravity and the sin(a) is sin of the angle.
We can rewrite sin(a) as V0y / V0.
And as above this will lead to "y = V0y * t - ((g* t^2) /2).
Now we have three loose variables. The starting velocity V0y, the gravity g and the y.
But if we say that we will take the point where y is the highest, then we know that would be exactly the half of the time (18.2 updates).

And say that we take y to be "the difference in y + 128". Meaning if sarah will jump in the same y height, her maximum height will be 128 pixels above her position now. If she were to jump to a platform 64 pixels above her, her maximum height would be 128+64 = 192 pixels and so on. But for now, lets just focus on a jump 200 pixels away in the same y-height. This will give us y = 128 at the time of (18.2 / 2) = 9.1.


But the problem now is that we still have two loose variables, g and V0y, right?

Your system should have a constant g, should it not? Your entire world would have some form of gravity, and your character that is finished will probably be using the same constant. [s]At mid jump, the apex, your V0y would be 0. At the start and the finish, your V0y would be 0. Mid-jump, your V0y would be your previous Vy. I may be wrong on that very last statement, but I don't think so. If V0y was to consider your initial jump's starting velocity, the character is not moving, so that would fully eliminate V0y * t.[/s]


EDIT: As an afterthought, and due to it being late, V0y would be a function included in your equation for y, and each point during the jump would recalculate the equation with a different t: y = (g * t + V0y) * t - ((g * t^2) / 2) where V0y is the very first velocity you want to give the character to jump.

-- To clarify: (g * t + V0y) is the velocity the character is at at the end of the last update.

Your system should have a constant g, should it not? Your entire world would have some form of gravity, and your character that is finished will probably be using the same constant. [s]At mid jump, the apex, your V0y would be 0. At the start and the finish, your V0y would be 0. Mid-jump, your V0y would be your previous Vy. I may be wrong on that very last statement, but I don't think so. If V0y was to consider your initial jump's starting velocity, the character is not moving, so that would fully eliminate V0y * t.[/s]


EDIT: As an afterthought, and due to it being late, V0y would be a function included in your equation for y, and each point during the jump would recalculate the equation with a different t: y = (g * t + V0y) * t - ((g * t^2) / 2) where V0y is the very first velocity you want to give the character to jump.

-- To clarify: (g * t + V0y) is the velocity the character is at at the end of the last update.

Thanks

The problem is that even though i set a constant "g" and a constant "V0y" the jump doesnt seem to land on the exact position i want to. Sarah seem to land to far :/

Perhaps you have something else affected it.

Like what one poster said you could simplify things by making some variables constant. But you could make it even easier by making almost every variable constant. Restrict yourself to a limited set of jump vectors and have the AI choose from among set one vector that best fits the situation.