I HATE when I wake up and my animation render has stopped because Octane crashed and Windows popped up the Windows Error Reporting dialog, hanging the C4D-Octane exporter. I just found out that you can turn it off!!
http://stackoverflow.com/questions/3963 ... dows-vista
or
http://stackoverflow.com/questions/3561 ... nit-test-i
2 different methods. I tried the first, we'll see how it goes.
How to disable Windows crash dialog!! No more hung renders!?
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Well, the second method seems to be necessary, it appears to have stopped crashing. With the new activation retry system, the only problem remaining is when Octane hangs before the render starts...if only it would detect when that happened.
Mac OS X 10.8.0 | ASUS GTX 580 1.5GB | MSI GTX 470 | ATI Radeon 6870 | Core i7 2.9Ghz | 16GB
- cheeweezz777
- Posts: 23
- Joined: Sun Feb 06, 2011 6:50 pm
This must be what I am experiencing- I haven't caught it "in the act", but I was getting the overnight "Octane has stopped working"- so I applied the reg edit on the mentioned Windows Report entry at all instances (it appeared twice, I believe?)
NOW- It seems every 300 frames or so, I check and Octane is sitting idle with a "Can't render frame "xyz"". Of course I can just pick up at the next frame, but it seems to be a regular instance (it happened today twice, both somewhere around the 300ish mark)
Anyone have any other ideas? Or is it just something I may have to deal with until the "kinks" are worked out?
NOW- It seems every 300 frames or so, I check and Octane is sitting idle with a "Can't render frame "xyz"". Of course I can just pick up at the next frame, but it seems to be a regular instance (it happened today twice, both somewhere around the 300ish mark)
Anyone have any other ideas? Or is it just something I may have to deal with until the "kinks" are worked out?
Win64 Ult/i7920 6GB DDR1600/2 X GTX480 ,V.260.99 CUDA 3.0,
Which exporter are you using? The mentioned error message is not coming from Octane itself.cheeweezz777 wrote:This must be what I am experiencing- I haven't caught it "in the act", but I was getting the overnight "Octane has stopped working"- so I applied the reg edit on the mentioned Windows Report entry at all instances (it appeared twice, I believe?)
NOW- It seems every 300 frames or so, I check and Octane is sitting idle with a "Can't render frame "xyz"". Of course I can just pick up at the next frame, but it seems to be a regular instance (it happened today twice, both somewhere around the 300ish mark)
Anyone have any other ideas? Or is it just something I may have to deal with until the "kinks" are worked out?
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
- cheeweezz777
- Posts: 23
- Joined: Sun Feb 06, 2011 6:50 pm
using the Cinema 4D export plugin. Exporting everything to Octane "sans textures", and doing all texture/light work in Octane. I am setting up another animation (same scene, modified some basic parameters) to see if it repeats itself. I haven't been able to successfully render the 2500 frame animation in one pass. It always gives me a "can't render xyz frame", or "failed to load object". If it happens again, I'll screen cap the exact instance.
Win64 Ult/i7920 6GB DDR1600/2 X GTX480 ,V.260.99 CUDA 3.0,
- cheeweezz777
- Posts: 23
- Joined: Sun Feb 06, 2011 6:50 pm
It happened again last night. I don't how much this even helps, as it's a pretty generic error- but it's definitely consistent. Always happens after a couple hundred frames. (this paticular render actually starts at frame 510...) If I click "close". I can just pick up the render at the frame it says it "couldn't render", and it renders without a hitch. Something is amiss though- any ideas? I am going to set up an entirely new scene, just to see if there is something within the C4D scene itself that is causing the hiccup. Using the latest 2.43, with the CUDA 3.0 drivers. (since I am running 2 GTX 480s)
Win64 Ult/i7920 6GB DDR1600/2 X GTX480 ,V.260.99 CUDA 3.0,
I think this is mainly an exporter problem. The next version will hopefully fix this problem. I think, I need to add some kind of delay between the time when Octane closes and when the exporter looks for the rendered image. (If the image isn't there, the exporter relaunches Octane to render the image for up to 3 times).cheeweezz777 wrote:It happened again last night. I don't how much this even helps, as it's a pretty generic error- but it's definitely consistent. Always happens after a couple hundred frames. (this paticular render actually starts at frame 510...) If I click "close". I can just pick up the render at the frame it says it "couldn't render", and it renders without a hitch. Something is amiss though- any ideas? I am going to set up an entirely new scene, just to see if there is something within the C4D scene itself that is causing the hiccup. Using the latest 2.43, with the CUDA 3.0 drivers. (since I am running 2 GTX 480s)
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra