OctaneRender 2020 for DAZ Studio [TEST and STABLE] Tweet

[Yorgurd]

Hello. I've been dealing with tons of issues lately with Octane 2020. I'm loading a scene I set up the other day and the first render goes smoothly. However, when I'm trying to move things around like moving a character, moving a light source I get this error:

06:36:50.942: CUDA error 700 on device 1: an illegal memory access was encountered
06:36:50.942: -> failed to wait for event
06:36:50.942: device 1: path tracing kernel failed
06:36:50.944: CUDA error 700 on device 0: an illegal memory access was encountered
06:36:50.944: -> failed to wait for event
06:36:50.944: device 0: path tracing kernel failed
06:36:51.003: Render engine failure occured! (WARNING)
06:36:53.943: Render engine failure occured! (WARNING)

It's either that or error 719.

So I restart Daz and the same thing happens - first render goes without any issues, I'm trying to do the second (or sometimes third) - error.
I found out it's not this scene specifically. It happens randomly. Sometimes each render, sometimes once a day. Way often when the scene is so big it starts using out of core ram (20 GB available for Octane).
It never happened to me in Octane 2019.

Octane 2020.1 version
Daz 4.12
NVidia drivers: 451.48
System: Windows 10, 2x RTX 2080 Ti (with NVlink), 1950X Threadripper, Asus ROG Zenith Extreme, 64 GB RAM, 1200W Platinum power supply.

Edit: SOLVED
Error 700: If anyone has the same issue, I had Parallel Sampling set at 16 which was way too much in heavier scenes. I set it up to 2 - 4 when I'm close to running out of VRAM and 32 (max) in lighter scenes which saves A LOT of rendering time!
Error 719: Turning off AI Lights seemed to do the trick for me. No more issues and render engine failures.

Question:
1. Can I use RTX acceleration when I'm out of VRAM and forced to using out-of-core? It seems like error 700 (illegal memory access) happens quite often then. Not sure if something is wrong or I simply can't.

[face_off]

Hello. I've been dealing with tons of issues lately with Octane 2020. I'm loading a scene I set up the other day and the first render goes smoothly. However, when I'm trying to move things around like moving a character, moving a light source I get this error:

06:36:50.942: CUDA error 700 on device 1: an illegal memory access was encountered
06:36:50.942: -> failed to wait for event
06:36:50.942: device 1: path tracing kernel failed
06:36:50.944: CUDA error 700 on device 0: an illegal memory access was encountered
06:36:50.944: -> failed to wait for event
06:36:50.944: device 0: path tracing kernel failed
06:36:51.003: Render engine failure occured! (WARNING)
06:36:53.943: Render engine failure occured! (WARNING)

It's either that or error 719.

So I restart Daz and the same thing happens - first render goes without any issues, I'm trying to do the second (or sometimes third) - error.
I found out it's not this scene specifically. It happens randomly. Sometimes each render, sometimes once a day. Way often when the scene is so big it starts using out of core ram (20 GB available for Octane).
It never happened to me in Octane 2019.

Octane 2020.1 version
Daz 4.12
NVidia drivers: 451.48
System: Windows 10, 2x RTX 2080 Ti (with NVlink), 1950X Threadripper, Asus ROG Zenith Extreme, 64 GB RAM, 1200W Platinum power supply.

Edit: SOLVED
Error 700: If anyone has the same issue, I had Parallel Sampling set at 16 which was way too much in heavier scenes. I set it up to 2 - 4 when I'm close to running out of VRAM and 32 (max) in lighter scenes which saves A LOT of rendering time!
Error 719: Turning off AI Lights seemed to do the trick for me. No more issues and render engine failures.

Question:
1. Can I use RTX acceleration when I'm out of VRAM and forced to using out-of-core? It seems like error 700 (illegal memory access) happens quite often then. Not sure if something is wrong or I simply can't.

These are questions/issues for OTOY, so I recommend asking them in the Octane Standalone release thread.

Thanks

Paul

[Sorel]

Paul will we be able to use the upcoming embergenfx with the daz plugin? I dont knownif that's something you have information on yet.

[face_off]

Paul will we be able to use the upcoming embergenfx with the daz plugin? I dont knownif that's something you have information on yet.

I don't know, sorry. However given the DAZStudio plugin does not currently support more basic Octane features such as the Universal Camera, Octane Lights, etc, my guess is that support for Embergenfx would not be simple. You would however be able to export the scene to ORBX and render with Embergenfx inside Octane Standalone.

Paul

[Tugpsx]

Anyone have suggestion for the render settings or are the default settings in 2020 ok? If i recall there were some decent render settings for portrait, indoor and outdoor, landscape renders and more, just can find them anymore.

[solomon]

Hi Paul, thanks for the great work on the Octane plugin for DAZ Studio.

I have a quick question, is it possible to have a one to one texture look and feel for the character shaders in Iray? Octane tries to convert the Iray materials but when compared, it looks like there is something lacking. Is there a setting we might be missing? or this is what we can expect for the characters to look like after the default conversion?

[Banti]

Hi Paul, thanks for the great work on the Octane plugin for DAZ Studio.

I have a quick question, is it possible to have a one to one texture look and feel for the character shaders in Iray? Octane tries to convert the Iray materials but when compared, it looks like there is something lacking. Is there a setting we might be missing? or this is what we can expect for the characters to look like after the default conversion?

The attachment Screenshot 2020-07-20 09.51.56.png is no longer available

The attachment Screenshot 2020-07-20 10.10.37.png is no longer available

1)
The auto-conversion will usually not give you the results you want. Especially with skin materials, you almost always have to adjust the bump strenght (usually 0.05-0.15 are good values) as well as the specular roughness (0.2-0.5 are the usual values). Another big thing to keep in mind is the lighting. Octane cannot convert Iray lights, but you can use HDRIs and emissive geometry. The daylight light you use in your pictures makes characters look flat more often than not. Try to use HDRIs and emissive planes.

2)
Looking at your characters eyes, it seems there are some artifacts. Set the ray-epsilon value in the render settings to its minimum value to prevent this.

3)
Make sure that the Surface Material Filter (in the preferences tab) is empty. By default, i think cornea and eylashes are filtered out and not rendered. I attached a picture to show you what it should look like

[Hun73rdk_1]

I have a problem came back to daz after a week of being away and not daz crashes on startup

it happens with version 2020_1_0_54 and 2020_1_0_55 but works with 2019_1_4_46
i am on win7 i7 6700k and 64gb ram and a 1070gts and a 2070s with latest nvidia driver and i had no crash over a week ago at all i have no clue what happen.

[face_off]

it happens with version 2020_1_0_54 and 2020_1_0_55 but works with 2019_1_4_46
i am on win7 i7 6700k and 64gb ram and a 1070gts and a 2070s with latest nvidia driver and i had no crash over a week ago at all i have no clue what happen.

This looks similar to the other crashes that users have reported. Otoy may have resolved it in 2020.1.4. I will post a build here shortly.

Paul

[face_off]

I have updated the installers at the top of this thread with:

2020.1.4.55
- Compiled with Octane 2020.1.4

Thanks

Paul