Hi Michael and good day,

I think that i'm not doing a mistake if a create this new thread, starting from my previous question http://moi3d.com/forum/index.php?webtag=MOI&msg=7904.5,
followed by your exhaustive reply at http://moi3d.com/forum/index.php?webtag=MOI&msg=7904.6.

Maybe this thread "Looking for a compromise for a good workflow involving both Moi V3 and Rhino V5",
could be useful for some others interested to the same topic.

Well....i did a little test based on your suggestions.

> Yes, that's currently the normal behavior - MoI goes through some effort to preserve object attributes of Rhino-specific things that MoI itself does not use,
> but that will only happen for objects that have not been edited in MoI. When you do the step of moving the sphere, that's a type of edit and
> it's basically the equivalent of the original sphere being destroyed and a new sphere with different coordinates being created.
> With the object being changed and having a different id, MoI will no longer find the original Rhino attributes that were assigned
> to the original sphere and so you get the result you see here.
> ....
> One thing that might work better is to assign your material by layer rather than having it assigned as an override
> to the individual object like you have done here.
> To do that in Rhino in the object material properties have that set to "Assign material by: Layer",
> and then set your material on the layer.
> Then as long as you don't modify the Styles list in MoI (which map to Layers in Rhino),
> the layer properties should round trip back to Rhino I think.
> Then I think you can create new objects in MoI, the materials will still work because the default for a new object is to have materials by layer.

I experienced this behavior and in fact all the materials managed in Rhino are maintained also in Moi, ONLY if i assign the materials directly to the Rhino layers.
This is could be a good starting point.
But unfortunately, as you told me, as long as i do any modification to the styles list in Moi and overwrite the .3dm file, all the materials infos are lost inside Rhino.
Pity.....
Maybe someone with a good skill with the Rhino's API or in the .3dm file format in general, wants to write a plugin that will preserve in some manner, this information managed by Rhino and destroyed by Moi.
Something like a file processor that extracts the Rhino specific data from the .3dm file, stores them in some place, and joins them again with th file saved in Moi.

Who knows ??? :))

But...in relation to your second indication :

> When you start a fresh 3DM file in MoI, it will default to writing Rhino v4 format 3DM files.
> But when you open a v5 3DM file originally created by Rhino v5 into MoI,
> MoI will remember it was a v5 3DM file that was opened and will then write a v5 file when you save it out again.

I'm sorry...i did what you said but every time i load in Moi any file first created in Rhino 5.0 3dm format, and save back from Moi, then reloaded in Rhino and saved it again, Rhino always shows me the popup that tells me that the file is a 4.0 3dm format,
and asks me if i want to maintain that format or save it with the new 5.0 format.

I've made more then one test for this, and the behavior is always the same, regardless of first creating the files in Rhino rather than in Moi.

I don't know.....

Anyway, i will stay tuned for this situation...

Thank's a lot for your suggestions and have a good day at work !

Marco.