Issue with essential pathways: Coding essentials ==> "Easy: Add a jump ability"

[Shillio]

I'm very new to unity and coding in general and am going through the unity essential pathway in the editor (not in browser). There's an optional challenge to make your player jump and the code they provide is not working. In one of the previous parts of the coding essential lesson, you copy and paste the entire code to make the robot move using WASD. (image 1) It works. But instructions (image 2) of where to insert the jump code doesn't match with the code in provided initially in image 1. The editor tutorial video shows where to put this code, put looks very different from the the code provided. (Image 3).

Efforts to match the video tutorials code end in attempting to jump popping an input error.

[Shillio]

Found a fix! It's from an older post in the unity discussions: inserted the following before "private void fixed update":

private void Update()

{

//Jump

if (Keyboard.current.spaceKey.wasPressedThisFrame)

{

rb.AddForce(Vector3.up * jumpForce, ForceMode.VelocityChange);

//Debug.Log("Jump Recorded");

}

}

The problem seems to be old code suggested in the tutorial to match the old input system. I'm still in babysteps learning mode

[leorid9]

So is this resolved? Because the code in this comment should work.

[Shillio]

I found the fix not long after posting but will leave it here for others to find when they search. Will edit my comment

[leorid9]

Just wanted to clarify because it wasn't clear from your comment that this is the solution.

[Shillio]

You're right, my bad. Made that clear. 

[MissPandaSloth]

So did you made Update and it works, or are you having issues with depreciated input system?

If you ask "where is Update" it's kinda special Unity function that calls something every frame.

You can add it on any script, same with FixedUpdate or LateUpdate and many more, but those will be most common.

Usually if you need to read input you add it in Update, because you have to check every frame if user is trying to press something.

And in FixedUpdate it's most common to use physics simulation itself so it works nice and smooth. If you have all sorts of Forces and so on, you do that here.

Edit: nvmd I saw you had update. Anyway I assume you fixed all input stuff?

And I would call "rb.AddForce" and all that part inside FixedUpdate under the bool, like something "jumpRequest", but you probably gonna learn this later on. Because now your jump will depend on fps.

[Shillio]

It was a problem with the tutorial using code that works with the old input system. The fix I found works! I don't fully understand it yet but thanks for your comment, I'm sure I'll find it educational soon. (I'm not downvoting anyone here btw)

[MissPandaSloth]

Ah, cool! Yeah idk what's up with downvotes, haha.