Octane crashed after 12 hours of rendering

[steveps3]

I've been rendering for 12 hours now when all of a sudden I got an error from the OpenGL driver. 12 hours completely wasted

Anyone got an idea what might have caused it? When it crashed I was just doing a bit of modelling in Blender whilst the render ran in the background.

[steveps3]

I've just got a new monitor so maybe driving 2 monitors is pushing my 8800 just too much. Odd that Octane crashed though because that was running on my 460 card.

[abstrax]

I've been rendering for 12 hours now when all of a sudden I got an error from the OpenGL driver. 12 hours completely wasted

Anyone got an idea what might have caused it? When it crashed I was just doing a bit of modelling in Blender whilst the render ran in the background.

Which version did you use?

Marcus

[steveps3]

Of octane? The new 2.48b version

[colorlabs]

Really I would love it if Octane would save backup images every 5 minutes. Or, at regular sample intervals - 64, 128, 256, 512, 1024, 2048, etc. Then when preparing to render an animation, I could let a still frame render for a minute or two, then look through the generated images. I would decide where I want to draw the line between quality and render time, for my animation.

[steveps3]

Well it has been rendering away for 3 hours how. fingers crossed. I've also gone back to 2.47 in a hope that it will be more stable.

Hopefully when I wake up in the morning the render will be somewhere near complete. I guess that is what I get for trying to render nearly 4M tris at 4000x3500 resolution. I've already lowered pathtracing down to a maxdepth of 4 in order to speed things up.

I was wondering whether things would render faster if I surround my model with portals just outside of the frame. I am assuming it would be a bit faster.

[abstrax]

Of octane? The new 2.48b version

Have you been doing other things in parallel or has your computer just been sitting there and rendering?

Cheers,
Marcus

[steveps3]

As I mentioned in my post, I was modelling in blender when it crashed. I have rerendered overnight using 2.47 and all seems fine. All except there is still a lot of grain so I will have to leave it rendering some some. Maybe a couple of days.

[abstrax]

As I mentioned in my post, I was modelling in blender when it crashed. I have rerendered overnight using 2.47 and all seems fine. All except there is still a lot of grain so I will have to leave it rendering some some. Maybe a couple of days.

What is your display card, how much memory does it have and did you work on a big mesh in Blender? Which graphics cards did you use for rendering in Octane?

Do you think there is a way to reproduce this problem?

When you re-rendered the scene in beta 2.47, did you do some modeling in parallel?

Thanks,
Marcus

[pixelrush]

in his sig it says an ECS 8800GT.
has 256mb vram or 512mb with a BIOS update apparently.
see here
http://www.overclockersclub.com/reviews ... 0gt/14.htm

further up it says he is using 2 monitors and a GTX460 for Octane.

at a guess I would say the 8800 is not ideal for 2 monitors for win7 + modelling if it is 256mb.
might want to consider flashing the BIOS to 512mb or upgrading to a card with say 1gb or even better a Quadro 600 (not expensive - good CAD,DCC performance).
alternatively perhaps there is a minor heat/stability issue after a prolonged period?
another thing that crossed my mind is if there is a screensaver set after an idle time that messes up the openGL?