OctaneRender™ 2019.1 RC5

[Daniel_Ward]

Hi Guys,

I am finding that the Display name of ORBX Materials in the Local DB ends up being "Project Settings" for any materials created or edited in Standalone.
Interestingly ORBX Materials created through the ArchicAD Plugin have the Display name they were originally exported to the Local DB with.

In the screen capture below most of the materials were created from the ArchiCAD Plugin, but aside from the top 3 on the list which haven't been edited since in Standalone, they all display the "Project Settings" name, but when you hover your mouse over them the little yellow information pop-up shows the correct name of the ORBX.

This issue is present in all of the current builds of Octane, but it's only become apparent to me recently since I started trying to optimise them in SA using the node graph editor to set them up better. The "Project Settings" display name then gets carried over into the way the ArchiCAD plug in shows the Local DB as well.

Cheers, Dan.

[wallace]

Thanks team.
This denoiser bug seems to be worse now. The denoised material is much brighter and looks very different

I have looked into it again and fixed it, sorry for the inconvenience.

[J.C]

VDB rendering is still broken:

Code: Select all

OctaneRender Enterprise 2019.1 RC5 (6000006)

CUDA error 700 on device 1: an illegal memory access was encountered
  -> failed to wait for event
device 1: direct light kernel failed
CUDA error 700 on device 0: an illegal memory access was encountered
  -> failed to wait for event
device 0: direct light kernel failed

[haze]

VDB rendering is still broken:

Code: Select all

OctaneRender Enterprise 2019.1 RC5 (6000006)

CUDA error 700 on device 1: an illegal memory access was encountered
  -> failed to wait for event
device 1: direct light kernel failed
CUDA error 700 on device 0: an illegal memory access was encountered
  -> failed to wait for event
device 0: direct light kernel failed

I can't reproduce this. Is it possible I could have an ORBX to look at?

[J.C]

VDB rendering is still broken:

Code: Select all

OctaneRender Enterprise 2019.1 RC5 (6000006)

CUDA error 700 on device 1: an illegal memory access was encountered
  -> failed to wait for event
device 1: direct light kernel failed
CUDA error 700 on device 0: an illegal memory access was encountered
  -> failed to wait for event
device 0: direct light kernel failed

I can't reproduce this. Is it possible I could have an ORBX to look at?

Sure. Here it is.

[grimm]

J.C and Haze,

Just tested on Linux Mint, no errors, but the cloud looks strange. Is this how it's supposed to look?

Jason

[J.C]

J.C and Haze,

Just tested on Linux Mint, no errors, but the cloud looks strange. Is this how it's supposed to look?

jc-cloud-test+.png

Jason

No, it does not. In 2018 it looks different.

The issue with Cuda Error happens on OSX, on Windows it is ok.

[J.C]

In Octane 2018.x Metallic material's default Diffuse color is Black, in 2019.x it is White.This leads to unexpected differences in projects created in 2018.x or below.

[Elvissuperstar007]

material from 2019 loses mixture texture in 2018

[osiosiosi]

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)