OctaneRender™ 2019.1 RC5

[desire]

I'm using c4d plugin and Aoktar said that the following issues are related to SDK.

Meet again in latest 2019.1-RC3_r2 very noisy Shadow Pass while using Render Laryer feature
Here is example 3000 samples:

noisy shadow pass

And still no alpha using Affect alpha in specular material:

no alpha in spec mat

[Hesekiel2517]

Did something happen to the rounded edge feature? I can't prove it, but i think this used to work better some versions ago...

Fast Option:

Accurate Option:

[sethRichardson]

Did something happen to the rounded edge feature? I can't prove it, but i think this used to work better some versions ago...

Accurate or fast?

[Hesekiel2517]

Accurate or fast?

Updated the Post, sorry

[sethRichardson]

Accurate or fast?

Updated the Post, sorry

Yup that looks odd. I don't know why they have been struggling so hard with rounded edges in octane. It really is a simple feature that everyone has nailed down flawlessly (even other GPU renderers).

Think this has to do with how they do bump mapping in general. You cant do bump maps on small objects they lose all detail, and some maps give faceting.

That whole system needs to be looked at imo.

[Hesekiel2517]

But it's strange that the sample images in the releasenotes seem to work nicely. It's basically the same geometry...

[haze]

:-(

In 2019.1 RC3 (DAZ plugin) i get Cuda errors again when rendering out of core ...

Seems it doesnt depend on the NVIDIA driver i use. Last version i had running was Octane 4.X. This rendered even huge scenes without a flaw.

Mentioning it here since RC3 is the only 2019.1 avaiable for daz plugin atm and there was nothing mentioned beeing fixed for 2019.1RC5


01:02:15.261: +++++ Plugin running.
10:16:28.331: CUDA error 700 on device 3: an illegal memory access was encountered
10:16:28.332: -> failed to wait for event
10:16:28.332: device 3: path tracing kernel failed
10:16:28.334: Render engine failure occured! (WARNING)
10:16:28.336: CUDA error 700 on device 1: an illegal memory access was encountered
10:16:28.336: -> failed to wait for event
10:16:28.337: device 1: path tracing kernel failed
10:16:28.494: CUDA error 700 on device 2: an illegal memory access was encountered
10:16:28.495: -> failed to launch kernel(kernel54)
10:16:28.496: device 2: failed to update AI light
10:16:28.497: CUDA error 700 on device 0: an illegal memory access was encountered
10:16:28.498: CUDA error 700 on device 2: an illegal memory access was encountered
10:16:28.498: -> failed to copy memory to device.
10:16:28.499: -> failed to launch kernel(kernel54)
10:16:28.500: device 0: failed to update AI light
10:16:28.501: CUDA error 700 on device 2: an illegal memory access was encountered
10:16:28.502: -> failed to clear linear device memory
10:16:28.503: CUDA error 700 on device 0: an illegal memory access was encountered
10:16:28.504: -> failed to copy memory to device.
10:16:28.505: CUDA error 700 on device 2: an illegal memory access was encountered
10:16:28.505: -> failed to clear linear device memory
10:16:28.506: CUDA error 700 on device 0: an illegal memory access was encountered
10:16:28.507: -> failed to clear linear device memory
10:16:28.508: CUDA error 700 on device 0: an illegal memory access was encountered
10:16:28.510: -> failed to clear linear device memory
10:16:28.510: CUDA error 700 on device 2: an illegal memory access was encountered
10:16:28.511: -> failed to clear linear device memory
10:16:28.511: CUDA error 700 on device 0: an illegal memory access was encountered
10:16:28.512: -> failed to clear linear device memory
10:16:28.512: CUDA error 700 on device 2: an illegal memory access was encountered
10:16:28.513: CUDA error 700 on device 0: an illegal memory access was encountered
10:16:28.514: -> failed to load symbol data to the device(kernel data)
10:16:28.515: device 0: path tracing kernel failed
10:16:28.516: -> failed to load symbol data to the device(kernel data)
10:16:28.517: device 2: path tracing kernel failed
10:16:31.371: Render engine failure occured! (WARNING)
10:16:34.387: Render engine failure occured! (WARNING)
10:16:37.485: 3 render engine failures within a minute - giving up! (CRITICAL)

A few questions -
1. What GPUs?
2. What is your OS?
3. Does it also happen in RC2?
4. In preferences please increase your GPU Headroom to 1024. Does it help?

Thanks

[BorisGoreta]

Network rendering is not working properly, nodes are giving the result on the left, right is from the local GPUs.

[BorisGoreta]

VDB volume isn't working:

This is rendered in 2018.1.3.0 :