LocalDB saved materials and C4D noise issue.

[Ibycus]

I noticed recently that if I use a C4D noise node in an octane material setup and save that material into the local DB, when I reloaded it from the local DB the noise node will be converted to an image. I'm assuming this has to be done for some reason? The problem with this is if you have a complex setup and you'd want to adjust the noise after reloading it you have to go in and replace every instance of the noise and try to find the same settings you had. I've just been loading my old projects instead and copying the material over from there but it kind of defeats the purpose of saving the material in the data base.

I also noticed that when saving to the data base it will split the gradient node into RGB Spectrum's for each color making a much messier node tree.

Just wanted to mention this and see if it can be improved upon or not. I'm using alpha 3 v6 by the way.

[Yambo]

Yeah! i wanted to open a topic about that and didn't get to it.

This problems not happening only with the C4D noise, the localDB is messing out all complex materials. The think with the noise & gradient is new but beside that:

* The localDB duplicates all transform and projection nodes (very annoying issue when working with a lot of textures and want to control them with the same node)
*Create weird setups for gradient like the image above

Anyway really messed up all my materials.
Ahmet hope there is an easy solution for that.

Thanks.

[aoktar]

I noticed recently that if I use a C4D noise node in an octane material setup and save that material into the local DB, when I reloaded it from the local DB the noise node will be converted to an image. I'm assuming this has to be done for some reason? The problem with this is if you have a complex setup and you'd want to adjust the noise after reloading it you have to go in and replace every instance of the noise and try to find the same settings you had. I've just been loading my old projects instead and copying the material over from there but it kind of defeats the purpose of saving the material in the data base.

I also noticed that when saving to the data base it will split the gradient node into RGB Spectrum's for each color making a much messier node tree.

Because it saves the resulting material in Octane side, not C4D material. C4D shaders gone to imagetextures and colors in gradients goes to external RGB nodes. You can check what will be exported from "LV->Help->Show Octane NodeGraph" command while material selected.

[Ibycus]

I assumed it was something to that effect. Would there be a way in the future to keep material copies in local DB that are exact copies of the C4D setups so they are easily used in future projects and then only have them convert if you wanted to send them to stand alone?

I for one never use standalone so what this means for me is that I'd just stop storing my materials in the local DB and have to create project files that I'd store them in instead.

[aoktar]

I assumed it was something to that effect. Would there be a way in the future to keep material copies in local DB that are exact copies of the C4D setups so they are easily used in future projects and then only have them convert if you wanted to send them to stand alone?

I for one never use standalone so what this means for me is that I'd just stop storing my materials in the local DB and have to create project files that I'd store them in instead.

Content browser is for that to hold c4d setups. But unfortunately i couldn't found any proper way to support mix material system on.
Btw, yes it's due shader to image functionality in plugin. It convert them to image to use. And C4D shaders are not best way to work in plugin. You should be away to use them and try to go with Octane shaders. And wait a while until we bring new texture types with help of OSL system. You'll never use C4D shaders after that.

[Yambo]

And what about multiple Transform & Projection nodes when moving to localDB? Same?

[aoktar]

And what about multiple Transform & Projection nodes when moving to localDB? Same?

It's not about moving to LiveDB, about how i create. If you check the window which i said, propably you'll see double nodes. So it just get what i create.
Revisions can be complicated and may requires lot of modifications on codes and i should be carreful to don't cause stability issues for other parts. I'll take a look to check how easy.

[Yambo]

If you aware of it i'm relaxed. I'm sure when opportunity will come you would fix it.
This plugin become greater everyday, Hope you don't find this requests annoying.

Just trying to help push it to perfection.

[aoktar]

If you aware of it i'm relaxed. I'm sure when opportunity will come you would fix it.
This plugin become greater everyday, Hope you don't find this requests annoying.

Just trying to help push it to perfection.

Great to see, nothing is annoying. Just I don't wanna to work 7/24 anymore. I wish to go slower while keeping it stable also user friendly.

[Yambo]

Totally got you dude.