Hi jonah,

> And you can't factor those into the equation of Rhino vs. MoI
> because MoI has no equivalent.

Just don't forget to also factor in the things that MoI has where there is no equivalent in Rhino, such as generating high quality mesh output including the option for having a clean wireframe with n-gons.

That's actually a hugely important function if you intend to generate mesh output from your model data, which is often needed for a variety of stuff such as exporting to a rendering program.

In fact there are many people who are primarily Rhino users who use MoI for its advanced meshing functionality alone since the meshing in Rhino totally fails for their needs.

It's a very important factor to consider if you will be needing to target mesh output.

Rhino tends to let a lot of people down at that particular stage in their workflow, and it is very frustrating when you have basically finished your model and then want to produce it as mesh data only to have it be completely mangled at that point.

- Michael