Version 3.06-TEST4.1 (WORK IN PROGRESS BUILDS) Tweet

[stefano-dear]

I have the same problem. Very slow material previews. Macbook Pro 2016 with 1xBizon Box eGPU. i hope there is a fix.

Can you give me some idea?
Where's textures? How much is number of preview samples?

My textures are on my internal SSD disk, and I have another path on my NAS server for the textures of some 3d models library. Usually I have 20-30 materials...
But often it's very slow even when you change some parameter of the material.


Thank you!
Stefano

[aoktar]

My textures are on my internal SSD disk, and I have another path on my NAS server for the textures of some 3d models library. Usually I have 20-30 materials...
But often it's very slow even when you change some parameter of the material.
Thank you!
Stefano

Still it's not clear for me.
Try to disable material/opengl previews and test it.
Also try with textures from project path.
Check main gpu has low priority.
Check preview/opengl samples from settings.

[Terryvfx]

@Stefano if your textures are in .jpg or .png when they are too big or too many it's gonna take some time for the plugin to load them, I suggest converting them to uncompressed tiffs to see if you have any gain in performance.

[aoktar]

@Stefano if your textures are in .jpg or .png when they are too big or too many it's gonna take some time for the plugin to load them, I suggest converting them to uncompressed tiffs to see if you have any gain in performance.

This should not be much problem when texture caching enabled.

[Terryvfx]

@Stefano if your textures are in .jpg or .png when they are too big or too many it's gonna take some time for the plugin to load them, I suggest converting them to uncompressed tiffs to see if you have any gain in performance.

This should not be much problem when texture caching enabled.

I see, sorry I wasn't aware of this new feature but would this also be true for textures that you are loading for the first time? I mean decompressing a big texture would certainly account for some lag.

[zoppo]

Maybe you have some texture paths in Cinema's preferences? That can slow down materials a lot.

[Cheiser]

In redshift render you can use any C4D shader (including Layer system) for texture source.
Any chance we can get it in Octane?

[aoktar]

In redshift render you can use any C4D shader (including Layer system) for texture source.
Any chance we can get it in Octane?

??? It's working since long time with c4d shaders. But it's like baking a shader to images. So not a runtime calculation and not adviced. Wait until OSL version out for much better support.

[Cheiser]

Wow. Just found it. I was looking for C4D shader node from the list, but there is no node like this.
But then i create Layer or C4D shader inside material dropdown list - it creates Layer and "shader-name" node. Wow. WOW!

[indigoGnat]

Thanks Ahmet for the hard work. Here's an example of the fruits of your labor.

I've rendered two images, one interior, and one not. The interior scene saw no speed-ups, at least in this scene, from adaptive sampling. However the robot render went from 4 minutes @ 4k resolution and 4k samples on PT, to 1 minute and 20 seconds with AS on.

What settings were you using for the Adaptive rendering on the interior scene? Render times?