OctaneRender™ Standalone 3.08 RC 3

[abstrax]

Thanks a lot for the reports. Yes, there was a bug introduced into the glossy material with RC 3, which Roeland fixed today. We found some other issue with the non-Octane BRDFs and try to solve it too and are planning to make another build tomorrow. Apologies for the trouble.

[cfrank78]

Marcus, do you also have found the issue with drivers above 390.xx and sometimes not showing cuda devices?

Searched the forum and especially gtx 7xx cards seem to have that problem!

Have a nice day - Chris!

[PolderAnimation]

Hi Abstrax,

I found that displacement maps only work on the first uv set, other uv sets are ignored.

[lassinger]

gpu driver 387.xx is not available for Sierra... ;(

Hi,
I can confirm that 3.08 RC 2 and 3 works correctly on Mac with internal Nvidia or via eGPU, and you need to update both CUDA and GPU drivers to 387.xx, in both Sierra or High Sierra:

CB51AD5C-A9D0-4ABD-A62D-B5D560F8AA4F.jpeg

ciao Beppe

[rrbarb]

macOS Sierra

CUDA = 387.128

GPU = 378.05.05.25f04

./rrb

[abstrax]

gpu driver 387.xx is not available for Sierra... ;(

Hi,
I can confirm that 3.08 RC 2 and 3 works correctly on Mac with internal Nvidia or via eGPU, and you need to update both CUDA and GPU drivers to 387.xx, in both Sierra or High Sierra:

CB51AD5C-A9D0-4ABD-A62D-B5D560F8AA4F.jpeg

ciao Beppe

We are currently using only the CUDA 8.0 toolkit, because on our test iMac, the latest CUDA driver doesn't work. I.e. you should be able to use any CUDA driver that supports CUDA 8.0 or higher. I will update the release notes.

[PolderAnimation]

I have a problem saving very large renders (15000x6000) with multiple passes in octane. If I try to save an ext with one extra pass it works but with more it crashes. I also can not render greater than 15k even when i have enough memory.

[cfrank78]

Cool. Thank you very much for not answering me Abstrax!

[abstrax]

Marcus, do you also have found the issue with drivers above 390.xx and sometimes not showing cuda devices?

Searched the forum and especially gtx 7xx cards seem to have that problem!

Have a nice day - Chris!

Yes, sorry forgot to reply. We have seen all kinds of issues with the 39x drivers. IF you check the log you will probably see that the CUDA initialization has failed. If that occurred, the only thing that helped was going back to 387 or 388. Unfortunately this option is npt available for our Quadro cards and on our OSX machine. We are currently in contact with NVIDIA, but have no solution yet.

[cfrank78]

Marcus, do you also have found the issue with drivers above 390.xx and sometimes not showing cuda devices?

Searched the forum and especially gtx 7xx cards seem to have that problem!

Have a nice day - Chris!

Yes, sorry forgot to reply. We have seen all kinds of issues with the 39x drivers. IF you check the log you will probably see that the CUDA initialization has failed. If that occurred, the only thing that helped was going back to 387 or 388. Unfortunately this option is npt available for our Quadro cards and on our OSX machine. We are currently in contact with NVIDIA, but have no solution yet.

Ai ai ai. You really seem to be very busy! I allready posted my log on the first site of this thread, when i asked here the first time.
It says:
CUDA error 999 on device -1: unknown error
-> failed to initialise CUDA driver API
Missing or invalid 'seconds_to_expiration' field from ORC server API response

I have to go to 39x.xx in the future. And i only have 780 cards so far for octane. So.........i hav emy fingers crossed! Btw, i only saw it as i believe in win 8.x. win 7 works well and 10 too as far as i can see. But changing OS is no option here.
Hope you find a solution soon!

Have a nice day. Chris!