The fact that you need to assign materials to your Rhino file before importing to avoid D5 grouping each individual object is crazy.
It basically means double the work: First put materials in Rhino and then put them all over again in D5…
Just make it so that the importer does not group objects per Rhino material at all! Please!
Let’s keep individual objects. Thanks!
Hello.
D5 currently recognises materials as different materials only if they are differentiated in the modelling software.
This makes perfect sense. That is not the problem.
The problem is D5 does not recognize different objects if they do not have different materials in the rendering software.
For instance, if I have a Rhino model with balustrades, doors, windows, slabs, columns, etc. unless I apply materials inside Rhino before exporting, D5 interprets the entire model as one single object, that means I can only apply one single material to it inside D5. Naturally one would want to apply Glass to windows and concrete to slabs…
Thanks for the suggestion. The rhino plugin for D5 is currently unable to distinguish different objects in a model file for now. It may be optimised in the future.
That would be great 
Please do use the rhino layers, so each layer can get different material inside D5.
now i have to manually ad material inside rhino AND then again in D5 which is a terrible workflow. many users use layers to separate materials, or layer colors, all this needed to be supported by D5 to enable a nice and fluent workflow for rendering.
thanks!