Material Display

[felipezumaeta]

Hi Paul,

I think I have mention this before, but do you think it's possible to create an option within the materials settings to create a custom display in the rhino viewport whitout affecting the octane material properties?
Right now if you use a Diffuse or a glossy material there is no problem with the display in the rhino viewport but as soon as you create a mix material it will be displayed in a grey color as the first attached image.

In the second image I'm showing how I will like to see the material in the viewport. For that now I'm duplicating the layers and I'm creating a basic rhino material to control the look but it really slow down my design workflow.

I hope this is possible,

Thanks!

[face_off]

Hi. Octane materials get converted to a simple Rhino material for the purposes of displaying in the Rhino Viewport. However there is no concept of a Mix Material in a Rhino material. So there is no easy way to convert an Octane Mix Material to the Rhino Viewport. At the moment the plugin will scan for any texturemaps in the diffuse, bump and opacity maps in the 2 materials connected to the Mix Material and use those maps in the Rhino material. But it does not scan for the RGB color.

Paul

[felipezumaeta]

So as the material get converted to a simple Rhino material in the background, do you think it's possible to add a material setting that override this default conversion with a simple custom mode. We will just need control of a diffuse and opacity (see attached images).

Viewport Display 01.jpg (80.32 KiB) Viewed 3172 times

Viewport Display 02.jpg (87.96 KiB) Viewed 3172 times

Thanks!

[face_off]

So as the material get converted to a simple Rhino material in the background, do you think it's possible to add a material setting that override this default conversion with a simple custom mode. We will just need control of a diffuse and opacity (see attached images).

This is technically possible, but a huge amount of work (since the material node pins are auto-generated from the Octane API - so this behavior would need to be overridden). The benefit of implementing such a solution would probably not justify the effort required to code it.

Paul