Rhino plug-in frustrations

Hi there !

And thanks to Chris for this Forum !

I use Rhino for modeling, and I'm trying to convince myself that Fryrender is the best render engine for me.
Why ?
-Fry's single sheet sub-surface scattering (SSSSS !) is a great feature for me because I deal with Architectural membranes.
-Fry's virtual reality looks real good, I just hope they will release it in my lifetime

But then I tried the demo.
The Fryrender plug-in for Rhino uses McNeel's "Render Development Kit".
In fact, the RDK interface is a -confusing- extra layer between Rhino and Fryrender.
By chance, one of Fran's posts helped me figure out how to apply a Fry material to a Rhino layer which is far from obvious.
But just when I thought my troubles were over, I started working on the material mapping in the Rhino rendered viewport, and things went haywire : the materials got mixed up on the display, and I simply could not go any further.
Materials were propagated to other layers, and changed randomly when I re-opened the file.

Cheers,

--
Olivier

On another forum, Fran told me that she doesn't use the RDK material editor because it loses material definitions between work sessions, plus other odd behaviors.
She assigns materials to layers through the Rhino layer manager, which avoids those problems.
I've been trying to do the same, but I find :

-Lots of clicks to get an existing material assigned to a layer
-Couldn't find out how to populate the material name in the layer manager
-The mapping in the viewport (with render preview) is not consistent with the mapping in the final render

Does anyone else use Rhino and Fry and could help me out ?

Cheers,

--
Olivier

I'm sorry...I don't use Rhino...

Maybe other user's can help you.

I hope you get the needing you are looking for.

Regards.