Default Material Behaviour (LET'S VOTE IT)

[moedeldiho]

Hi Aoktar, hi guys,

first off: terrific work as always - it's a pleasure to see how fast things develop!

After having done some larger projects in Octane & C4D (you might have seen Seed: https://vimeo.com/134957666 ) we've stumbled over Octane material's behaviour inside C4D:

- When deactivating a material's diffuse channel, it is set to a light grey default value. This seems a bit odd - expected behaviour in C4D would be to set the diffuse channel to pure black. That is especially bugging when you have to set up lots of emissive materials as most of the time you'd want the diffuse channel to be black.

Any feedback / opinions on that?

Thanks & Cheers,
Moritz

[aoktar]

Hi Moritz,
Thanks for posting your request. It looks a favorable request, but i'm worried about backward compatibility and different outputs than old versions.
Anyway i can change it if many people is agree with this request?

[bepeg4d]

For me it makes sense that disabling the diffuse channel it turns to black, even if the plugin has the same behavior of the standalone right now.
ciao beppe

[pxlntwrk]

no diffuse = black

[aoktar]

close to 500 view and votes are just 8. Come on guys, let's vote this.

[augdalmo]

I prefer it will be black.

I have also a question about the behavior of material when the scene will be edited in Standalone.
On material a black color (RGB 0,0,0) on C4D will be changed on grayscale 0,000 when exported on Standalone, this isn't good because if I need to change it with a little fade on other color I need to change the node, it's time consuming, mostly when there are several black materials.
Coud you fix this problem?
I some case I prefer the structure of material on C4D, but as you know there aren't perfect match on terminology between plugin and Standalone, for example on C4D there isn't a "grayscale image" node, but a "Float" option. It need one more click, because I must select "imagetexture" at first and then select "Float" (less use of memory). You know that specular and bump maps are usually a gray scale color images. So when the number of materials is high, there are a high number of more clicks.
Another question is if it's possible when "Edit in Standalone" to export only the materials of active objects.

Thanks. Manu

[aoktar]

I prefer it will be black.

I have also a question about the behavior of material when the scene will be edited in Standalone.
On material a black color (RGB 0,0,0) on C4D will be changed on grayscale 0,000 when exported on Standalone, this isn't good because if I need to change it with a little fade on other color I need to change the node, it's time consuming, mostly when there are several black materials.
Coud you fix this problem?
I some case I prefer the structure of material on C4D, but as you know there aren't perfect match on terminology between plugin and Standalone, for example on C4D there isn't a "grayscale image" node, but a "Float" option. It need one more click, because I must select "imagetexture" at first and then select "Float" (less use of memory). You know that specular and bump maps are usually a gray scale color images. So when the number of materials is high, there are a high number of more clicks.
Another question is if it's possible when "Edit in Standalone" to export only the materials of active objects.

Thanks. Manu

1-I see your reasons. But most important is C4D workflow for me. I can't change anything if it's giving problems on stability or speed of plugin. So i can't say anything for this without checking. It's a very complex part.

2-Name matching issues are due lot of changes in standalone and sdk. It's hard to follow each one and modify always. Also lot of people newer use standalone.

3- Maybe. But requires a lot of new revisions on plugin. I'm thinking to do optimisations for unused materials, etc.. We can use same functions for exporting. But each additional control can causes extra performance losses. You may know that plugin works and check every click or action while active. Iterates all data in scene. I can't give more info but you may feel the my drawbacks.

[aoktar]

I think to make as default to generate black and adding an option for gray output as current versions.

[jate]

24 votes later, and not a single one for "it's good as it is now" yet.