OTOY Forums

Selecting a material from the Live DB - FAB_Velvet-1a from Non-organic/Cloth

Another one...

Hmmmm... might have been nVidia Drivers version 337.88... just install this driver... Octane crashed... went back to an earlier version of the driver... octane didn't crash.

RGUS wrote:Hmmmm... might have been nVidia Drivers version 337.88... just install this driver... Octane crashed... went back to an earlier version of the driver... octane didn't crash.

Good to know. Thanks! I'll avoid this driver version.

I have to admit, that, since being on driver vers. 337.88, Octane/Poser plug-in crashes on my machine from time to time as well, during rendering.
With earlier versions that never happened. Octane/the plug-in always was rock solid on my system.
Somehow I have a feeling, that the crashing happens, when having displacement enabled somewhere. No evidence there, just a feeling.

Selecting a material from the Live DB - FAB_Velvet-1a from Non-organic/Cloth

Fixed in the next release.

Paul

Ok, i am also getting the 999 error now.

And it is in some way tied to rayepsilon. I'm 99% certain this is the first time ive tried to dial back the rayepsilon since using octane 2.0, so im hoping that means this is some issue with octane and not my video cards, as one is only a week old, and the other two only a few months old.

The first time i had the 999 error pop, it was 2 seconds after dialing rayepsilon down to 0.0 and resuming the render. So i experimented. I re-loaded the same scene and left rayepsilon alone, and it continues to render with no problems. As soon as i dial rayepsilon to 0.0, boom, down it goes. I also loaded another scene that i successfully rendered to 10,000 samples last night. Same with that one, as soon as i touched the rayeps setting, 999 error comes out to say hello.

Anyone else getting 999 error able to re-create this by reducing rayepsilon?

Paul, are you able to shed any light on this? Not ground breaking, as can still render if leaving rayeps alone, but hopefully this helps you/Otoy fix this if it is indeed an issue with octane and not my machine

edit: attached log

Ok, i am also getting the 999 error now.

In general, this seems to be a hardware error rather than an Octane issue. Try switching each video card off in turn to work out which is the problem card. Also, try under clocking the cards.

Paul

face_off wrote:

Ok, i am also getting the 999 error now.

In general, this seems to be a hardware error rather than an Octane issue. Try switching each video card off in turn to work out which is the problem card. Also, try under clocking the cards.

Paul

Hmm, thats scary. An issue with one of the 780s would mean i might have to replace both. But, im not certain theres an issue yet. Heres what happened trying to find which of the cards was the problem.

I used the cuda devices tab to test each card one by one. The first 780 in the list popped the error. So i disabled that one and tried the second 780. the second one also popped the error. So my wallet started to get nervous. Just to confirm i turned both 780s off and turned my 770 on. This time i did not get a 999 error, however i did get a total display driver crash. This happened within seconds of resuming the render, as the 999 error did using the 780s.

Could this be a driver issue? i am on 340.43, which is in beta. Is it worth rolling back to previous stable release?

Nubblet, this is well outside my area of expertise. But definitely worth a) rolling back Cuda drivers, and b) underclocking the cards.

Paul