NEW: Octane X - is finally here! [MEGA FAQ THREAD]

[atracksler]

Hi octane team, any updates on the silicon build? I know you’re working hard, but it’s been almost 6 months into my year subscription without being able to use octane in Cinema. Was hoping to get some insight.

[bepeg4d]

@Leandersson: the log shows that also RedShift is installed, but it is incompatible with the Rosetta mode:

So you should need to have two versions of C4D installed, one for native plugins like RedShift, and another one in Rosetta mode for c4doctaneX and any other plugin not in native mode for M1 chip.

@altestudio and atracksler: we need to wait for the upcoming 2022.1-XB2 SDK, the core devs are working on it, to have the first M1 c4doctane plugin, also supporting ACES/OCIO.

ciao,
Beppe

[Leandersson]

@Leandersson: the log shows that also RedShift is installed, but it is incompatible with the Rosetta mode:

04C4B06B-619E-4EA4-99C7-BFEA24332675.jpeg

So you should need to have two versions of C4D installed, one for native plugins like RedShift, and another one in Rosetta mode for c4doctaneX and any other plugin not in native mode for M1 chip.

Thank you! Unfortunately, this did not help. I removed Redshift for the Rosetta version of C4D and the result is still the same.
It doesn't seem to be an issue with other plugins but rather something with the GPU since I still get this error message.

Compute error 2097152:825:
compute device 0: Linking 00696900aaaadec4 shader failed
device 0: failed to initialize render thread 0x7f7d92816160

[sebbans]

Just want to say, I'm super thankful OctaneX works on my Silicon Mac in C4D r25, fantastic to use. And I'm really looking forward to the first native plugin for S26 so that I can run everything natively without having to switch between versions.

[tolitoli]

it seems my subscription will end but I will not try M1 c4doctane plugin
I have been waiting since October 2021

[bepeg4d]

@Leandersson: please write to help at otoy dot com, asking for Beppe, I need to investigate more deeply.

@sebbans: Thanks for your positive feedback!!!

@tolitoli: for licenses issues, please write to help at otoy dot com too, thanks.

ciao,
Beppe

[altestudio]

@altestudio and atracksler: we need to wait for the upcoming 2022.1-XB2 SDK, the core devs are working on it, to have the first M1 c4doctane plugin, also supporting ACES/OCIO.

ciao,
Beppe

Thanks Beppe. Do you have a rough timeline for when this is likely to be released? Are there usually announcements when there are new releases? Octane is working better on my mac than I expected and aces will be the cherry on top!

[bepeg4d]

@Leandersson: sorry, didn't notice at first time, but c4doctane plugin is installed in a custom wrong path, and even worse, in Dropbox

Please go to c4d menu Edit/Preferences/Plugins, and remove the octane folder from the list:

The installation paths for Mac is:

• HD\Applications\Maxon Cinema 4D R2X\plugins\C4D-OctaneX-PR14 (You have to create the plugins folder in lower case!)

After installation, please open c4d, then go to c4d menu Extensions/Console, (Shift+F10), and copy paste the default console output in your answer, thanks.

Please, also share a screenshot like this one, that shows both the c4doctane directory opened, and the entire installation path, thanks:

ciao,
Beppe

[Ainionu]

So denoiser in PR14 on M1 does not work right? Or is there some kind of trick I don't know about? It does not crash it simply cannot finish rendering... Without denoiser it renders about two minutes one frame, with denoiser turned on my patience ended after twenty minutes when renderer still hadn't finished rendering. Any suggestions?

[bepeg4d]

So denoiser in PR14 on M1 does not work right? Or is there some kind of trick I don't know about? It does not crash it simply cannot finish rendering... Without denoiser it renders about two minutes one frame, with denoiser turned on my patience ended after twenty minutes when renderer still hadn't finished rendering. Any suggestions?

M1 chip is completely different from previous CPUs, and does not have the necessary AVX2 instructions for performing AI Denoiser, and Denoised passes.
So AI Denoiser, and denoised passes must to be disabled, or the render never finishes.

Alternatively, you can try with Hot pixel removal slider in Camera Imager node, but avoid to go under 0.65, and consider that it is distructive, so you can have artifacts.

Another option is to try with internal C4D Denoiser in Picture Viewer, but it is not like AI Denoiser:

ciao,
Beppe