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

[mikmod]

I've had a few Cuda 700 errors in the last few days as well after upgrading to 2020.1.0.54.

At the moment however, I have a scene I was working on yesterday, that now crashes DazStudio when I open the OctaneRender viewport after loading the scene.

It seems to always crash with the bellow reason.

Code: Select all

Exception Reason:
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\octane.dll" at 0033:00000000869CAF00, Octane::isGreyscalePass()+5682624 byte(s)

The only thing different about this scene is that I used a defuse emission material on some instances of a sphere for candle flames. However deleting the instances, the original sphere and material doesn't stop the crash, so I don't know if that's related.
A workaround I've found is to open the viewport before loading the scene, I can then open the viewport again after the scene has loaded without it crashing DS.

I can confirm, Daz, especially beta, doesn't like Octane plugin's presence at all. Beta Daz since 4.12.0.96 crashes quite frequently, stable 4.12 is more predictable, maybe because it's not riddled with debugging stuff. Thanks for pinpointing the possible cause!

[face_off]

I've had a few Cuda 700 errors in the last few days as well after upgrading to 2020.1.0.54.

At the moment however, I have a scene I was working on yesterday, that now crashes DazStudio when I open the OctaneRender viewport after loading the scene.

It seems to always crash with the bellow reason.

Code: Select all

Exception Reason:
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\octane.dll" at 0033:00000000869CAF00, Octane::isGreyscalePass()+5682624 byte(s)

The only thing different about this scene is that I used a defuse emission material on some instances of a sphere for candle flames. However deleting the instances, the original sphere and material doesn't stop the crash, so I don't know if that's related.
A workaround I've found is to open the viewport before loading the scene, I can then open the viewport again after the scene has loaded without it crashing DS.

Are you using the DAZStudio stable or beta version please?

Thanks

Paul

[face_off]

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

2020.1.0.55
- Compiled with Octane 2020.1

Paul

[SiliconAya]

I've had a few Cuda 700 errors in the last few days as well after upgrading to 2020.1.0.54.

At the moment however, I have a scene I was working on yesterday, that now crashes DazStudio when I open the OctaneRender viewport after loading the scene.

It seems to always crash with the bellow reason.

Code: Select all

Exception Reason:
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\octane.dll" at 0033:00000000869CAF00, Octane::isGreyscalePass()+5682624 byte(s)

The only thing different about this scene is that I used a defuse emission material on some instances of a sphere for candle flames. However deleting the instances, the original sphere and material doesn't stop the crash, so I don't know if that's related.
A workaround I've found is to open the viewport before loading the scene, I can then open the viewport again after the scene has loaded without it crashing DS.

Are you using the DAZStudio stable or beta version please?

Thanks

Paul

I'm using Daz Studio 4.12.0.86, which I believe is stable.

[mikmod]

At this moment I'll share something:
I'd like to thank you, Otoy Team, for being able to use this plugin in Daz Studio, not only because it's fast and quite robust (after some learning curve), but for me is also the only way now to use hardware rendering on my RTX 2080 in Daz Studio. Latest Iray 2020 iterations crash immediately upon starting preview/render on hardware, because I'm still using Windows 7 with Skylake-X CPU, which mean trouble with AVX-512. Iray 2020 is probably compiled to forcefully use this instruction set once SKX CPU is spotted, no matter the OS, so it ends up with illegal instruction exception crash in nvoptix.dll library.
Thanks for the possibility to be able to choose!

[abayliss]

I've had a few Cuda 700 errors in the last few days as well after upgrading to 2020.1.0.54.

At the moment however, I have a scene I was working on yesterday, that now crashes DazStudio when I open the OctaneRender viewport after loading the scene.

It seems to always crash with the bellow reason.

Code: Select all

Exception Reason:
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\octane.dll" at 0033:00000000869CAF00, Octane::isGreyscalePass()+5682624 byte(s)

The only thing different about this scene is that I used a defuse emission material on some instances of a sphere for candle flames. However deleting the instances, the original sphere and material doesn't stop the crash, so I don't know if that's related.
A workaround I've found is to open the viewport before loading the scene, I can then open the viewport again after the scene has loaded without it crashing DS.

Are you using the DAZStudio stable or beta version please?

Thanks

Paul

I'm using Daz Studio 4.12.0.86, which I believe is stable.

I am having the exact same issue since I installed - OctaneRender for DAZ Studio 2019.1.5.51

"DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\octane.dll" at 0033:00000000B90A47C0, Octane::isGreyscalePass()+5556736 byte(s)"

The work around I have found, is to create a new Default Render Setting, and use that once before switching back to the previous render setting.

However, after using this work around, and avoiding the crash, I have also started seeing CUDA 700 errors randomly occurring, requiring me to restart DAZ.

[mikmod]

Just now, after going back and forth with preview and Final Rendering, and rebuilding scene, I've got an 40000015 exception in octane.dll (2020.1.0.55) in Daz beta 4.12.1.115. I'll include the WER file (Polish locale, 1045), since the dump file is WAY too big to include, 285MB 7z-compressed, 824.5MB uncompressed. My net's really bad in terms of upload, sorry about that.

[face_off]

Just now, after going back and forth with preview and Final Rendering, and rebuilding scene, I've got an 40000015 exception in octane.dll (2020.1.0.55) in Daz beta 4.12.1.115.

I tried doing this, but could not reproduce the crash. Which DAZStudio Viewport DrawStyle are you viewing?

Paul

[face_off]

However, after using this work around, and avoiding the crash, I have also started seeing CUDA 700 errors randomly occurring, requiring me to restart DAZ.

Can you post the specific Octane Log when this happens please?

Paul

[mikmod]

Just now, after going back and forth with preview and Final Rendering, and rebuilding scene, I've got an 40000015 exception in octane.dll (2020.1.0.55) in Daz beta 4.12.1.115.

I tried doing this, but could not reproduce the crash. Which DAZStudio Viewport DrawStyle are you viewing?

Paul

At the time I was using Texture Shaded view with cameras switched in between with Perspective.
It was quite a bit of a scene, at least 800MB of textures and 1.4GB of mesh (hair strands mostly, but also high body SUbD - 3)
Ah, right, Daz beta stays in memory after graceful exiting (crash removes it from the mem, as expected), I have to disable Octane plugin to see DS disappear from the memory after such exiting or kill Daz after exiting gracefully. It eats about 4.,7GB of RAM at that point.