Help with Vector 3 normalization

[worn hinge]

Hi, I'm new to Visual Scripting and I just can't figure out how to connect my set vector 3 Y to Vector 3 Normalize, This is the only normalize option I get.

Here's the full sequence

Do I need to convert the Set Y float output to a transform and then connect it to Vector 3 Normalize?

[gaunt grove]

I think you are trying to do this

[worn hinge]

It breaks with simple float normalization

[gaunt grove]

yeah so try and get the Y instead of setting it

[worn hinge]

ah okay

[worn hinge]

That doesn't work either, it's harder since I'm also trying to get camera rotation (Cinemachine Freelook) and getting the model to move in the direction according to the camera. The Set Y was basically there to ground the gameobject from entering orbit.

For Example, if I press S while my camera is pointing down, it starts floating up.

(Sorry if this is too complicated to understand, English isn't my first language)

None of this is now connected to the main sequence chain

[gaunt grove]

Then i don't know if this would work but connect the Set y before the set linear velocity

[worn hinge]

I see, I'll do that now, thank you so much!

[gaunt grove]

Did it work?

[worn hinge]

Unfortunately no, but I maybe have a new idea in mind, I'm gonna try it and tell you how it works

[gaunt grove]

Cool

[worn hinge]

@gaunt grove Hey, fixed it. It was as simple as creating a complete new vector purely to process the movement

[gaunt grove]

ah i see perfect

[fair tusk]

Just in case, there's different normalize nodes.

One of those can accept vector 3 as input. And gives v3 output. And then can use get X or Y or Z if needed.

Cool that you made it work at the end ✌️

[fair tusk]

What node turned red with this? Hmm dynamic fetch usually means you are getting a changing variable data without saving it first

[worn hinge]

There weren't any which turned Red, that confused me too because then I could've easily debugged it. Though I asked Claude about my nodes and it made me realize just how many useless calculations there were. I simplified it down and then placing "Get X and Get Y" after "Add inputs" then creating a new vector 3 transform value simply just solved all the complications for me

[fair tusk]

Thats good to get results. But knowing why you had an error is important as well..

Sometimes clicking the error in the console takes you to the source of the error - where the red node is

You can also use the error finder uploades here

#1402768265217835100

Find the subtitle:

*🤬 The uVS-specific error messages are annoying" there's a errorFinder.cs you can use to quickly find red nodes