Page 9 of 12
Re: Cinema 4D version 2018.1-R3(Latest stable) - 29.03.2019
Posted: Mon Apr 01, 2019 3:34 pm
by bepeg4d
Hi,
please update to the latest Apple security update, then try to update only the GPU driver to the following version:
https://www.nvidia.com/download/driverR ... 2147/en-us
ciao Beppe
Re: Cinema 4D version 2018.1-R3(Latest stable) - 29.03.2019
Posted: Mon Apr 01, 2019 6:27 pm
by SRCOBB
Well, I downloaded the latest security update, and now my system is incompatible with an Nvidia web drivers.....
Trying to figure out how to undo a security update, which I don't think is possible. I sure hope that wasn't an April Fool's joke! (kidding)
UPDATE:.
It looks like Apple just re-updated their most recent security update, and it killed Nvidia drivers in Macs like mine. In fact, my computer didn't recognize that I had any GPUs. Searching the internet, I found people in the same boat in some very techy "Hancintosh" forums, and in the last day or so, they even came up with some workarounds that involved a lot of terminal/code stuff that makes me uncomfortable. I got about half way through all of that, when I found that Nvidia saved the day by releasing a brand new web driver today! GPUs working again.. security up to date. We'll see if there's any change in 2018.1 behavior. First I have to downgrade my CUDA driver, because Octane will not work with the latest. Sorry to be long-winded. That all made for a scary day and eventually a huge sigh of relief.
Update 2:
Still freezing up regularly.
Re: Cinema 4D version 2018.1-R3(Latest stable) - 29.03.2019
Posted: Tue Apr 02, 2019 4:10 am
by FullHPetroL
It seems there is a render region issue.
it somehow locks at 60 samples. It goes up after render region is re-enabled.
Re: Cinema 4D version 2018.1-R3(Latest stable) - 29.03.2019
Posted: Tue Apr 02, 2019 6:12 pm
by Domenicozzo
Hi Ahmet,
With the latest 2018.1 versions, I'm getting a lot of crashes when I happen to resize the LV, this never happened with the earlier versions of Octane, am I the only one?
Cheers,
Domenico
Re: Cinema 4D version 2018.1-R3(Latest stable) - 29.03.2019
Posted: Wed Apr 03, 2019 12:44 pm
by leehenshall
Hi Guys,
Is it just me or is the film attribute missing from the specular material?
Missing in C4D
Present in SA
Is this a bug?
Re: Cinema 4D version 2018.1-R3(Latest stable) - 29.03.2019
Posted: Wed Apr 03, 2019 1:04 pm
by aoktar
leehenshall wrote:Hi Guys,
Is it just me or is the film attribute missing from the specular material?
Missing in C4D
film_missing_01.JPG
film_missing_02.JPG
Present in SA
film_missing_03.JPG
Is this a bug?
Looks like I overlooked to display this part for specular material. I'll fix for next build. As a workaround set it with glossy type and switch to specular.
Re: Cinema 4D version 2018.1-R3(Latest stable) - 29.03.2019
Posted: Wed Apr 03, 2019 1:16 pm
by leehenshall
Thanks for confirming aoktar
I'll use the work around for now.
Thanks

Re: Cinema 4D version 2018.1-R3(Latest stable) - 29.03.2019
Posted: Wed Apr 03, 2019 4:11 pm
by pixelbrain
Getting consistent crashes (spinning rainbow ball) on Cinema 4D 20.059 (Build 272827), OctaneRender Enterprise 2018.1 (5000010).
Mac Pro (5,1) 2.4 GHz 12-core Intel Xeon
128 GB RAM
Mac OS 10.13.6
GTX 980 Ti + GTX 1080 Ti
NVIDIA Web Driver 387.10.10.10.40.122
CUDA Driver 410.130 (confirming 418.105 breaks Octane)
Re: Cinema 4D version 2018.1-R3(Latest stable) - 29.03.2019
Posted: Wed Apr 03, 2019 5:46 pm
by Iceman9
2018 has been super stable for me so far. But I’m on PC. A few glitches here and there that I will report later, but stable and sweet.
Apple being at war w/Nvidia is going to make Mac support difficult I suspect.
Re: Cinema 4D version 2018.1-R3(Latest stable) - 29.03.2019
Posted: Wed Apr 03, 2019 5:59 pm
by SRCOBB
pixelbrain wrote:Getting consistent crashes (spinning rainbow ball) on Cinema 4D 20.059 (Build 272827), OctaneRender Enterprise 2018.1 (5000010).
Mac Pro (5,1) 2.4 GHz 12-core Intel Xeon
128 GB RAM
Mac OS 10.13.6
GTX 980 Ti + GTX 1080 Ti
NVIDIA Web Driver 387.10.10.10.40.122
CUDA Driver 410.130 (confirming 418.105 breaks Octane)
I'm glad (I guess) to see that I am not alone!
Someone suggested to me that it may not be the plugin, but in the standalone app?.. I just hope it gets worked out.