Sorry maOS 13 Ventura is not supported yet.

Why would switching from Monterey with Metal to Ventura with Metal make a plugin scream for CUDA. That doesn't make any sense.

Is anyone else getting the "There is no CUDA device which is selected" nonsense on an M1 (Studio 32GB OS X Ventura) and knows how to solve this?

Did anyone get this to work on an M1 mini.

My Octane C4D plugin doesn't even show up. And if I set C4D R25 to open in Rosetta, some X-particles Lib makes it crash.

That's quite a shit show since standalone works on the mini.

+1 please update for r24 ! all my plugins work exept octane !
Thanks you !
When was the last time the C4D plugin was ready when a new C4D version came out?
What do you mean?

What I mean is that while all other developers of plugins seem to know when a new C4D version comes out, know what ...

wrapthereal66 wrote:+1 please update for r24 ! all my plugins work exept octane !
Thanks you !

When was the last time the C4D plugin was ready when a new C4D version came out?

387.10.10.30.106 doesn't help either. CUDA is not loading.

Just upgraded to OS X 10.13.4. with
CUDA 387.178 and Driver 387.10.10.30.106.

Doesn't work (CUDA error 999). Could anyone share a working driver combination for High Sierra?

Ahmet, it has been a while since an update. Are we going to see 3.1 next?

Ahmet,

3.07 and 3.08 don't play well with the OVDMmesher in XP4 (or vice versa). If the Octance C4D plugin isn't present all is fine. With the Octane plugin installed under OSX and R19, OVDBmesher causes a hard crash with a machine reset.

There's a lot of blaming on Octance in R19 under OSX ...

Ahmed, any chance we see a Mac lib file for R19 or will that come with the next test version?