Octane material slows down my viewport / c4d plugin

[ubicz]

Hello everyone,

I'm considering buying Octane licenses for c4d. Before that, there are some problems that bother me.
Recently I tried to manually reproduce VRay materials, that were applied to the tree models that I use. After applying the materials to the tree model, the whole viewport started to work EXTREMELY slow. With just one simple bush or tree model I can kill my whole scene, while normally (without octane materials applied to geometry) I can copy&paste numerous trees without even bothering to perform any optmalisation.
Didn't use anything special in the materials, one of them obviously uses Alpha, all others are straight-forwards glossy materials with some textures in Diffuse, c4d noise in roughness and one of them has texture in Specular.
this is extremely annoying, can anyone tell me, what can be causing the problem?

I don't think it's a common problem, since it would prevent anyone from using this software surely.

[aoktar]

I don't think it's a common problem, since it would prevent anyone from using this software surely.

Not a common problem. Bu i believe you have c4d shaders in Octane materials? Is it?

[ubicz]

Not a common problem. Bu i believe you have c4d shaders in Octane materials? Is it?

True, I use c4d shaders. Are they very heavy for Octane?

Anyway, it seems like it's some memory (RAM) problem. I restarted c4d and the problem is mostly gone (still slower, then with VRay materials, but not so slow to prevent me from working).
The problem appears only, when I apply Octane materials to huge portion of geometry. Then I have to reset the software and it starts to work again.
Is there any way to make those c4d shaders less heavy?

[aoktar]

True, I use c4d shaders. Are they very heavy for Octane?

Is not being heavy or not heavy. It's about how we use them. So will enlight you about question.
They are not sampled on render time for per pixel of visible screen points as should be. Because they are cpu shaders and we don't yet a shading language to re-write them in gpu.
So they are converted to pre-rendered images and mapped as an image. This give good results for uv based shaders but not 3d-spaces or pixel information based textures. This process is slow depend to size of baked image. Baking size can be set from settings->c4dShaders or on material commons->C4D_shaders parameter.

But i don't never advice to use these if you have possibilites to make by octane textures.

[ubicz]

But i don't never advice to use these if you have possibilites to make by octane textures.

Good to know. Apparently, I'm gonna have to study Octane shaders a little bit more. I really like c4d shaders though (maybe I simply got used to them) - I hope you will work it out in some release.

Thanks for help anyway