Cinema 4D version 4.04-R2 (Obsolete stable) 06.05.2019 Tweet

[lucioing]

Hi Ahmet!
I'm still working with V4.01.1-R2.
My CUDA driver is:
CUDA Driver Version: 387.178 under MacOS 10.12.6
So, can I update to latest release? 4.04-R2
Thank you

L.

PS I'm working with a Hackintosh... So, as you know, isn't easy to update o.s. ...

[bepeg4d]

Hi Lucio,
please upgrade to v4.04-R2.
At least you need to update your RXX c4d copy to the latest build.
No problem with CUDA 387.178 under Sierra.
ciao Beppe

[lucioing]

Thank you Beppe...

L.

PS Fatte senti'...

[selor]

Link for Offline MANUAL didnt work ::!!:

[lucioing]

OK. I'm in trouble !
4.04 on main works fine
4.04 sa on slave works fine
daemon on slave doesn't works.
Here's some screenshot.
What's wrong with slave?

L.

[bepeg4d]

With High Sierra you need CUDA 410.130:
https://www.nvidia.com/object/macosx-cu ... river.html
Just install on top of the current installed version.
ciao Beppe

[lucioing]

Thank you Beppe... I'll try later...

L.

[3dworks]

beppe, just curious, what is wrong with 418.163? cheers markus

[bepeg4d]

Hi 3dworks,
the question should be asked to Nvidia.
No 418.xx CUDA driver versions are working with OctaneRender, and as far as I remember, it was never happened in the past.
Nvidia has fixed the issue in 419.xx and higher, but never published a fixed version for Mac, at least until yet.
ciao Beppe

[3dworks]

i am having an issue with live viewer and i can reproduce this in all my complex scenes.

when a scene is loaded in C4D and i start the live viewer the first time, data will be transferrend very fast to the engine, only a few non-octane materials in the scene are converted. if i stop and restart that preview render (also after i closed and reopened the lve viewer window), and start a preview, octane will take a much longer time to send all the data to the engine. i also can see that status will report a material conversion for ALL the used materials in the scene. in many cases it goes from a few sconds to nearly a minute! is this a known bug or could it be some setting which causes this?

C4D prime R20 V20.059 mac / macpro 5,1 48G RAM, nvidia 980ti 6G VRAM, mac os 10.13.6