gsmetzer

I'm having this same issue, any solve for this? Still a problem in R25.

I'm having the same issue, did you find a solve for this?

Well, I opened S24 after clicking "open with Rosetta" under Get Info. Corona renderer has shown up and seems to be working fine. I'm not sure what I'm missing using c4d with Rosetta but hopefully it isn't a problem.

S24.111, latest corona and latest redshift builds as of today. I don't think builds is the issue though...

I have tried everything here, trashed preferences, linked plugin folders to different places but s24 plugins (on a m1 Mac) doesn't show up. Specifically corona renderer and redshift. Anyone else had this issue? Any ideas to get it to work?

Mac Users: Update on M1 Apple silicon. Working amazingly well with R23 but hold out for machines with more RAM when Apple releases them. The Mac mini M1 is smooth as butter between applications and I have had limited crashes and mostly because of plugins or doing experimental commands. Only limits is the measly RAM. I team render with my PC to handle most of the rendering workload.

Update: So my 6 year old Intel based MacBookPro's battery swelled up. I went out and bought a MacMini M1. I'm using Corona renderer and it is working great, team render too.

My Intel based Mac running BigSur is unusable with any version of Cinema4D. So I switched to and have been working on my PC. On the PC with one of my files all the generators disappeared in the viewport. I have checked everything including Viewport filters etc. Pulling on the handles of generators sometimes pops them back into view. Trashed prefs etc. no avail Otherwise the file is corrupt, on older versions too. I'll file a bug report but this has been severely limiting and I've never found a buggier version of c4d. Been using since R8. I'm starting to think this isn't just Apple's issue with Intel GPU's but also C4D GPU handling. Hope we can figure this out and happy to help MAXON in any way I can. Otherwise c4d is amazing. I'm wondering if all the GPU programming talent has been sucked into the crypto mining world? AMD Ryzen 24core Intel 1070ti GPU Windows 10 -Using nested generators, suddenly disappear in viewport after two hours of work.

Weird it disappeared in R23. Sound rendering was pretty useless as it was implemented. However, I do think MAXON has a huge opportunity to implement a game engine sound module like FMOD or WWISE that does 3D sound rendering really well. It would be a huge feature for motion graphic designers.

Is your Mac an Intel? or M1? I just updated to the 11.2 macOS Beta and still crashing. 😞 I will probably downgrade to Catalina this weekend, I have work to do and not seeing any response from Apple on this. Luckily I have a PC that is working fine. Here is the other main forum:

For those having issues please include the following, Operating System and version: GPU and CPU Make and model: Cinema4D version: What were you doing at time of crash: It'll help narrow down where the problems are occurring. Thank you! For example my issues, macOS BigSur Beta 11.2 Intel Iris Pro, Quad i7 R23.110 Adding an object or spline.

Someone in another forum says they are getting constant crashes on their new Apple with M1 processor, so I don't think it is old Intel GPUs. As far as I can tell it is an openGL issue related to spline rendering. That is my guess. I can't even add a cube without crashing c4d. Then when I un-check Filter/Handles I can add a cube. Weird. When I turn all the filters off I cannot add a spline without crashing.

Interesting, if issues happen on M1 then Intel GPU theory is bunk and might be c4d side issue. Dragging is handled by C++ (I think) I'm assuming it is a memory leak of some sort? Unfortunately with the holidays, developer investigation probably won't happen until later.

As found in another forum, if your Mac has an Intel GPU, like the Intel Iris Pro, c4d will be un-usable. Make sure to send a support ticket to apple to look into the issue. I know Apple uses c4d for their 3D graphics so they may be sympathetic and fix soon. (Hopefully)

Hey Cababa, I've had a 15 year career in motion design. Doing sculptural work like your references are going to be fun to make but probably pretty difficult to monetize. I recommend you practice what you love, keep it fresh and a studio may like to incorporate your style into commercial work. Continually develop a demo reel to get those commercial contracts. Start billing those at around $350/day (US) In a few years you can get up to $500/day. As far as technique, of course I would recommend c4d and a good renderer. For GPU rendering use Redshift or Octane, if you render on your CPU use Corona Renderer (more for archive). Knowing these will help you pretty easily get into commercial production for a little film but mostly commercial agency and corporate brand work. For your references get good at displacement mapping and volume rendering. Get Xparticles as a plugin. Best thing is to learn the fundamentals, sounds like you have a base in sculpture, great start, learn about 3 point lighting, color theory etc etc. and buy Drawing On The Right Side of The Brain, its a classic to help you tap into the subconscious well of creativity. For animation, learn the 12 principles of motion. Follow Motionographer, School of Motion and Wine after Coffee. Most of all, never ever ever never ever stop learning, learn every day. Learn to pick up new software and just click around, break it and restart fresh. You'll develop fast. Have fun! Gabriel

Thank you, Yes my 2015 MBP has the Intel Iris Pro GPU running into same issues since BigSur/R23 upgrade. Looks like I'll have to wait for Apple to fix? That may take a long time or never happen. I'll send a report to Apple.

Anybody figure out a solution for this?

Having same issues with BigSur c4d r23.110, I have tried trashing prefs, deleting Wacom driver and getting zero functionality from c4d. App opens fine but crashes as soon as I add anything to the scene. Running a 2015 MacBook Pro with an IrisPro GPU. R21 won't open at all. I cannot send crash report as the dialogue doesn't appear. I tried the hotkeys to send crash report but no luck. Good thing I have a PC running everything fine 🙂

Yep, me too, on my MBP after upgrading to BigSur. Cannot send a crash report either. I tried trashing all my preferences. Still nothing. Crashing immediately after adding an object to the scene.