![]() This is the core of how Tops interacts with the rest of Houdini, so its important to understand that early! If you refer to that elsewhere, in exactly the same way you'd use $OS or $T, tops now 'controls' that parameter, and will change what that value represents for each unit of work. Tops nodes create attributes for each bit of work you want to do, say to represent filenames, or for a wedged velocity. To drill down on that a little more, you might be used to putting $T or into sops parameters to do things, or $OS and $HIP elsewhere. Tops attributes, and lots of hython under the hood to do work. That's a very dry summary, but it important to keep these fairly simple core concepts in mind. Tops can also start many hython jobs in parallel, each one running whatever process you ask it to (mantra, a sim cache, ffmpeg, shotgun etc), and give you a gui to track all this. Tops creates variables (like hscript vars) that can be used to drive other nodes. If any of it isn't clear (or better, if you have fixes for my mistakes), let me know! It was a good time to update these notes, try and explain tops in terms Houdini artists can understand. I've been able to do some complex work setups that would be difficult or impossible without Tops. ![]() ![]() That said in December 2020 I had that 'click' moment. Lops was in a similar boat, but at least that had the excuse of deriving from USD and having to stick to those concepts. Feel free to skip down to the examples section if you just want hips vs my ramblings.Ī huge problem with Tops is terminology, documentation, workflow. This page starts off very wordy, sorry about that.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |