Michael you beat me to it. I was going to point to that same Rhino discussion. True, such a command can create some potentially bad situations if someone imports a non-manifold mesh without knowing it. But I have found that command to be very useful in Rhino. And probably it has practical use for archviz work. For example, you could easily import a Sketchup model, run MeshToNurb, then run MergeAllFaces to get a clean nurbs model on boxy geometry. But it takes some knowledge of the mesh you putting in before you do it! I guess many of the problems occur when the mesh is created first by someone else... Either way, I don't much see the point of converting something organic like that "pighead?" to be all planar nurbs faces. It's kind of useless, except as reference. So might as well just import a mesh, and forget converting to Nurbs...

jonah

Thanks for the info.
I see it pretty much as jbshorty:
this is not for importing organic forms into moi, but rather to import basic geometries as references.
I do mainly arch viz.

Hi okapi, sure I understand that.

And what will probably work better is if in the future I can add a polygon mesh object type as another kind of object in MoI, rather than trying to convert polygons to a bunch of little NURBS planes as the primary way to bring OBJ data over. (which is what you seemed to be asking about in the start of this thread)

If for example I added an OBJ import to the regular File/Open and File/Import commands that would do this kind of polygon-to-faceted-NURBS processing, it would get used by quite a few people for trying to bring in organic forms anyway, even though it would not work well for that. Pretty quickly I would be getting questions why opening OBJ files results in 200MB NURBS files that are totally unwieldy...

That's why that one particular method of conversion to NURBS is difficult to set up as the main way to handle polygon reference data, it would probably tend to work better if polygon data would stay as polygon data for the general case.

- Michael