was really excited about this overnight C4D animation render Tweet

[colorlabs]

but Octane crashed six frames in, and the C4D exporter just sat there waiting for 8 hours. abstrax - PLEASE make it detect crashes and relaunch! or let me set a per-frame timeout!

I stayed up really late tweaking this scene so I could render it overnight! now I have to wait a few days to try again cuz of my schedule!

[electromusic.se]

Same here,

I was rendering a 90 frame piece and after an hour octane just stopped at frame 50. Very dissapointing

I'm on OSX 10.6.6, C4D R12, Octane 2.43, The very latest nVidia stuff.

It sounded like the machine did a LOT of disk stuff at the time the rendering stopped working. No other clue...

/Björn

[abstrax]

but Octane crashed six frames in, and the C4D exporter just sat there waiting for 8 hours. abstrax - PLEASE make it detect crashes and relaunch! or let me set a per-frame timeout!

I stayed up really late tweaking this scene so I could render it overnight! now I have to wait a few days to try again cuz of my schedule!

Hmm, the exporter for CINEMA 4D tries 3x (the next version will try 5x). At least it should. How did Octane crash? Was the process still running? What exactly happened?

Cheers,
Marcus

[electromusic.se]

Seems like other exporters suffers from the same problems. I've seen similar posts in the Blender and Max forums.

[colorlabs]

Well, on windows 7, when a program crashes, it doesn't close until the user clicks Close on the Windows crash dialog. However, i found that there is an option in the windows registry to bypass this dialog, which appears to have solved 80% of the problem. The other 20% is when octane just freezes while loading the scene. This happens on my machine quite a bit, though not nearly as often as hard crashes which are once every 20-100 frames. Seems the only solution here is for the exporter to have a timeout option. Or, it would be great if there was some "ping" that went on during rendering, so the exporter could tell instantly if octane was dead.

[abstrax]

Well, on windows 7, when a program crashes, it doesn't close until the user clicks Close on the Windows crash dialog. However, i found that there is an option in the windows registry to bypass this dialog, which appears to have solved 80% of the problem. The other 20% is when octane just freezes while loading the scene. This happens on my machine quite a bit, though not nearly as often as hard crashes which are once every 20-100 frames. Seems the only solution here is for the exporter to have a timeout option. Or, it would be great if there was some "ping" that went on during rendering, so the exporter could tell instantly if octane was dead.

I can do that. I have been thinking about this alreday: I could record the average render time for the last 3 frames and then apply a factor of maybe 8 plus 30 seconds. And if that time has passed, kill the process and try again. Maybe I make the factor settable by the user.

Cheers,
Marcus

[colorlabs]

Yes! Sounds great! Yay!

[cheeweezz777]

I'm excited about this as well- I had this exact same thing happen...I set up a 2000 frame animation, went to bed, and it turns out it was sitting with an "Octane has stopped working", waiting for me to click, wait... it then started back up, but of course it kind of defeated the purpose of much faster it is if it stops every 3-400 frames. (which it continued to do the next day until I finished)

Still very impressed with the product- makes me VERY excited once I can get it rolling for an entire animation (right now an HD animation natively in C4D is taking about 30+ hours)

[TheOracle]

This fix is very much needed indeed.
my animation crashed just about every 14 frames (300 in total)
No way for me to render overnight, kills my productivity.

[abstrax]

This fix is very much needed indeed.
my animation crashed just about every 14 frames (300 in total)
No way for me to render overnight, kills my productivity.

You can disable the error reporting in Windows:

http://msdn.microsoft.com/en-us/library ... 85%29.aspx

"DontShowUI" is the one you have to set.

After that Octane just dies, when it crashes and the export plugin tries again.

On the other hand, Octane shouldn't crash at all. Does it happen only with a specific scene or with any scene? Could you send us an example scene that causes Octane to crash?

Cheers,
Marcus