Jump and Y (AXIS) constraint clash

[lapis schooner]

Hi, I had a similar issue before and Asked some people but it was fixed for a moment.

From the second snippet, you can see I'm using "Vector 3 Create" (Node) to set the character's absolute Y value to 0. Why do I have to do this? Because I'm using Camera Relative movement with CineMachine's freelook camera.

The main purpose of using Camera Relative movement was so that I could create the well known "Press W and move around with mouse" effect. It worked, still works perfectly, but it has caused direct problems for other parts of character movement.

Mainly the Jump (And the exact same issue with Flying) is bugged out. I'm using Impulse (First Snippet), which is normally used for Jumping. I did some calculations and at double gravity, the character reaches back to the ground after 2.24 seconds, with a Y difference of 0.79.

That's not all, the jump is "Instant". As soon as I press Spacebar, it goes to 1.79 units INSTANTLY.

I did some debugging and mainly after creating a rigidbody default cube fall, I realized the issue is with my Y constraint within the actual movement script. Even if I press jump which has it's own graph (Not mixed with the player movement), the movement script still forces the constraint onto the character, causing the instant jump with the slow fall.

I want to remake the graph but I have no idea how I should go about doing that. Please help.

Thank you for reading this far and for providing advice! (Full Snippet for Character Movement will be in chat)

(Please ignore the caution on Animator as I'm in my testing workspace which does not have an animated character)

I have this new plan here:

Get Camera Forward → Set Y=0 → Normalize
Get Camera Right → Set Y=0 → Normalize
Multiply with Input (WASD)
Combine X/Z with Rigidbody.velocity.y → Vector3 Create
Set Rigidbody.velocity to that

But I have no idea how I would apply it. Help of any amount would be highly appreciated!

[ivory bear]

I see a possible conflict in there because you have two nodes interacting with rigidbody

Set linearVelocity and addForce impulse.

Im not sure where the linearVelocity starts as its in a subgraph? I see an input...

And the input of set linear velocity doesnt look clear where it comes from because the screenshots are cut.

But i think it has a new vector x, 0, z) before it - so that 0 should affect jumping (specially when these graphs are flowing)

I usually do a "get linear speed get y" and connect y to that set linear velocity, while x and z are being received by control input .

This way it never interferes with altitude (jumping) and just adds velocity on x and z.

[lapis schooner]

Hi Litoid, thanks again for coming to my rescue! (You're an angel)

I'm sorry for not sending the full picture as my monitor isn't big enough for that (unless I sacrifice clarity). So here's the full picture so you can see the flow completely (With the first 2 providing clarity)

[lapis schooner]

Oh my god... I think that worked

Okay it kind of worked, aside from this happening (And the character being LAUNCHED) when I press Spacebar

[ivory bear]

Ignore that error, i also get it and its no uVS related. Not sure what it is but have never interfered with my coding

[ivory bear]

Hmm wait. You say it happens when you press space bar?

Looks like you'll need to do one of these things (usually fixes my issues)

1. restart unity. Its weird but sometimes random bugs stay. Restarting clears it.

2. click the console log error and see where it takes you in the hierarchy or in your project files assets

3. dismember your code. Right click certain white arrows to cut the flow and see if it happens again. See where it begins.

(It helps to change settings in project settings > editor > "do not reload scene or domain"

So starting playmode and stopping is blazing fast (seconds)

[lapis schooner]

@ivory bear here's a video of what's happening, no idea why it is doing this

This shouldn't be happening

Makes no sense to me why this would happen

I just realized, it's not even applying the force

[ivory bear]

did you see this tutorial I made not so long ago? #1405549841400201266

[lapis schooner]

Actually, no, let me look at it right now (I fixed the raycast by the way, so it applies the force now)

[ivory bear]

yeah start there - watch that, and let me know if you found something useful or else we can continue to debug this

[ivory bear]

It is shooting to the sky too fast, and you DONT need "get up" node.

Just apply that jump force directly to AddForce node

There's a node variation that allows you directly connect to Y input

[lapis schooner]

I JUST did a test, by removing the movement graph, and jump worked perfectly

The issue is in the movement controller subgraph

This part specifically is the culprit (The only thing I changed)

[ivory bear]

that's what you added or removed?

[ivory bear]

I pointed that out before, not sure if you saw it

[lapis schooner]

Added

I tried to add this line from your message above it: "I usually do a "get linear speed get y" and connect y to that set linear velocity, while x and z are being received by control input ."

I may have misread it completely

This picture in particular which you sent

Also quick question, do you use a drawing tablet? That looks pressure sensitive drawing

[ivory bear]

It was done in Google Keep, on my phone.

glad it worked out for you