Octane / GPU dropping out problems

[MoGrafik]

Hi everyone.
I'm having problems with a scene I'm trying to render. The poly count is quite high, but nothing crazy.
The shot begins rendering. Then a few samples in (after 3 mintues or so) it will stop. Windows informs me that the graphics driver successfully reconnected, or something like that. So it seems like there's some error with the GPU.
I'm using c4d r14, octane plugin 2.12.2 (latest) and just updated GPU drivers, but that didn't work unfortunately. Does anyone have any ideas what might be causing this?
Would really appreciate any help
Thanks

[FooZe]

Have you ever installed the standalone?
If not, I would recommend you do. There is a registry setting (TdrDelay if i remember correctly) that sets how long the GPU can be "out of contact" before windows figures it's got a problem and tries to reset it. The standalone increases this timeout during installation. I think the default is 2sec and the standalone install increases it to 10sec

[MoGrafik]

Hey Fooze,
thanks very much for your suggestion. Just installed the latest standalone. It might have actually helped a little, as the render now progressed further (10 mins or so) before the problem occurred again.

I have a lot of materials in the scene - could that be affecting it in any way? Previous I have encountered the maximum texture limit, however I thought octane had worked away around this limitation in v2.0 - is this correct?

I'm going to keep experimenting, but would be great if anyone has any further insight to the problem.
Thanks for your help Fooze, certainly can't help to update the standalone!

[Yan]

I have the same problem. I get an error something like this: Open GL stopped working ...etc. error code 3 or display driver stopped working and has recovered. I have tried with TrDelay, but it's not working. For me these errors are random I think. I have used multiple scenes and I didn't find a pattern. In my case the error is quite rare.
I hope there is a solution to this.

[MoGrafik]

Hey Yan,
thanks very much for your input. Sorry your're having similar problems, but glad it's not just me!
I'm having trouble finding a pattern too.
I think in my scene it might have something to do with materials. Deleting all the materials in the scene seems to allow the renderer to finish rendering the image. However it's inconsistent, If I delete half of the materials it stills seems to crash.
Is the TrDelay parameter something that is implemented manually? Or should it be effective automatically when the latest standalone is installed?
Also, Yan - would version of c4d are you using? I'm on r14 here. I wonder if it's version specific?
Thanks

[aoktar]

do you have displacement? are you checking free vram? what are you seeing on octane log window?

[MoGrafik]

Hey Aoktar,
yes, I'm using displacement, with 4096 x 4096 sampling. If the render begins and crashes mid way through, this shouldn't be the problem should it? I thought if you didn't have enough vram the render simply wouldn't begin.

I'll try to open a crash log after it does it next time, so I can share it with you.

I've tried downsampling the displacement resolution, so I'll see if this fixes it. Thanks!

[aoktar]

no, i saw similar problems as yours. Begins for a few samples and crashes on displacement. Also let me know vram and console output. test it without displacement to see problems

[MoGrafik]

Hey Ahmet, I think it was the displacement problem after all - I reduced the displacement sampling from 4096 down to 1024 and I haven't had a crash since!
Thanks for pointing out the problem to me. Much appreciated! - This forum saves my life once again!