OTOY Forums

I'm on:
- Windows 10 Pro 1903
- 64 GB RAM
- Nvidia Studio Driver 431.86
- Octane 2018.1.3-R5
- C4D R21.026


I'm having repeated crashing from the same action. I would let a render churn for a while, pause the IPR and close it and C4D will crash immediately. I've done a clean install of my Nvidia Studio driver but the same issue still happens. I don't know what else I could be going wrong. I've seen posts where the aoktar has said the problem is hardware at this point and not Octane, but that's hard to believe. None of my GPU's are overclocked and constant crashing is only something I experience with Octane and not Redshift. This is one of many random crashes I've had, but this one is just too frustrating and consistent. I would like some clear answer or direction on what I need to fix to make Octane more stable.

Thanks,

Seun

I see a plugin crash in your bugreport, but my answers are not about same issues. Mostly about driver related crashes.
Where's your other random crashes?

Thanks for the response. I've had crashes that come from trying to disconnect node wires in the node editor. Other crashes from just general use of the plugin. They're random and not as frequent but this one happened enough times for me to submit a bug report. In the future, I'll try and be more on top of following up with any crashes. To the best of my knowledge, I don't think any of my crashes have given me CUDA errors. I had one a few days ago and I submitted it to Maxon and they said the crash came from the plugin.

Seun116_1 wrote:Thanks for the response. I've had crashes that come from trying to disconnect node wires in the node editor. Other crashes from just general use of the plugin. They're random and not as frequent but this one happened enough times for me to submit a bug report. In the future, I'll try and be more on top of following up with any crashes. To the best of my knowledge, I don't think any of my crashes have given me CUDA errors. I had one a few days ago and I submitted it to Maxon and they said the crash came from the plugin.

Could you please try with 2019 demo builds?
It would mean that fixed it doesn't happen.

aoktar wrote:

Seun116_1 wrote:Thanks for the response. I've had crashes that come from trying to disconnect node wires in the node editor. Other crashes from just general use of the plugin. They're random and not as frequent but this one happened enough times for me to submit a bug report. In the future, I'll try and be more on top of following up with any crashes. To the best of my knowledge, I don't think any of my crashes have given me CUDA errors. I had one a few days ago and I submitted it to Maxon and they said the crash came from the plugin.

Could you please try with 2019 demo builds?
It would mean that fixed it doesn't happen.

Did you want me to try with a demo build or latest 2019 stable? I tried with latest 2019 stable and I still got the same crash. I've attached the bug report below.

Ok if you have 2019 build. I use it hundreds of times everydays without any crashes. Could you please record some screenshots from crash moment with visible error message? Even I prefer a video capture. Also select all log output options and send me c4doctanelog.txt when crash happened. It will show where it crashes.

aoktar wrote:Ok if you have 2019 build. I use it hundreds of times everydays without any crashes. Could you please record some screenshots from crash moment with visible error message? Even I prefer a video capture. Also select all log output options and send me c4doctanelog.txt when crash happened. It will show where it crashes.

I had a chance last night to run through some tests on another computer (my home rig) with the same project, different project, and a scene with just a cube/octane material. It seems like the crash happens when I pause the Octane Live Viewer and close the window, then when I click on any octane related icon/object, a crash happens. No crash when just closing live viewer or if I just pause the live viewer and continue to work. I'd be interested to hear if it's something that can be recreated on your end. It's obviously an action I can avoid in the future, but just though I should share an update.

Ok, I can reproduce it by steps:
render, pause, close LV and select any octane material.

It's not happening on 4.05 builds, so it seems like a problem on 2019.1.2 SDK