OTOY Forums

Hello,
lately I have been working in quite complicated scenes with 30-50 materials.
I often find myself waiting quite long for the material previews to update.
And the texture manager runs very slow in these large scenes.

What triggers octane to update all materials?
Sometimes I make a change in one texture and octane goes through and updates all materials in the scene.

Is there any way I can control or disable the material updates?
I have lowered the material preview samples and turned off "use octane for opengl previews".

Do you have any general tips on how to speed up my workflow when working with many materials in one scene?

Material previews are not blocking any proces in C4D. Why do you wait?
Updates are triggerred by c4d. But mix material system wil do extra operation for triggering. I'm curious how one material will force updates on rest of materials.

I learned from a Raphael Rau tutorial that you can pause the render in the Live Viewer and that will allow all of those swatches to update on your materials since those swatches actually have to be rendered by the Octane engine; they are not cached like C4D materials probably are.

Hope this helps,

-Ben

prisonbread wrote:I learned from a Raphael Rau tutorial that you can pause the render in the Live Viewer and that will allow all of those swatches to update on your materials since those swatches actually have to be rendered by the Octane engine; they are not cached like C4D materials probably are.

Hope this helps,

-Ben

Thanks, but the problem in these scenes is that the previews update too often, and with so many materials in the scene it takes time.

aoktar wrote:Material previews are not blocking any proces in C4D. Why do you wait?
Updates are triggerred by c4d. But mix material system wil do extra operation for triggering. I'm curious how one material will force updates on rest of materials.

It might be something with the mix materials, I will look at the scenes again and try to see exactly when this update triggers.

Update:
This seems to have been an Xref related issue, the scene material previews and the Texture Manager behave much better after I imported all Xrefs into the scene.