Hi Micha,

> So, couldn't you not try add advanced features per ini file switches?

It's possible, but in general .ini file switches work better as a switches that modify some existing behavior rather than enabling some large new feature area.

Having a large new feature totally hidden from all users unless they activate a special switch is just not an efficient way for me to develop stuff - it involves me doing a lot of work which is not likely to affect very many users since it would be such a hidden area.

When an .ini switch just modifies some existing behavior to help advanced users, that's a lot different kind of a thing as far as my workload goes, because a behavior modification is easy for me to implement. An entirely new way to save files is not the same amount of work as a small behavior modification though.

I'm not saying that it will never be done, but if the only way to implement this easily would be making it by default a completely hidden feature that only a few users would ever turn on, that just makes it hard for me to justify working on that area as compared to features that are more easily accessible and used by more people...


I'm pretty sure that we've had this exact conversation at least one time before...


- Michael

Hi Micha, so you wrote: "A little ini switch"

So the .ini switch itself is little, that's true - the problem is implementing the functionality that the .ini switch would then enable.

Please realize that just setting a switch does not make anything happen to a program - I have to write program code in order to make the program do any particular special things.

So it's not really just a "little" thing involved here - you're talking about implementing a major new file export feature...

- Michael

Steve wrote:
"When you export moi stuff, you can select which items to export. You can do it by styles or by object name, for instance. You can save those as separate mesh layers, then import them separately into one scene in say, Modo or C4D."

Like I sayed, I need the meshes for rendering of complex models like train interiors with many details or big ocean ships. Here at my webpage you can see what I mean ;)

http://www.simulacrum.de/

The complex models are meshed per MoI. I use MoI for meshing very often!

And I think I'm not the only user how need it. For example Cinema4D and the IO plugin - "Rhino.io is a connection and import/export plugin, that lets you directly open and save native Rhino files (3dm) from within MAXON CINEMA 4D."

http://www.rhino.io/

The IO tool open the 3dm file and uses the Rhino render mesh. Here I see a strong weak point of the workflow, where MoI could help a lot. The Cinema4D user could save the NURBS to a mesh 3dm with all layers and open it per IO. The meshes could be clean and low poly and not so crapy like from Rhino.
The same workflow is known for Modo:

http://www.rhino3d.com/resources/display.asp?language=de&listing=4480

It's a pity that the great NURBS mesher can't be more used for scene with a lot of layers, without to export/import layer by layer.

Yes, we talk about it in the past, but as I have seen this topic here I thought it's a good time to talk about it again. This thread was started from an other direction of need, but it show, that user like to mix NURBS and meshes in 3dm files. I hoped the pressure of the v2 beta time is gone and it's a good time talk about this feature again with more success.

So, we have two needs for meshes in 3dm:

* mesh export for rendering in Rhino3D, Cinema4D, Modo. Since MoI dosn't support render plugins, this export-for-rendering is interesting for MoI user too, not only for meshing-only-user. A MoI mesh-2-3dm would match current workflows, it's not a quick idea of a single render freak only. ;)

* MoI user would like to show her models in an mesh object content like people, trees&plants, cars ... all this stuff that is needed to present design or architecture models.

The question is too - will MoI be closed for mesh import for ever? If not, why not go the first step in v3?

Hi Micha,

> * mesh export for rendering in Rhino3D, Cinema4D, Modo.

Well, Cinema4D and Modo are already completely covered - use OBJ export to go from MoI into Cinema4D and LWO format to go from MoI into Modo - that's what Cinema4D and Modo users already use for mesh transfer.


> The Cinema4D user could save the NURBS to a mesh
> 3dm with all layers and open it per IO. The meshes could
> be clean and low poly and not so crapy like from Rhino.

They can already do this without that plug-in - just simply export from MoI to OBJ format and import the OBJ into Cinema4D. Layer assignments are preserved as material assignments into Cinema4D and you are also able to use n-gons and true welding unlike 3DM format.

3DM format is not a good way to store mesh data - it does not really make any sense to export meshes to 3DM format to go to Cinema4D or Modo when the OBJ or LWO formats are able to do it without having the limitations of 3DM format (again, no n-gons or proper welding in 3DM format is possible).


> The question is too - will MoI be closed for mesh import for ever?
> If not, why not go the first step in v3?

re: "why not go the first step in v3" - as I described earlier, it's because it requires some work for me to produce a 3DM mesh export, and there is not a good way right now to incorporate it into the UI in some normal way...

There are already many steps in place for mesh export since MoI v1 - I've worked hard to have very good support especially for the OBJ and LWO formats which are normally used by people who are exporting to mesh based programs already. Layers in MoI are preserved as material assignments when exporting to OBJ and LWO, and both formats also support n-gon polygons and also true welding.

- Michael

Consensus is that the Rhino IO plugin for C4D is not worth bothering with. This is because it reads Rhino's display mesh, which is not very good for importing (no welded vertices, etc). It's fine for working in the Rhino viewport. Rhino itself can export OBJ files which are a lot better.

Hi Steve, so the main thing that the RhinoIO C4D plugin can do for someone is to bring over stuff that is not able to go into an OBJ file like lights and cameras.

So if someone has put in a bunch of effort setting up additional stuff like that in Rhino instead of waiting to do it in Cinema4D then that could be useful to have that stuff transferred over.

But yes just for transferring geometry only I can't see why you would want to do that.

MoI does not set up lights or cameras in it, so that aspect of the plugin won't be of any particular use for trying to use 3DM files to transfer mesh geometry from MoI into Cinema4D - that won't be gaining anything and will actually lose functionality, particularly n-gons.

- Michael