Page 2 of 2

Re: Automatically close failed slave?

Posted: Mon Nov 27, 2017 12:10 pm
by PHM
abstrax wrote:James, I just noticed that you are using version 3.06. Could you (when you've got time) update to version 3.07 to see if the problem is gone. I don't think that the update will solve your problem, but it's worth a try. Thanks.
We have just finished a major project, so we are due to do all our updates when we've had a bit of a clean-up. I'll let you know if it does make a difference.

Re: Automatically close failed slave?

Posted: Wed Nov 29, 2017 4:17 pm
by PHM
Just to confirm, it still happens in 3.07.
2017-11-29 16_43_39-Picture Viewer.png
During this test, none of the slaves even reported an error of any kind. And you can see, Octane estimates it is 6 seconds from finishing the frame, but the C4D clock is 8 minutes over that. As soon as I unticked Network Render the frame finished.

It's not a memory problem either, it's using under 3Gb for the scene and the smallest card has 6Gb.

Re: Automatically close failed slave?

Posted: Fri Dec 01, 2017 11:54 am
by thanulee
I have again lost a render overnight. I assume that the slave pc did a windows update therfore slave crashed or closed and render just stopped.
Im attaching the log, i dont open new thread. I dont know how to narrow this besides the log or if it provides any information about why the render stopped. Thanks

Re: Automatically close failed slave?

Posted: Sat Dec 02, 2017 8:34 am
by aoktar
thanulee wrote:I have again lost a render overnight. I assume that the slave pc did a windows update therfore slave crashed or closed and render just stopped.
Im attaching the log, i dont open new thread. I dont know how to narrow this besides the log or if it provides any information about why the render stopped. Thanks
Looks like it's a user break.

Re: Automatically close failed slave?

Posted: Sat Dec 02, 2017 10:28 am
by thanulee
What u mean users break? Like someone stopped it manually?