No responding

[steveps3]

Does anyones else encounter this problem?

I can leave a render overnight in order to get up to sufficient number of samples. In the morning, I pause the render in order to have a look at the final result. Here is where the lottery starts. I would say that 25% of the time, when I zoom into the image, Octane goes into a "not responding" state. It simply stays in this state until I shut it down. So my all night render has been wasted

If anyone has a solution, even better.

[erik]

Sorry to sound simplistic but the obvious solution for now until the next build is to not zoom until you have the render sitting in Photoshop or something happily. I haven't experienced that particular problem by the way but then I probably haven't done exactly what you do (could also have to do with hardware/driver combination etc).

[steveps3]

Well, that is the obvious answer but then I don't know how much of the new funky hot pixel removal tool to use. I suppose I could start rendering at 100% but then I would need to know where the highest areas of hot pixels would be.

I guess what I will have to do is save the image as is and then zoom in. At least if it crashes then everything won't be lost. I will just end up with an image with hot pixels.

[hmk]

In the "Mesh Preview Kernel" change rayepsilon to 0.0020 or more.

[radiance]

it could also be a heat issue.
once octane runs and it stays stable it should stay stable for overnight renders.
have you tried slightly underclocking your GPU ?

Radiance