OctaneRender 2020 for DAZ Studio [TEST and STABLE][OBSOLETE]

[rajib]

Can we have the 2020.1 RC1 plugin ?

Standalone RC2 is out, so I will do a plugin build with RC2 once the API is available.

Paul

Okay Paul. Will wait. I don't see RC2 being mentioned but you do have insider info. And if RC2 came out so fast after RC1, I guess there is some major bug in RC1.

[wader]

Hi Paul,
I am using the 2020.1.0.50 Enterprise plugin for Daz3D and just tried rendering a scene that was created and rendered fine yesterday, but today cannot get beyond the "Building geometry" stage.

This scene was a test involving water and caustics and was based on another scene which still renders without real problems in the same level of Octane plugin (sometimes requiring the Pause -> Continue toggle to work the first time, though).

Here's the log when this newer scene is loaded and I try to open the Octane Viewport:

Code: Select all

22:08:12.926: +++++ Plugin running.
22:09:16.113: CUDA error 700 on device 0: an illegal memory access was encountered
22:09:16.113:   -> failed to wait for event
22:09:16.113: CUDA error 700 on device 1: an illegal memory access was encountered
22:09:16.113: device 0: direct light kernel failed
22:09:16.114:   -> failed to wait for event
22:09:16.115: device 1: direct light kernel failed
22:09:16.119: Render engine failure occured! (WARNING)
22:09:19.113: Render engine failure occured! (WARNING)

Here are my System settings:

Ideas welcome.

[face_off]

Ideas welcome.

Suggest rebooting and trying again.

Paul

[wader]

Ideas welcome.

Suggest rebooting and trying again.

Paul

Thanks, I have tried that a few times with no better effect.

It seems that ONLY this newer file is having this problem: the earlier versions of this same scene exhibit none of those System errors when opening the Viewport. But, as soon as I try with this newer scene, then the errors occur.

[face_off]

It seems that ONLY this newer file is having this problem: the earlier versions of this same scene exhibit none of those System errors when opening the Viewport. But, as soon as I try with this newer scene, then the errors occur.

I suggest exporting that scene to ORBX and seeing if the error occurs in Octane Standalone. If it does - report it to OTOY in the Octane Standalone 2020.1 release thread.

Thanks

Paul

[face_off]

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

2020.1.0.51
- Compiled with Octane 2020.1 RC1
- Removed the setting of the Windows TDR Deley setting when the plugin starts up
- Removed the OOC GPU Headroom slider, as this is now in the Device Settings panel

Thanks

Paul

[rajib]

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

2020.1.0.51
- Compiled with Octane 2020.1 RC1
- Removed the setting of the Windows TDR Deley setting when the plugin starts up
- Removed the OOC GPU Headroom slider, as this is now in the Device Settings panel

Thanks

Paul

Thanks Paul. Will take it for a spin. Main thing I want to see is if the OOC memory issue goes away like it did in my stand alone Octane test. That itself will be a huge relief.

[wader]

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

2020.1.0.51
- Compiled with Octane 2020.1 RC1
- Removed the setting of the Windows TDR Deley setting when the plugin starts up
- Removed the OOC GPU Headroom slider, as this is now in the Device Settings panel

Thanks

Paul

Thanks Paul - your new build happened to fix my prior reported problem.

Some experimentation revealed that only when I saved a scene file with

Environment -> Medium settings -> Scattering

enabled, later re-opening that scene file and rendering would lead to the error messages. Weirdly, I could be working on a scene and changing the Environment setting to those same values, but it would render without problems while that scene remained open in Daz. So, this only happened after opening a scene file whose settings were set to use Medium and Scattering.

My Octane standalone was able to render exported .ORBX files for those scenes giving the older Daz plugin problems - I guess the update you made has gotten around the issue.

Of potential note, I am now getting this seemingly benign message whenever I load the once-problem scene:

Code: Select all

We can't evaluate items of a different version (version 8000002)!

As I implied, there is no obvious impact related to this message on the rendering - not sure if it's significant in some other respect, though.

------------

Separate item to note:

- Removed the OOC GPU Headroom slider, as this is now in the Device Settings panel

The slider is still present and operable in the plugin System panel, now limited to 6336MB on my system (with 32GB of RAM). The Device Settings panel shows a GPU headroom slider which goes up to 1024 max - that seems rather limiting.

[rajib]

Having issues Paul. Every scene of mine crashes as soon as I hit Render. Even the ones which have no issue rendering under 2020.1.XB3, 2019.1. 5.49 and earlier.

Also why is the OOC Memory slider restricted to 6336MB ? I have 128GB of RAM and I should be able to set it to any size within my Total System Memory. You can see my earlier post regarding the test I did with the Stand Alone version and I had selected 50+ GB of RAM as OOC Memory in the Stand Alone. I switched back to 201.1.5.49 and there I can set the slider to any size up to my system memory size of 128GB. Please check this. Maybe my crashes are related to this.

[rajib]

Having issues Paul. Every scene of mine crashes as soon as I hit Render. Even the ones which have no issue rendering under 2020.1.XB3, 2019.1. 5.49 and earlier.

Also why is the OOC Memory slider restricted to 6336MB ? I have 128GB of RAM and I should be able to set it to any size within my Total System Memory. You can see my earlier post regarding the test I did with the Stand Alone version and I had selected 50+ GB of RAM as OOC Memory in the Stand Alone. I switched back to 201.1.5.49 and there I can set the slider to any size up to my system memory size of 128GB. Please check this. Maybe my crashes are related to this.

Hi Paul,

Here's a screen shot of the issue. I have 2 copies of Daz. One with 2019.1.5.49 and the other with 2020.1.RC1. I ran both together to show the issue with the OOC memory size slider selector. As you can see in 2019.1.5.49 I set it to around 15GB and I can still drag the slider a lot to the right to allocate even more. But under the 2020.1.0.51 (RC1) the slider is already max out at 6336MB.

2019.1.5.49 / 2020.1.9.51 (RC1) OOC memory setting difference.

I did reboot just to see if it was just an initial installation issue. But the issue persists after the reboot.

Hope you can fix this ASAP.

Regards,
Rajib