Okay, so I'm on a deadline and obviously things are going wrong. I've got a scene with a few cameras around a building; I've rendered - quite happily - three of them. The fourth camera, whose position and lens are the only thing that change in the entire scene (same resolution, materials, objects, render target, everything) renders up to 1% or so and then my entire screen goes blank for a second; when it comes back, I get a "the video driver has stopped working" and that's it. No way to render.
I've got the latest plug-in, removed all instances and unseen high-poly models, installed the latest video drivers from NVidia (it's a Titan black btw) and just to make doubly sure I tried the same scene on my other machine, which has a different Octane license and a different Titan Black (and a different OS too) and got the same result. So no, the Titan isn't broken thankfully, but I have absolutely NO idea what's going on. The logfile is rather long, but the interesting part I think is here (note that we're at 7 out of 3000 samples):
[BEGIN LOGFILE]
00:01:08 (0068.91) | ... Statistics: 7 of 3000 samples, 33 sec, 1.39 Ms/sec
(...)
00:01:09 (0069.85) | >>> Draw preview image finished. Releaseing mutex
00:01:09 (0069.93) | >>> Refresh preview window done
00:01:29 (0089.34) * OCTANE API MSG: CUDA error 999 on device 0: An unknown internal error occurred.
00:01:29 (0089.34) * OCTANE API MSG: -> kernel execution failed (pt)
00:01:29 (0089.34) * OCTANE API MSG: device 0: path tracing failed
00:01:29 (0089.34) |
00:01:29 (0089.34) | ++++++++++++++++++++++
00:01:29 (0089.34) | +++ RENDER FAILURE +++ processing the failure callback
00:01:29 (0089.34) | ++++++++++++++++++++++
[END LOGFILE]
Help?!
ADP.
