OTOY Forums

Posted: **Wed Dec 16, 2020 11:27 am**

As you can see the c4d status bar indicates remaining cspp but you cannot see the octane status bar overlay on the render. Also I realised the Picture Viewer doesnt update the progress of the render. You see the rendered image after its complete. This is a different issue than my previously reported bug with black screen and no results in picture viewer. (not all the passes requested for tonemapping are enabled denoiserThread0: CUDNN_STATUS_BAD_PARAM)

Posted: **Wed Dec 16, 2020 11:33 am**

aoktar wrote:Please change BUFFERTYPE=HDR not HDR-HALF, it's default and will fix it.

That indeed solved the status bar issue and black screen renders. It takes longer than previous stable release to render the scene though and I get this again at the end:

denoiserThread0: CUDNN_STATUS_BAD_PARAM
. Restart required
not all the passes requested for tonemapping are enabled

Edit: I get this error with or without Denoiser enabled.

Posted: **Wed Dec 16, 2020 11:35 am**

Mikla wrote:
aoktar wrote:Please change BUFFERTYPE=HDR not HDR-HALF, it's default and will fix it.
That indeed solved the status bar issue and black screen renders. It takes longer than previous stable release to render the scene though and I get this again at the end:

denoiserThread0: CUDNN_STATUS_BAD_PARAM
. Restart required
not all the passes requested for tonemapping are enabled

what's GPUs and driver? and RTX enabled?

Posted: **Wed Dec 16, 2020 11:38 am**

Driver: 457.30 3080 and 1070ti

Posted: **Wed Dec 16, 2020 11:40 am**

Mikla wrote:Driver: 457.30 3080 and 1070ti

please send me the scene if you can

Posted: **Wed Dec 16, 2020 8:03 pm**

BUG:
Channel Inverter does not work correctly for Normal maps.

Posted: **Thu Dec 17, 2020 7:44 am**

aoktar wrote:
Mikla wrote:Driver: 457.30 3080 and 1070ti
please send me the scene if you can

I'm tryıng to replicate the error with another scene as I'm not allowed to share the one I'm working on.

It's a heavy scene with lots of instances, geometry and scatter. Getting this on the console:

Code: Select all

CUDA error 2 on device 0: out of memory
  -> failed to allocate device memory
OptiX error for device 0: [ERROR] "sbt->raygenRecord" is null
OptiX API error for device 0: Invalid value
device 0: RTX picking failed
CUDA error 2 on device 0: out of memory
  -> failed to allocate device memory
OptiX error for device 0: [ERROR] "sbt->raygenRecord" is null
OptiX API error for device 0: Invalid value
device 0: RTX picking failed
OptiX error for device 0: [ERROR] "sbt->raygenRecord" is null
OptiX API error for device 0: Invalid value
device 0: path tracing kernel failed
not all the passes requested for tonemapping are enabled

The scene renders fine on previous stable. (2020 1.5)

Posted: **Thu Dec 17, 2020 8:15 am**

Mikla wrote:
aoktar wrote:
Mikla wrote:Driver: 457.30 3080 and 1070ti
please send me the scene if you can
I'm tryıng to replicate the error with another scene as I'm not allowed to share the one I'm working on.

It's a heavy scene with lots of instances, geometry and scatter. Getting this on the console:
Code: Select all
CUDA error 2 on device 0: out of memory
  -> failed to allocate device memory
OptiX error for device 0: [ERROR] "sbt->raygenRecord" is null
OptiX API error for device 0: Invalid value
device 0: RTX picking failed
CUDA error 2 on device 0: out of memory
  -> failed to allocate device memory
OptiX error for device 0: [ERROR] "sbt->raygenRecord" is null
OptiX API error for device 0: Invalid value
device 0: RTX picking failed
OptiX error for device 0: [ERROR] "sbt->raygenRecord" is null
OptiX API error for device 0: Invalid value
device 0: path tracing kernel failed
not all the passes requested for tonemapping are enabled
The scene renders fine on previous stable. (2020 1.5)

Messages are from RTX functions. Try without it if you can't share anything

Posted: **Thu Dec 17, 2020 9:57 am**

hi,
this release is highly unstable on my side.
I notice that the interactivity is very reduced the objects(obj,mat, param...) that we manipulate are not always updated in the Liveviewer.
Sometimes when we change a parameter on an object, all the cpu are loaded at 100% and we have to wait for octane to give us back control, sometimes several minutes.
All in all here's a collection of some bug reports if that helps.

ps:These concerns appear with this version 2020.2, everything works fine with 2020.1.5.

thanks

Posted: **Thu Dec 17, 2020 12:04 pm**

pxlntwrk wrote:hi,
this release is highly unstable on my side.
I notice that the interactivity is very reduced the objects(obj,mat, param...) that we manipulate are not always updated in the Liveviewer.
Sometimes when we change a parameter on an object, all the cpu are loaded at 100% and we have to wait for octane to give us back control, sometimes several minutes.
All in all here's a collection of some bug reports if that helps.

ps:These concerns appear with this version 2020.2, everything works fine with 2020.1.5.

thanks

I don't know what's the issue on your side BUT there is NOT ANY Changes in plugin side to cause these kind of issues. Please be more specific and tell is it for one scene or many? And give more info, what's OS/C4D versions, GPUs, RTX usage.

EDIT:
I see some logoutputs, thanks for that. I see only render failures in one log, there's nothing for error in others.

OTOY Forums

Cinema4D version 2020.2-RC5 (Release candicate) 23.12.2020

Re: Cinema4D version 2020.2-RC5 (Preview release)

Re: Cinema4D version 2020.2-RC5 (Preview release)

Re: Cinema4D version 2020.2-RC5 (Preview release)

Re: Cinema4D version 2020.2-RC5 (Preview release)

Re: Cinema4D version 2020.2-RC5 (Preview release)

Re: Cinema4D version 2020.2-RC5 (Preview release)

Re: Cinema4D version 2020.2-RC5 (Preview release)

Re: Cinema4D version 2020.2-RC5 (Preview release)

Re: Cinema4D version 2020.2-RC5 (Preview release)

Re: Cinema4D version 2020.2-RC5 (Preview release)