![]() ![]() ![]() My tip is to start learning Houdini full stop. Your friend's advice was correct in that you ultimately need to learn to write vex wranglers but it isn't absolutely mandatory, at first. It has turned out to be so handy that every TD uses wranglers, even if there is a SOP to do that work. Just so you know a Snippet VOP is how wranglers are exposed at the top so there you go! Wrangling was added to offer TD's a convenient way to wrangle attributes on geometry. Then wrangle VEX code is a logical progression. Once comfortable with VOPs, start inspecting the vex code generated to learn how the code is constructed. It offers everything you can do in wranglers but in a node network. VOPs create vex code behind the scenes in a way that you rarely can create code that doesn't compile. Actually learn VOPs first as Marc recommended. Many hscript functions have been ported to vex making for a somewhat seamless cross-over. To say “learn programming” to learn vex is way way WAY overkill for most of what we do. ![]() The things you learn when undertaking the daunting task of learning to write code. We are not talking about writing functions, code design such as OOP, large or small application development, etc. Marcįollowing from Marc who I agree with (learning by hacking and slashing at vex is a fabulous way to learn it)… When we are taking about using vex in the scope of using Houdini efficiently, we mean using vex functions for almost all the work we do to take advantage of the free threading from VEX evaluation inside Houdini. I know some “artists” who would frankly refuse to eben think about writing lines of instructions to “generate art” (instead of creating it with their own hands), if that resembles in any way your feelings about “coding”, I would, instead, use Houdini's network view based VOP editor and, over and over again, glimpse at the code it creates. On the other hand, “learning how to program” depends on what your personal background is. And there are many resources and options to learn JS, including your very own webbrowser (which, very likely, has a JS console and code completion). If you are specifically interested in VEX but don't want to learn it hands-on by following some tutorials and trial and error (which is how I learned programming in the 1970s/80s, though neither with VEX nor with Python), you could have a go at “classic” Javascript, which is very, very similar to VEX. Yet, I would not recommend Python, as this language is very “special” in some of its “grammatical” approaches (yes, you can use Python in Houdini, but VEX is the “natural” way and you get threading with it). Moin, Nick, I do agree with “aoakenfoAchiact”: I think it is a good idea to get some practical programming experience first. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |