Paul_Newman

spoogicus
I love your salad dressing.

Thanks! Nice to know!

jimc
Paul,

Don't know if this is still relevant, but I found that importing an iges model into Houdini quickly bogged it. It seemed that every single little patch was it's own nurbs object. Made it very difficult to work with. Using the Nurbs modeling tool to export an OBJ file worked much better.

Thank you for posting your experience! It is relevant for any future plans involving Houdini, but not right now. I have for now reverted to using separate packages which specialize. For instance, using Silo for subD modeling and importing that into messiah Studio for staging and rendering.

I have all but given up on finding a suitable all-round package which truly excels at most aspects of 3D. Modo, although still lacking animation features, seems to be making steady progress. The closest I have seen must be Maya. I do entertain similar hopes for Houdini, but perhaps in a future version?

I do not know exactly what the vision of the Side Effects team is for Houdini.

Very often our thoughts in these matters are misplaced because we do not share the vision and challenges of the software creators. Sadly and practically, we need to work with what is at hand instead of fumbling with dreams of what tools might someday be.

Pardon my drama… I've just read two exciting chapters of The Three Musketeers to my family. ops:

Simon
Your best route for complex models is via rhino.

But the path from Rhino to Houdini using IGES is fine no matter what you modeled in Rhino?

Are there problems with imported IGES parts? For example an IGES file I imported has 5 parts which I'm doing stuff to in Houdini. Now I need to go back to make a serious change on the base NURBS object in Rhino and then export again, but this time there are 7 parts. Will the object replacement in Houdini behave correctly? Or will I need to manually sort and assign nodes to the parts again? That sort of thing.