I did some computer science and these intro courses can actually be a perfect case usage of them, since this is pure computer science and Iove it. I use python and C# so I am very used to these, thanks for these master classes
3 ปีที่แล้ว +5
Thanks to you for all tutorials and thanks to side fx for making it public.
appreciate the time and effort you put into these, and just know i only watch your videos for houdini tutorials, have been for a while, cant wait for next part
the best thing is VEX syntax same as C# thnx you so much i can't say thnx enough also after all done if you feel combatable you can do some houdini engine for unity . but for now stick in houdini cuz you are a legend
Hi there, thanks for the tutorials it's been really helpful dipping my toes into Houdini and 3D in general for the first time. I'm just looking for clarification on a few points. Is there a reason we grab the values for position as: v@P.y v@P.x Instead of just @P.y etc? I was wondering about that since x, y, z are individual numbers themselves and not vectors? (Or are they?) E.G The x position is a single float of whatever you want it to be, rather than an vector comprised of three numbers right? I did try use @P by itself and it works, but I was wondering if that was just bad practice or something like that. Also wondering why we brought in colours as v@Cd.x (yz) instead of v@Cd.r (gb) as in tutorial 1. I assume they're interchangeable since it's basically displayed in x, y, z position in basically anything, but am just wondering what's best practice use for that.
Hey, thanks for the positive comment. Those are good questions that I should have clarified. To answer your first question, when saying @P.x, it is the float component of a vector. Houdini understands that - so it doesn't have to be in the form v@P.x. However, I prefer to always specify the attribute type. It is a good habit to get into and in general, coding is always cleaner when you're being specific. To your second question, there are three ways to get a vector3's components (keep in mind there are also vector4s and arrays which only use the third method that I'll mention). The first is @P.x, @P.y, @P.z. The second is the RGB syntax, @P.r, @P.g, @P.b. The third method which is also used for arrays is @P[0], @P[1], @P[2]. These are all doing the same thing but is there to make it intuitively easier. IE. When working with transformations, xyz makes sense. When working with colors RGB makes more sense. When working with arrays and longer form vectors, [0,1,2...] makes more sense. Hopefully that helps. Basically, these are not major concerns but more like small habits that I tend to have fallen into so I dont even notice them when making tutorials. Thanks for watching, cheers!😁
Why not just to use: float yPos = v@P.y; float xPos = v@P.x; if (yPos >= 0) { @Cd = {1, 0, 0}; } else { @Cd = {0, 0, 1}; } if (yPos >= 0 && xPos >=0) { @Cd = {0, 1, 0}; } What's the point of not using @Cd because it seems v@Cd "set" in this case it doesn't make any difference ?
@@antost_ Okay I just tried again and noticed, your code works... now I know whats happening when you mention @Cd = (1,0,0); if you use brackets color doesn't work, it works if you use set if you use parantehiss " { } " the color works without using set
I did some computer science and these intro courses can actually be a perfect case usage of them, since this is pure computer science and Iove it. I use python and C# so I am very used to these, thanks for these master classes
Thanks to you for all tutorials and thanks to side fx for making it public.
Thank you so much for this amazing tutorial series!
Your lessons are very helpful. Love the way you have set things out and explain this in an easy manner. Keep it up!
Thanks Thomas! I appreciate the kind words
appreciate the time and effort you put into these, and just know i only watch your videos for houdini tutorials, have been for a while, cant wait for next part
the best thing is VEX syntax same as C#
thnx you so much i can't say thnx enough
also after all done if you feel combatable you can do some houdini engine for unity .
but for now stick in houdini cuz you are a legend
Thanks you for sharing your knowledge. 👌
Thank you!!!
Love your videos.. Thank you!
Great stuff. Thanks!
bro this is what I need you are best you help me so much thanks
very helpful brother, thanks a lot.
you made my life easier
so interesting! thank you!
Lets dive into VEX
Thank You my friend really appreciate your efforts and very good explanation to understand the vex
Great Tutorial Thank You So Much ❤
This is great! A lot of times, I know what I want to do, but I just don't know the syntax.
Love you sir :*
thank you
Hi there, thanks for the tutorials it's been really helpful dipping my toes into Houdini and 3D in general for the first time. I'm just looking for clarification on a few points. Is there a reason we grab the values for position as:
v@P.y
v@P.x
Instead of just @P.y etc? I was wondering about that since x, y, z are individual numbers themselves and not vectors? (Or are they?)
E.G The x position is a single float of whatever you want it to be, rather than an vector comprised of three numbers right? I did try use @P by itself and it works, but I was wondering if that was just bad practice or something like that.
Also wondering why we brought in colours as
v@Cd.x (yz) instead of v@Cd.r (gb) as in tutorial 1.
I assume they're interchangeable since it's basically displayed in x, y, z position in basically anything, but am just wondering what's best practice use for that.
Hey, thanks for the positive comment. Those are good questions that I should have clarified.
To answer your first question, when saying @P.x, it is the float component of a vector. Houdini understands that - so it doesn't have to be in the form v@P.x. However, I prefer to always specify the attribute type. It is a good habit to get into and in general, coding is always cleaner when you're being specific.
To your second question, there are three ways to get a vector3's components (keep in mind there are also vector4s and arrays which only use the third method that I'll mention). The first is @P.x, @P.y, @P.z. The second is the RGB syntax, @P.r, @P.g, @P.b. The third method which is also used for arrays is @P[0], @P[1], @P[2]. These are all doing the same thing but is there to make it intuitively easier. IE. When working with transformations, xyz makes sense. When working with colors RGB makes more sense. When working with arrays and longer form vectors, [0,1,2...] makes more sense.
Hopefully that helps. Basically, these are not major concerns but more like small habits that I tend to have fallen into so I dont even notice them when making tutorials. Thanks for watching, cheers!😁
thanks
helpful
First you create a float data type yPos and then store ya vector position in it how does that make sense like v@P is stored in a float as a variable
cool
I am newish not sure why set is a function?
v@Cd = set(0,1,0);
rather than?
v@Cd = {0,1,0};
Tanks bro
5:20
It doesn't rotate? What should i do
Why not just to use:
float yPos = v@P.y;
float xPos = v@P.x;
if (yPos >= 0) {
@Cd = {1, 0, 0};
}
else {
@Cd = {0, 0, 1};
}
if (yPos >= 0 && xPos >=0) {
@Cd = {0, 1, 0};
}
What's the point of not using @Cd because it seems v@Cd "set" in this case it doesn't make any difference ?
i noticed with set you get the color, without set I just get black...
if(@P.y >= 0)
{
v@Cd = set(0,1,0);
@@PixelVagrant For my case it works in Houdini 20
@@antost_ Okay I just tried again and noticed, your code works... now I know whats happening when you mention @Cd = (1,0,0); if you use brackets color doesn't work, it works if you use set if you use parantehiss " { } " the color works without using set
@@PixelVagrant Don't forget to apply it on points, not primitives. @Cd is a vector attribute by default, so everything should work fine :)
@@PixelVagrant Glad it works for you!
Very helpful!