Page 1 of 1
Auto-Kill Octane on Failure?
Posted: Fri Jun 10, 2011 12:20 am
by cperkins
Okay, I'm having a problem with Octane intermittently failing while running an animation sequence. When it fails, I get the 'octane.exe has stopped working' dialog that just stays there until I click close, whereupon the exporter detects the failure and tries again. Is there any way to automatically close Octane when this happens? I've already disabled some things in the Windows registry and in the Control Panel, and that got rid of the Windows 'check for solution' dialog but I am still left with the one I am describing and it's like if I want the animation to finish I have to babysit the thing. Has anyone found a workaround to this situation?
Re: Auto-Kill Octane on Failure?
Posted: Fri Jun 10, 2011 12:47 am
by bitoffish
I've encountered a few hangs like this in Linux, especially when the app closes after rendering a frame. I am working on an upcoming animation production, and I can't afford to have nodes in the render farm hang idly while Octane is hung. So, I am working on a Linux solution that would monitor the process, GPU utilization, GPU Temp, whether or not the rendered output file exists and is a vilid image file, and possibly the average render time for the previous few frames. If these values look wonky (e.g. The process has been running 30 minutes longer than the previous frame did, and the GPU is idle, and there is an outputted image file, Octane is probably hung), the script sends sends out an alert, or if too much time has passed, it kills the process and has that frame flagged for review. I am reading these values through
nvidia-smi which, I believe, only works for Tesla cards.
I'm not sure how easily something like this could be cooked up for Windows, but it's fairly straightforward in Linux if you're comfortable with bash.
Re: Auto-Kill Octane on Failure?
Posted: Fri Jun 10, 2011 3:48 am
by cperkins
Sounds like a fun project
I think I found a solution in changing another Registry setting.. believe it was HKEY CURRENT USER>SOFTWARE>WINDOWS>WINDOWS ERROR REPORTING>SET DISABLE UI TO
1. That seems to have done the trick as I haven't gotten hung for the past 100 frames or so.
BTW - to ABSTRAX,
You C4D plugin is by far the best I have used thus far for Octane, keep up the good work!