Problem with Direction in 3D

hazelsnowie

So the player in my project (a kinematicbody with an animatedsprite3d and capsule collision) is having an issue where, when I coded in gravity it started spontaneously changing directions when standing still. Does anyone know a solution? I'm happy to provide a project folder if you need to look into the detail more.

is just some footage.

cybereality

Most of the code is good, but the part at the end with the looking is confusing to me. What are you trying to accomplish with that code?

Azedaxen

This is a quirk of KinematicBody.move_and_slide(). One fix would be to avoid applying gravity when you know that the player is on the ground

cybereality

Usually what I do is:

if is_on_ground():
     velocity.y = 0

Right before the move_and_slide call.

hazelsnowie

@cybereality said: Usually what I do is:
if is_on_ground():
     velocity.y = 0
Right before the move_and_slide call.

i tried it and it didnt work (also i accidentally marked your response as accepted, is there a way to reverse that?)

cybereality

I think the issue is with the normalize() function right above where you check the length. This is because it will make the length 1 regardless of the magnitude, so a very small number that is close to zero (but not zero) will become 1. I think you want to remove the normalize function, then below check if the length is greater than speed, that should be correct. Then you might need to normalize inside the if statement before your other calculations.

hazelsnowie

@cybereality said: I think the issue is with the normalize() function right above where you check the length. This is because it will make the length 1 regardless of the magnitude, so a very small number that is close to zero (but not zero) will become 1. I think you want to remove the normalize function, then below check if the length is greater than speed, that should be correct. Then you might need to normalize inside the if statement before your other calculations.

this fixed the initial problem but it broke the turning

hazelsnowie

@hazelsnowie said:

@cybereality said: I think the issue is with the normalize() function right above where you check the length. This is because it will make the length 1 regardless of the magnitude, so a very small number that is close to zero (but not zero) will become 1. I think you want to remove the normalize function, then below check if the length is greater than speed, that should be correct. Then you might need to normalize inside the if statement before your other calculations.

this fixed the initial problem but it broke the turning

fixed the video

cybereality

Yes, because you have to normalize look directly under the if statement.

hazelsnowie

@cybereality said: Yes, because you have to normalize look directly under the if statement.

do you mean like this?

cybereality

That is the right place, but you need to do this:

look = look.normalized()

hazelsnowie

@cybereality said: That is the right place, but you need to do this:
look = look.normalized()

i tried, but it didnt change anything