VEX Isn't Scary | Part 2 | Conditionals

[@evening8990]

Fantastic, this is what I've needed to get my head around vex, many thanks for the clarity

[@sharath2273]

One thing: colors can also use curly braces: @Cd = {1, 0, 0} is a valid expression that is shorter and easier to write.

[@kirandev]

he knows that but he is making easier for beginners!

[@sharath2273]

@@kirandev It is useful to know shorthanded, and curly braces are simpler to write But note that you can't use variables in curly braces, that is, "@Cd = {x, 0, 0}" is invalid and you have to use set() in such cases

[@aydin_yaman]

Superb tuto for beginners.Thanx a lot for this tuto series :)

[@KZLR]

You're a good instructor.

[@pratapmistry7659]

Nice .. very very helpful ..great instructor.

[@dipankarbiswas033]

Oooo brother ur awesome 👍👍👍 thanks... Is it possible to write or type in vscode please please let me know

[@정채환-f4i]

This is so good

[@정채환-f4i]

I hope this is profitable and will be continued

[@nitroflap]

How did I miss it? Houdini has it's own programming language )))

[@awesomeguitarshorts]

Awesome Sir !! Thanks a lot.

[@ros27922]

Will there be also the “Python Series” ?

[@axleonex1777]

This was so helpful, thank you!

[@douaaal-mgoter5260]

Thank you 💕

[@natecastronovo]

Well done tutorial. except, at least in 17.5, it seems the box set to polygon mesh doesn't actually have Cd value.

[@grimwolf9988]

Haha, "VEX isn't scary". Trying telling VEX that. Following along, I immediately got stuck like 5 minutes in despite following along exactly. The code started failing, and the error messages were vague and useless. Turns out, I accidentally capitalized the V in "float yPos = v@P.y;" Extremely basic problem, extremely difficult to spot even when looking right at it, and the editor refused to actually show me what had gone wrong or where. It was 5 lines of code! And not only is it both super strict about case, and also will not tell you if you're using the wrong case, but the required case seems really arbitrary as well. @Frame and @ptnum are both base functions used in the next video, but for some reason @Frame has to start with a capital letter, while @ptnum uses no capital letters at all. I'd have an easier time using C++ than VEX.

[@sharath2273]

What I tend to do is to comment out all the code, starting from the end to the start and see when the error disappears.

[@sharath2273]

Additionally, you can remove "Create additional attributes" (or just set it to Cd if you are making color, etc.) on the attribute wrangle. This means that @p will register an error, instead of being created.

[@FabiodeSaldanha]

Why did you say Cd.x and not Cd.r ?

[@shahriartanvir977]

for color x, y, z represent r,g,b respectively. So what I understood

[@sovattasim39]

Its a good question, I was very confused about that, and I just replaced the Cd.x, Cd.y and Cd.z by Cd.r, Cd.g and Cd.b. And it worked ! I hope it will help someone else also

[@meltedpolys1104]

Because in the UK they dont say Red, Green, Blue. They say Xed, Yreen, Zlue. Kinda like with grey and gray, or 'Zee' and 'Zed'.