Trying out visual scripting - not sure why it's not responding

[patent geode]

I'm following a tutorial that shows visual scripting, I think I did exactly what was shown in the video but I'm not getting any response in the debug log. Not sure what I'm doing wrong here.

(this is the same as above but for the A key) what it looks like while running

It just doesn't seem to be recognizing that I'm pushing A/D. It stays red even when the buttons are held down, whereas in the video, they seem to respond and it works just fine

[smoky compass]

So... it looks ok to me, but if thats not working, try flowing through GetKey before If (the green ports).

I thought it should work how u have it tho. SOME nodes need to be executed before they provide values though.

If it is red, there should be an error message in ypur console to explain why it 8s red. Anything there?

[patent geode]

"You are trying to read Input using the UnityEngine.Input class, but you have switched active Input handling to Input System package in Player Settings."

and then a whole bunch of text

well, I guess chatgpt helped me with that one after I found the error message. the problem was in the default project settings, aka
project settings > player > other settings > active input handling needs to be on old or both

and that wraps up my problem :) the issue was in the project settings.

[smoky compass]

Ah, ok, yep unity wants to use the other input system

Yeh, this just means you accidentally or unknowingly opted in to the more recent input system

Dont be fooled though, just because it is kore recent it is not "automatically better".

Its just another option if it fits your needs better, as it can make universality easier but at some additional burden on codeside. So you pick your poison.

In your case, yeah, best course of action is possibly just to remove the input package

[patent geode]

I understand both input systems use cases, my teacher actually talked about it in class one time and explained how it's different and why it's sometimes better. but for this project, I am literally just trying to practice visual scripting and wrap my head around it, so I changed it to 'both' so that I can work with the normal GetKey node as well as try to understand the new input system later if I want to.

thanks for your help, I can't stand how chatgpt offers no help whatsoever if you don't know the source of the issue, you just pointed me straight to it lol

[smoky compass]

Once you get more familiar with it all you will fimd yourself providing clearer info to chatgpt too, the more info it has the better it is.

Sounds like you're on a good track anyway.

I think if you learn C# you will instantly know how to do everything in visual scripting

Honestly the process is "what's that method or variable again? Ah, thats right".

Your mastery of C# directly translates to your visual scripting knowledge. You require almost no practice if u know C# already

[smoky compass]

UVS is not that well known to ChatGPT though... a little, sure.

Better not to ask it UVS specific questions, better to ask it general logic questions.

"How can i sort casino tokens?" rather than "which nodes should i use to sort casino tokens?" Etc, then use the logic in UVS

[patent geode]

understandable

[patent geode]

kind of the problem I'm having that made me pick up visual scripting in the first place is that I can't for the life of me figure out coding. it's not easy when I do it and it doesn't sound remotely not confusing when someone else is explaining it to me. perhaps my ADD diagnosis is related but whenever I see code I just see a whole bunch of meaningless text on the screen formatted in ways that I can't figure out and with very specific syntax that I couldn't care to memorize; and this is where it falls short for me. I'm picking up UVS right now to hopefully counteract this problem, maybe something more visual will finally make it click for me and I'll be able to make my own scripts that way.

[smoky compass]

Its definitely not something that's meant to be intuitive. There is only one way to make it less alien too lol

Syntax stuff puts a lot of ppl off. In the end it boils down to simple rules that just didnt seem simple at first.

Once you have the following down, you're set for life pretty much, as these apply to most modern, popular languages:

• variables, primitive types & values
• assignment & logical operators
• branching statements
• loops
• methods, parameters & return types
• classes, objects, interfaces
• OOP (abstraction, encapsulation, inheritence, polymorphism) or any other paradigm, as long as you learn the principles of SOMETHING

It's a lot, but it's also not.

Once you have those down you're almost good to go in most modern languages minus the odd quirk.

Later you can learn things like

• abstractGeneric Types
• lambda syntax
• coroutines
• linq etc.

There's always more to learn, but get the fundamentals down first, they'll never steer you wrong and you can make actually a LOT without much extra

It definitely is not meant to be looked at and understood at first glance tho. It requires study, reading, practice lol

But it does also work backwards too. If you get good at UVS, code concepts will generally make more sense if you do give them a shot again