Need Unity Master of doom.

[Yali]

Hey y'all

I'm currently searching a way how to do simillar player mechanics of this game: Bean Boy (

)
I'm just looking for the mechanics for the jump.

 

(I use the Unity Engine)

So.. Yeah..
-Yali

[trag1c]

It looks to be just a Simple 

RigidBody::ApplyForce()

or whatever it is. Its mostly going to applied over several frames to stop it from going wonky.

 

EDIT: This is psuedo code. Don't copy pasta.

if (key.isdown("SPACE")){Object.ApplyForceOverFrames(50, 5); // 50 units of force over 5 frames}

[Yali]

 

It looks to be just a Simple 

RigidBody::ApplyForce()

or whatever it is. Its mostly going to applied over several frames to stop it from going wonky.

if (key.isdown("SPACE")){Object.ApplyForceOverFrames(50, 5); // 50 units of force over 5 frames}

Wow. I'll try that thx!

[IshanSethi]

Hey y'all

I'm currently searching a way how to do simillar player mechanics of this game: Bean Boy (VideoLink)

I'm just looking for the mechanics for the jump.

 

(I use the Unity Engine)

So.. Yeah..

-Yali

I DONT use unity but rather I made an OpenGL game engine through Java, and you need to do it as if there were physics, that is the only way to do it to make it look real.

 

 

so what you need a gravity constant (negative val), a jump (positive val or initial velocity), and each second subtract the gravity constant from the velocity.

 

so if velocity upward it +5, and the g const is -2,

after the jump it will be

 

second 1: 5

second 2: 3

second 3: 1

second 3.5: the guy is still, so 0

second 4(downward fall): -1

 

so on until the velocity is the same so the total change in position in the y direction is 0, I DONT know any unity, but if you have some way to calculate time you should be good. thats why i gave you the logic, so you see the analysis behind it

..

I think you should understand it rather than copying code.

 

 

EDIT: then -> than

[IshanSethi]

Wow. I'll try that thx!

From that line of code, it seems that unity has some physics/mechanics built into it, so I should probs shut up lol.

But I tried, and if you had to make a jump method, what i said would be the answer and that is the logic behind the ApplyForceOverFrames Method

[IshanSethi]

Wow. I'll try that thx!

Btw ur game looks sick

[Yali]

 

It looks to be just a Simple 

RigidBody::ApplyForce()

or whatever it is. Its mostly going to applied over several frames to stop it from going wonky.

if (key.isdown("SPACE")){Object.ApplyForceOverFrames(50, 5); // 50 units of force over 5 frames}

Oh wow.

 

Btw ur game looks sick

Oh, it's not mine

[Yali]

I DONT use unity but rather I made an OpenGL game engine through Java, and you need to do it as if there were physics, that is the only way to do it to make it look real.

 

 

so what you need a gravity constant (negative val), a jump (positive val or initial velocity), and each second subtract the gravity constant from the velocity.

 

so if velocity upward it +5, and the g const is -2,

after the jump it will be

 

second 1: 5

second 2: 3

second 3: 1

second 3.5: the guy is still, so 0

second 4(downward fall): -1

 

so on until the velocity is the same so the total change in position in the y direction is 0, I DONT know any unity, but if you have some way to calculate time you should be good. thats why i gave you the logic, so you see the analysis behind it

..

I think you should understand it rather than copying code.

 

 

EDIT: then -> than

Dude, you're a champ. Thx so much!

[Yali]

 

It looks to be just a Simple 

RigidBody::ApplyForce()

or whatever it is. Its mostly going to applied over several frames to stop it from going wonky.

if (key.isdown("SPACE")){Object.ApplyForceOverFrames(50, 5); // 50 units of force over 5 frames}

Oh is it Js?

[trag1c]

Oh is it Js?

No its non functional code. Probably should have marked it psuedo but its up to you to do the coding and not copy pasting. All you have to do is apply force in the direction that you want. Its fairly trivial.

[trag1c]

From that line of code, it seems that unity has some physics/mechanics built into it, so I should probs shut up lol.

But I tried, and if you had to make a jump method, what i said would be the answer and that is the logic behind the ApplyForceOverFrames Method

What I wrote was code that I forgot to mark as psuedo but the engine does have methods for apply force vectors. For those they can be dealt with all at once, can be done through functions that are called each frame or they can be done through fixed time updates. 

[IshanSethi]

 

It looks to be just a Simple 

RigidBody::ApplyForce()

or whatever it is. Its mostly going to applied over several frames to stop it from going wonky.

 

EDIT: This is psuedo code. Don't copy pasta.

if (key.isdown("SPACE")){Object.ApplyForceOverFrames(50, 5); // 50 units of force over 5 frames}

The problem with this is that if your game lags, then the jump is going to be laggy as well. If you do it time-based it would be sooo much better

[carldun]

Yeah just use deltaTime

[trag1c]

The problem with this is that if your game lags, then the jump is going to be laggy as well. If you do it time-based it would be sooo much better

I recognize that however for what the op is posting this is a simple and I find typically less error prone approach for very early learners of unity. He really should be using a fixed time step that's independent of rendering e.g. 60 fps for physics but that's something that's probably well beyond the op at the point where he is now (I don't believe Unity has this functionality so it would be up to the dev to implement it). 

 

Yeah just use deltaTime

That is no different the apply at x frames as delta time is derived from the time between frames so your time steps would be the same. 

[IshanSethi]

I recognize that however for what the op is posting this is a simple and I find typically less error prone approach for very early learners of unity. He really should be using a fixed time step that's independent of rendering e.g. 60 fps for physics but that's something that's probably well beyond the op at the point where he is now (I don't believe Unity has this functionality so it would be up to the dev to implement it). 

 

That is no different the apply at x frames as delta time is derived from the time between frames so your time steps would be the same. 

Dude, there is nanoTime in all programming languages. and that is 1*10^-9 seconds. so that times 1000000000 = 1 second, w/o lag

[trag1c]

Dude, there is nanoTime in all programming languages. and that is 1*10^-9 seconds. so that times 1000000000 = 1 second, w/o lag

That still doesn't generate a fixed time step unless you can guarantee that the engine will update x times per second because you still have to query a timer object between draw calls. It is extremely hard to guarantee a frame rate on PC due to the vast variety in hardware configurations. (console this is a bit easier because there is no variation in hardware).

[fizzlesticks]

I recognize that however for what the op is posting this is a simple and I find typically less error prone approach for very early learners of unity. He really should be using a fixed time step that's independent of rendering e.g. 60 fps for physics but that's something that's probably well beyond the op at the point where he is now (I don't believe Unity has this functionality so it would be up to the dev to implement it). 

 

There is a function called FixedUpdate that gets called on a fixed time step for physics.

[trag1c]

There is a function called FixedUpdate that gets called on a fixed time step for physics.

Okay I didn't know that.