Many tasks in Houdini are carried out in the network editor and not in the viewport; every single step, whether bevel or extrude, for example, creates a new node. So it's all purely procedural, isn't it? The overview goes to zero in parallel with the working speed and the user goes to other DCCs that can be modelled directly. Modelling directly in Houdini has some clear advantages. In addition to the obvious saving of export/import loops, Houdini offers wonderful opportunities for automation, experimentation and endless iteration (or quick non-destructive customer feedback rounds) with its basic, but not exclusively, procedural approach.
Add to this a bit of VEX coding at the right time and the conversion of complex modelling setups into simple shareable or sellable HDAs, in which the artist simply has to adjust given parameters to create countless variants of the model, and you have a gigantic arsenal of creative possibilities. Unfortunately, Houdini is not always particularly i...
Hello Stranger!
This article is exclusively for Digital Production Subscribers.
If you are already subscribed, please log in below,
if you aren't subscribed, What are you waiting for?
Subscribers get
exclusive access to many articles like the one you just wanted to read,
can directly contact the authors or the newsroom,
can download many cool things from the archives,
support one of the last independent platforms weithout an "Algorithm"
and are granted exclusive bragging rights for being a better person!
Get an overview on what's available here, and access everything on the site!
If you need another reason,
here is a picture of the editorial cat,
which you'll be supporting as well!
