Octane crashed after 12 hours of rendering

[steveps3]

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

Octane was rendering on my 460 card with 2GB of ram. I have an 8800GTX card to drive the screen. This card has 320MB of ram. I'd only just started modelling in Blender when it crashed and to the best of my knowledge there wasn't anything else running. Yesterday I was able to model in Blender whilst the render was running in 2.47 with no problem. I did have one problem this morning when I saved the render I got the same error that lots of people have reported in that I then tried to zoom into the render and it went into a not responding loop. So I have had to restart the render all over again.

I'm not too sure whether the problem is recreatable. I can certainly try when I've finished my current renders.

As I mentioned at the top of the thread, I've just got a new monitor so I suspect that maybe I am just pushing the 320MB of ram that the 8800 card has. The new monitor is a 2560x1440 resolution so it requires a lot of video ram. At the time of the crash, Octane was open on my old monitor but I don't think this would have any significance.

I think it may just be a one off glitch but I was just worried in case anyone else got the same thing happening. I can send you the .OCS file if you want to try it out at your end but the render had been going to 12 hours so it's not going to be something you can easily test.

[steveps3]

n his sig it says an ECS 8800GT.

It's actually an 8800GTX, my sig is slightly wrong. It has 320MB of ram. When I got the new monitor I had heard a few people commenting that maybe the 8800 might not be up to the task.

I don't have any screen savers turned on and I've been running Octane for nearly a year now with no similar problems.

So the crash was either caused by the 2.48 version of Octane, the new monitor causing an over heat, or just some random event. I could certainly monitor the heat of the GPU but it is odd that it was Octane that crashed which couldn't have been using much of the 8800s power because it was rendering on the 460 card.

As I say, the main reason for the thread was simply incase anyone else had the same problem and then maybe a pattern might emerge. Hopefully it was a one off fluke.

[abstrax]

n his sig it says an ECS 8800GT.

It's actually an 8800GTX, my sig is slightly wrong. It has 320MB of ram. When I got the new monitor I had heard a few people commenting that maybe the 8800 might not be up to the task.

I don't have any screen savers turned on and I've been running Octane for nearly a year now with no similar problems.

So the crash was either caused by the 2.48 version of Octane, the new monitor causing an over heat, or just some random event. I could certainly monitor the heat of the GPU but it is odd that it was Octane that crashed which couldn't have been using much of the 8800s power because it was rendering on the 460 card.

As I say, the main reason for the thread was simply incase anyone else had the same problem and then maybe a pattern might emerge. Hopefully it was a one off fluke.

The reason why Octane got killed by the OpenGL driver is very likely that displaying the result was exceeding the amount of available memory on the 8800GTX, but I'm not sure here and I also don't know why it doesn't happen with the beta 2.47. I guess, we will investigate this issue soon, but first we have to dig out some old cards with little memory...

Cheers,
Marcus

[steveps3]

The render has been rendering for 24 hours and I just opened photoshop whilst it was still running and it didn't complain. So I think it must have been a gremlin in the works. Now that the render has finished I can try to "break" 2.48.

The results of the render are in the gallery.

[abstrax]

The render has been rendering for 24 hours and I just opened photoshop whilst it was still running and it didn't complain. So I think it must have been a gremlin in the works. Now that the render has finished I can try to "break" 2.48.

The results of the render are in the gallery.

Was it beta 2.47 or beta 2.48 that ran 24 hours?

Marcus

[face]

I know that the newer versions of Photoshop uses GPU acceleration.
Maybe thats the problem...

face

[Jaberwocky]

Yes but i believe that Photoshop CS4 & 5 uses Open GL for GPU acceleration.

This should not happen whilst 2.48/Beta is running because all the Open GL coding should have been junked.

I think these versions have now switched to running purely Cuda 4.0 code now. so there shouldn't be a clash.

Unless of course that there are still some function on the latest beta releases that are still reliant on portions of GL code.

[abstrax]

Yes but i believe that Photoshop CS4 & 5 uses Open GL for GPU acceleration.

This should not happen whilst 2.48/Beta is running because all the Open GL coding should have been junked.

I think these versions have now switched to running purely Cuda 4.0 code now. so there shouldn't be a clash.

Unless of course that there are still some function on the latest beta releases that are still reliant on portions of GL code.

No, that is not correct. We still use OpenGL for displaying the render result, because it's platform independent and fast. CUDA itself can't display anything.

What we have changed is the connection between CUDA and OpenGL: In the past the CUDA driver had to know how to load the render result into OpenGL, which was only guaranteed to work with NVIDIA graphics cards. With the new system, this requirement is gone.

Cheers,
Marcus

[Jaberwocky]

Thanks for the clarification Marcus

So Running Photoshop CS4/5 will need to have Open GL acceleration disabled if you are going to run Octane underneath it . Other wise they may well clash as they will be both try to use open GL at the same time to display the results.The Graphic card in question may well then get slightly confused.

[abstrax]

Thanks for the clarification Marcus

So Running Photoshop CS4/5 will need to have Open GL acceleration disabled if you are going to run Octane underneath it . Other wise they may well clash as they will be both try to use open GL at the same time to display the results.The Graphic card in question may well then get slightly confused.

It should be similar to what was before. As far as I know there should be no problem having several applications accessing OpenGL, as long as you don't run out of graphics memory.

Cheers,
Marcus