OTOY Forums

after watching this video i come to a conclusion i had before...
the render settings (for picture viewer) should have the full octane (render) options, not only the kernel mode.
a "copy settings from live viewer" button would be helpful there then

i sometimes use different render settings for different cameras (in the same file)
so this would allow to have optimized render settings for each camera
and not to be force to manually set them again in the liveviewer/settings window

another way would be that all settings can be set per camera
but i think it would be better be the way above.

just a suggestion

indexofrefraction wrote:in my view the general logic of menus/settings could be improved a bit anyway...
the render settings (for picture viewer) should have the full octane render options, not only the kernel mode.
a "copy settings from live viewer" button would be helpful there then
just a suggestion.

to explain why:
i sometimes use different render settings for different cameras.
it allows to have optimized render settings for each camera.

i don't ignore this ideas. I'm taking some notes for that and i'm going to check when i have time.
Thanks

aoktar wrote: i don't ignore this ideas. I'm taking some notes for that and i'm going to check when i have time.
Thanks

tried to say it more nicely in my 2nd post (& explain better) ... but you got my 1st post before i deleted it !
u work too much still... thanks for that!

We noticed today that if gpu memory / max tricount / something else is exceeded and *** Render failure **** is displayed, it is not possible to restart the render.
Instead, I have to close cinema 4d entirely, force quitting it because it is unable to close by itself.
Is this a known effect?

Edit:

We noticed something unpleasant today, which might or might nog be a fluke.
Last night we started a render which never went past the preparing sky maps stage.
Octane was stuck on preparing sky maps for 10 hours.
Unfortunate for us, we have to finish this project by friday!

iFloris wrote:We noticed today that if gpu memory / max tricount / something else is exceeded and *** Render failure **** is displayed, it is not possible to restart the render.
Instead, I have to close cinema 4d entirely, force quitting it because it is unable to close by itself.
Is this a known effect?

Edit:

We noticed something unpleasant today, which might or might nog be a fluke.
Last night we started a render which never went past the preparing sky maps stage.
Octane was stuck on preparing sky maps for 10 hours.
Unfortunate for us, we have to finish this project by friday!

can you try with only octane in plugins folder? Posibily a confusing with some one

iFloris wrote:We noticed today that if gpu memory / max tricount / something else is exceeded and *** Render failure **** is displayed, it is not possible to restart the render.
Instead, I have to close cinema 4d entirely, force quitting it because it is unable to close by itself.
Is this a known effect?

Edit:

We noticed something unpleasant today, which might or might nog be a fluke.
Last night we started a render which never went past the preparing sky maps stage.
Octane was stuck on preparing sky maps for 10 hours.
Unfortunate for us, we have to finish this project by friday!

We've been experiencing the exact same problems here. Yesterday was madness. Render Failures and the occasional sky maps forever problem. This is on a pretty big project with lots of polys.

Alec

ASyme1 wrote:
We've been experiencing the exact same problems here. Yesterday was madness. Render Failures and the occasional sky maps forever problem. This is on a pretty big project with lots of polys.

Alec

"Render Failures" is a error on cuda renderer. most probably, a texture count or memory problem on your scene. Something exceed your gpu(s) limits. Check with one gpu(non output gpu) otherwise try with less objects or textures.

Hi Aoktar,

Please can you confirm whether support for Mograph Shaders (Color Shader, Multi Shader) will be implemented further down the line, or if you think it will not be possible.

I am working on a project now that uses the Mograph Color Shader and would love to be able to use Octane to render it For now I will have to use standard/physical render for this one.

Thanks!

Iksmada

Iksmada wrote:Hi Aoktar,

Please can you confirm whether support for Mograph Shaders (Color Shader, Multi Shader) will be implemented further down the line, or if you think it will not be possible.

I am working on a project now that uses the Mograph Color Shader and would love to be able to use Octane to render it For now I will have to use standard/physical render for this one.

Thanks!

Iksmada

At the moment, Octane has no similar shader. But this is my todo list. I'm trying to get this effect.

aoktar wrote:can you try with only octane in plugins folder? Posibily a confusing with some one

Hello aoktar, sorry for the late response.
We finished our project in time, thanks in no small part to your great plugin!
This afternoon I tried the project both with only octane in the plugins folder as well as my regular configuration but I was unable to reproduce the problem.

Could it be the case that this sometimes happens on large scenes?
ASyme1 pointed out that he was having the same problem on a large file as well.
In this project we are working with 16 million tris, a few hundred meshes and 116 rgb textures.