The original problem we are trying to solve:
Is a combination of both JD1 & JD2. (I’m calling thee JDX to differentiate form my original requests numbers).
JD1: Yes, we want this. We want to have a way to give each object a Rhino viewport material + an Octane material + maybe a Vray Material (less often these days) + maybe a Bella material?
The fundamental problem is that our preferred, easiest, fastest and most consistent (because we also use it in Modo) render engine is Octane. And we can’t even see the RGB value of our octane materials in the Rhino viewport. So we want to have also separate assignment for Rhino viewport.
JD2: At the same time that we are seeing something on a floating frame buffer in Octane with Octane materials we also want to see in in the Rhino Rendered Viewport with Rhino materials. Not ‘per object’ like you describe, but globally.
The new opportunity this presents:
If we have like a material table of some sort, we can assign different materials for different criteria, not just render engine of choice. Something like this:
For example we could use libraries for visual management of how are we building these models (we do a lot of prototyping): CNC? Formlabs? FDM? What material? in-house? Outsourced?
We could also have materials to show if a model has unwrapped meshes yet of not? Very important for our AR work.
I’m confused as to why JD1 and JD2 and very different? COuldn’t a render engine we just another viewmode? Just like Rantrace (Cycles) is doing, and if I recall correctly Maxwell had a version of this too, where you could set a viewport to show you Maxwell progressive rendering.