Hi
After a few minutes (maybout about 100/16000 samples) of rendering Octane always crashes.
The scene has about 200000 Verticies, resolution of about 1750x1150px, I'm using pathtracing, GPU temparature goes up to about 92 degree....
Does anybody have an idea where to search the fault ?
Kind regards
Alain
Crash after a few minutes of rendering
Did you run the installer or did you unpack the ZIP files to install Octane? If you didn't run the installer, please do it now. The installer disables the graphics timeout. If you ran the installer, then my first guess would be overheating. If for example opening the case doesn't help, it might also be a driver problem. Which driver are you using and which CUDA build of Octane beta2.44?Alain wrote:Hi
After a few minutes (maybout about 100/16000 samples) of rendering Octane always crashes.
The scene has about 200000 Verticies, resolution of about 1750x1150px, I'm using pathtracing, GPU temparature goes up to about 92 degree....
Does anybody have an idea where to search the fault ?
Kind regards
Alain
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Yes, GeoPappas is right: I forgot to mention that you have to reboot Windows to make this registry change become effective.Alain wrote:I installed Octane 2.44 Cuda 3.2 with the installer.
Using the newest graphiccard driver (266.58).
Still doesn't work :-/
Kind regards
Alain
If you have rebooted your computer, but the problem is still there, please do one more test, to make sure that it's not a scene specific problem: Please download the demo suite from http://refractivesoftware.com/downloads.html and try the benchmark scene or the chess set with path tracing. Do they work? If not, your card is very likely overheating.
If they do, but your scene doesn't, I need a test scene to reproduce and fix the problem.
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
I tried your scene and when all textures are loaded correctly, it quite takes some time to render. -> I still think that it's a timeout issue. I just saw that you are using Windows XP SP3. The TdrLevel fix doesn't work there. You can specify the timeout only since Windows Vista SP1.Alain wrote:I just succesfully tested the benchmarkscene but my scene still crashes.
I just sended you the downloadlink of my scene.
Kind regards
Alain
If you render your scene at half the resolution (875 x 575), does it work then? If yes it's definitely the GPU timeout.
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
It is a timeout enforced by Windows: http://msdn.microsoft.com/en-us/windows ... 87368.aspxAlain wrote:Thanks, I will test that.
But what is this "GPU timeout" usefull for ?
Is it Windows timeout or a driver timeout ?
Kind regards
Alain
It basically resets the graphics driver if there has been no feedback for some time. The default time limit depends on the Windows version you are using. And since Windows Vista SP1 you can tweak it via some registry keys, which is done by the installer. That's why I asked you to run the installer. But I missed that you are using Windows XP...
Regarding your scene: I can render it on a GTX 470 without problems, i.e. using pahttracing and all textures, defined in the Blender file.
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra