I would agree with what has been said above. You have to talk about a pipeline, not a single piece of software. My traditional route, for example, would have been:
Rhino(Modeling) -> ZBrush/Mudbox(Texturing + Finishing) -> Maya(Animation/Rendering)
I actually discovered MoI due to its rather awesome mesh generation. I had Maya artists going nuts with the .obj files generated from old versions of Rhino, MoI fixed that - then I started playing in the MoI modeler and found that I could work almost twice as fast as in Rhino, and even work on my tablet. More recently I moved from working exclusively in the film industry into a small industrial design startup. Now there is more emphasis on fast renders and 3D printing/CAM. This is my current pipeline:
MoI(Concept/Initial Model) -> Rhino(Finishing, Render) -> MoI(Mesh Generation/3D Print) -> Rhino(CAM generation)
I can't express how powerful this simple pairing of software (MoI + Rhino) is. Now that there is a decent and fast render engine inside of Rhino (Brazil + Neon) I don't need Maya (which required a time investment to get a good render and is still very overpriced). I can cut and paste and move back and forth seamlessly between MoI and Rhino.
MoI excels in areas where Rhino is a bit deficient (UI, for example), and Rhino has an expanded feature set that covers rendering and parametric design (Grasshopper), as well as old-school scripting with Python/Rhinoscript.
All that said, depending on the industries you work with people will often have a preference for Solidworks or Catia. Personally, I hate them.
-FDP
|
