Page 3 of 3

Re: Bug - Network rendering - lost samples when slaves quit

Posted: Tue Mar 31, 2015 8:48 pm
by abstrax
Julien wrote:Hi Marcus,
I've got the same problem:["the device driver gets "killed" by windows"] and the render fails again and again and stops eventually.
My scene is quite heavy but my hardware should do the job easily. The problem still occurs after removing octane proxys and displacement.
So I've changed the "TdrDelay" to 30 and even 60 but nothing changed.

Honestly, this is a very important problem.
I'm thinking of reversing to another rendering program for this scene. It depresses me to do that but I don't see any other way. Do you?

PS: error log attached

1 GTX TITAN X and 2 GTX TITAN Black
Octane Version 2.21.1
GeForce Driver Version 347.88

Sincerely,
Julien
Is this happening on the master or on the slave or on both? To which value "TdrLevel" set and to which value "TdrDelay"?

EDIT: Could you please send us the scene so that we can have a look? Does it happen on the first frame or somewhere in the middle of the animation?

Re: Bug - Network rendering - lost samples when slaves quit

Posted: Wed Apr 01, 2015 12:25 pm
by Julien
Hi Marcus,
Actually, I'm not doing network rendering, only local, all devices are on one PC.
Also, not rendering frames, just stills but quite High resolution (I need a 5000 pixel render in width).

I tried:
"TdrLevel" value set to 3 and "TdrDelay" value set to 30

"TdrLevel" value set to 3 and "TdrDelay" value set to 60

For proprietary reasons, I'm sending you the link to my scene on a private post.

I've taken away the displacement on the grass but left the multiscatter and proxys, you can just hide them to start with.

Many thanks,
Julien