Cinema 4D quit unexpectedly (R23-25) after about 1 and a half minutes. This is with just having a project open and not doing anything, no live viewer open or rendering happening.
I've tried to get to the bottom of it by removing all my plugins 1 by 1 and it seems that Octane PR13 is the culprit.
Can I send a c4doctanelog.txt bug report to your mac team?
NEW: Octane X - is finally here! [MEGA FAQ THREAD]
Forum rules
For new users: this forum is moderated. Your first post will appear only after it has been reviewed by a moderator, so it will not show up immediately.
This is necessary to avoid this forum being flooded by spam.
For new users: this forum is moderated. Your first post will appear only after it has been reviewed by a moderator, so it will not show up immediately.
This is necessary to avoid this forum being flooded by spam.
Please write to help at otoy dot com, asking for me.atoyuser1 wrote:Cinema 4D quit unexpectedly (R23-25) after about 1 and a half minutes. This is with just having a project open and not doing anything, no live viewer open or rendering happening.
I've tried to get to the bottom of it by removing all my plugins 1 by 1 and it seems that Octane PR13 is the culprit.
Can I send a c4doctanelog.txt bug report to your mac team?
ciao,
Beppe
many thanks - I just realised PR13 is in development, dohbepeg4d wrote:Please write to help at otoy dot com, asking for me.atoyuser1 wrote:Cinema 4D quit unexpectedly (R23-25) after about 1 and a half minutes. This is with just having a project open and not doing anything, no live viewer open or rendering happening.
I've tried to get to the bottom of it by removing all my plugins 1 by 1 and it seems that Octane PR13 is the culprit.
Can I send a c4doctanelog.txt bug report to your mac team?
ciao,
Beppe
-
dannydisaster93
- Posts: 4
- Joined: Thu Jan 21, 2021 12:02 pm
I've spotted that the PR13 release notes say that only AMD made RX 6900 XT cards are supported on PR13 due to issues with the OS. Just to confirm all board partners i.e. ASUS cards for this line are not supported with PR13 anymore? I'm running Octane PR11 just fine on BigSur with a non-reference 6900 XT but don't want to take the plunge in updating to Monterey for PR13 if my card will no longer be able to run Octane.
I use Cinema 4d 25, and I use plugins that don't work through a M1 (Rosetta), but work M1 (native)
because now Octane X is not displayed in C4D and opening with help Rosetta is not suitable for me
when to expect native support Octane X for m1 ?
because now Octane X is not displayed in C4D and opening with help Rosetta is not suitable for me
when to expect native support Octane X for m1 ?
Hi All,
Hope this might help some of you who are trying to install Pr13 on a MacOS Monterey (12.0.1), I had some issues while installing and made a youtube video tutorial should you be having difficulty.
https://www.youtube.com/watch?v=N8HEepX ... jax4AaABAg
Hope this helps!
Hope this might help some of you who are trying to install Pr13 on a MacOS Monterey (12.0.1), I had some issues while installing and made a youtube video tutorial should you be having difficulty.
https://www.youtube.com/watch?v=N8HEepX ... jax4AaABAg
Hope this helps!
Thanks for this, interesting it says install the plugin in preferences. I just had a reply from Beppe that it should be in the the Application folder:ProTharan wrote:Hi All,
Hope this might help some of you who are trying to install Pr13 on a MacOS Monterey (12.0.1), I had some issues while installing and made a youtube video tutorial should you be having difficulty.
https://www.youtube.com/watch?v=N8HEepX ... jax4AaABAg
Hope this helps!
The correct installation path for Mac is:
HD/Applications/Maxon Cinema 4D R25/plugins/C4D-OctaneX-PR13 (You have to create the plugins folder in lower case!)
Yes please, better to create the plugins folder in lowercase in /Applications/Maxon Cinema 4D R2X/ directory, and place the uncompressed c4doctaneX folder there, removing from the c4doctaneX folder all the unnecessary c4doctane-R2X.xdlib files not related with R2X specific version, and leave only one c4doctane-R2X.xdlib file in ../plugins/c4doctaneX directory.
Avoid to add the c4doctaneX folder in c4d menu Edit/Preferences/Plugins, or you will have a conflict.
ciao,
Beppe
Avoid to add the c4doctaneX folder in c4d menu Edit/Preferences/Plugins, or you will have a conflict.
ciao,
Beppe
Thank you !ProTharan wrote:Hi All,
Hope this might help some of you who are trying to install Pr13 on a MacOS Monterey (12.0.1), I had some issues while installing and made a youtube video tutorial should you be having difficulty.
https://www.youtube.com/watch?v=N8HEepX ... jax4AaABAg
Hope this helps!
Also for the explanation on how to use RDNR on Mac !!
Mac Pro (5,1 | 2010 | 12 Core | 48GB Ram) • Nvidia GTX 980 + 1080 • Cinema R19 Studio
hey i hope someone will see this,
i want to get a PC slave working with my m1, when will this happen? i cant find any documentation on the version compatibility and its extremely frustrating to say the least. this is so far from being production ready when that is missing along side the lack of denoiser.
when monterey p12 came out, i was told id have to wait a version for render slave support, now in p13 i still cant do it and i have no idea what compatiblity across differently named versions will look like. can we please get some office word on the roadmap for how this will work so i dont have to pull my hair our 2 times a month in these forums looking for an answer.
im so tired of this versioning getting so messy and no documentation to clearly explain what everything means and the cross compatibility. put it somewhere easy to find! please
thank you, be safe
i want to get a PC slave working with my m1, when will this happen? i cant find any documentation on the version compatibility and its extremely frustrating to say the least. this is so far from being production ready when that is missing along side the lack of denoiser.
when monterey p12 came out, i was told id have to wait a version for render slave support, now in p13 i still cant do it and i have no idea what compatiblity across differently named versions will look like. can we please get some office word on the roadmap for how this will work so i dont have to pull my hair our 2 times a month in these forums looking for an answer.
im so tired of this versioning getting so messy and no documentation to clearly explain what everything means and the cross compatibility. put it somewhere easy to find! please
thank you, be safe