[VEX for Algorithmic Design] E16 _ Geometry Functions

[@moviesgamer6574]

what a chad to provide this content for free , thank you junichiro sir

[@proker3d546]

I watch your lessons through an AI translator and I began to understand everything. No one could explain it clearly in their native language, but you explain it so clearly! Thank you very much, Horikawa!

[@fazlgumus9421]

Thank you so much your effort Mr Horikawa

[@Egokiv]

Thanks a lot, Junichiro!

[@benoithuguet5857]

Once again, thanks a lot Junichiro for this ! :)

[@wenmaowang5790]

Thank you, Junichiro. This is very very useful😁

[@mushogenshin]

Much appreciated, Junichiro!

[@eleazartheproducer]

Wonderful tutorial! Thanks bro!

[@jia-linzhou7542]

hi, thank you Junichiro san, the method you introduced to prevent exceeding point number in 36:00 is genius, I really love your detailed and efficient teaching style about design patterns, thank you so much for sharing your knowledge with us :]

[@marvelouswalrus949]

Simply brilliant! Thank you!

[@chrisrogers8370]

wow! what a thorough and expert resource to create and share! thanks!!!

[@peretiatko]

Great lesson 🔥

[@PointsDance]

Thank you so much!

[@PostmanStudio]

Here a quick tips, In node tab, if you type WA, you will get the attributes wrangle, no need to type the full name.

[@boole_cat]

Thanks, you are the Best

[@pompeyliang28]

Hi junichiro, I am trying to follow your example, and I have some problems now, whether you could help me to solve them?

[@maurypb]

In the sort vertex order segment, it seems simpler to get the backward prim's points with primpoints (instead of using primverts and vertexpoint), then use the reverse() function on the returned array. Then make a new prim from these reversed points and delete the old prim. Or, if you need to keep the primnum the same, get points with primpoints, and reset vert associations with setprimvertices in a loop, using the reversed points. Either way, this saves a second level of "indeirection" by going through the linear vertex indices step to get the points list.

[@18bovende]

Do you cover the spline() function somewhere?

[@sandegg2526]

Your video is pretty helpful ,thinks ; )

[@BizarreSelfProduction]

Great lesson! Thanks. Also, is there a way to feed the array into addprim, so that based on the len(array) it will create n-gone poly?

[@jamaljamalwaziat1002]

Addprim could accepy array ptnum to create geo without for loop

[@bass_journey]

The "sort vertex" part is difficult to visualise, although I understood what it does

[@FaitelTech]

Sometime Junichiro using uvsample function. Did I miss explanation of it in previous lessons? If anybody knows where to get more details about the function, please share a link.

[@maurypb]

my understanding (I'm a beginner, so take this with a grain of salt) is that uvsample returns another attribute at the same "location" as a specific point. It seems to me that "UV" is somewhat of a misnomer, because you can use P, or any other attribute. So, for instance, lets say you have an attribute "pscale" on every point of a geo. You'd like to know the interpolated pscale at a point xyz on the surface - but xyz might not be at a vertex, but between them. uvsample lets you get the interpolated pscale when given the surface position. Let's say you have the vector "position" somewhere on the geo's surface. You can get the pscale at that point like this: uvsample(0,"pscale","P",position);

[@aieuosama]

everytime I reach 1:13:30 coding, houdini crashes. does this happen to anyone

[@teamsakura3678]

only if you are using a laptop

[@bigasuo231]

Thanks a lot, Junichiro!