System log

[jang2235]

The frequent stops at 99% during these days if rendering. What the hell can not find the cause. 780ti 4way system ....

Sometimes it comes on, but also that you are working in four gpu often happens if you look at the gpu information that is not doing the 4 gaejung one operation.

The initial version 2.1 is now occur more frequently than the version. Anything but this may be a problem with the system experiences of others who are?

Octan log mesage...

01:52:35 (6755.41) * OCTANE API MSG: CUDA error 700 on device 0: Error code unknown.
01:52:35 (6755.41) * OCTANE API MSG: -> kernel execution failed (dl)
01:52:35 (6755.41) * OCTANE API MSG: device 0: direct lighting failed

[juanjgon]

Yes, I didn't know that you are getting this kind of error messages. This sounds to me like a hardware problem.

I think that you should try to work only with three GPUs, disabling one of them, to try to see if one of the boards is damaged, or if you have a problem with the PSU. If one of the boards has problems and Octane crash on it, the render never ends because some samples are lost.

-Juanjo

[atnreg]

This is partially off-topic but anyway

I have those 99% render problems too with two cards (3 GPU total see my sig) and even if the driver does not crash the renders sometimes stop at 99%. I have tried disabling the GPUs but that does not seem to have any effect. As I told in another thread I usually set the max samples very high and then check the image and Abort/Continue or save the image in the middle at proper moment. But for animation or other batch type rendering that of course is not possible so I hope this can be fixed although it can be difficult if you Juanjo cannot get it to happen on your system.

Related to this, could it be possible to add button to Octane menu or IPR that would 're-connect' the driver to LW after it has crashed? Now if the driver crashes in the middle of render, that render is usually possible to be saved but after that using IPR or F9 (depending on which it crashed) does not work and LW crashes if I try those after crash. But if there was some button to 'wake up' LW to see that the driver is back on, it might save the situation.

That may be impossible as the driver is global in the system and so it may not be possible to tell one application to connect to it again but as the system does not crash otherwise, it might be possible

Antti

[juanjgon]

I have those 99% render problems too with two cards (3 GPU total see my sig) and even if the driver does not crash the renders sometimes stop at 99%. I have tried disabling the GPUs but that does not seem to have any effect. As I told in another thread I usually set the max samples very high and then check the image and Abort/Continue or save the image in the middle at proper moment. But for animation or other batch type rendering that of course is not possible so I hope this can be fixed although it can be difficult if you Juanjo cannot get it to happen on your system.

Can you please enable the log file to see if you also get this error messages from the Octane API when the render stops at 99%?

-Juanjo

[atnreg]

I have those 99% render problems too with two cards (3 GPU total see my sig) and even if the driver does not crash the renders sometimes stop at 99%. I have tried disabling the GPUs but that does not seem to have any effect. As I told in another thread I usually set the max samples very high and then check the image and Abort/Continue or save the image in the middle at proper moment. But for animation or other batch type rendering that of course is not possible so I hope this can be fixed although it can be difficult if you Juanjo cannot get it to happen on your system.

Can you please enable the log file to see if you also get this error messages from the Octane API when the render stops at 99%?
-Juanjo

Yes, sure, when that happens next time. I usually stop the F9 render anyway before the max samples limit is reached (i.e. when I am happy with the cleaniness) so it may take a while until next complete render but I will report then

And I enabled the log now so whenever that happens, it will be on the log, I donät think it will slow down too much.

Antti