[Xavier Bonet]

Hi Emir! Thanks for your reply! The “glass” sphere and emitter setup are 100% spot on. But I’m not seeing any particles “snowing” at all unless I disable the Plain, but that just makes it all work as normal. What I need are the particles inside the sphere but not outside (without having them bounce around, which would happen if I used dynamics). I don’t know if you’re seeing something different in your C4D. I’m using R19, if that makes a difference.

________________________________________
…So this is how I managed to bungle it up today.

[Xavier Bonet]

Yay! Great to hear that, Ian! I’m, glad you won’t be between a rock and a hard place come the next project.

I guess we’re never going to get an explanation from Maxon as to why these things are happening. I for one am DREADING having to update anything on my Mac… But the time is coming when I’ll have to. ????

________________________________________
…So this is how I managed to bungle it up today.

[Xavier Bonet]

Actually, I’m not 100% sure I know what I mean, as those observations weren’t mine, but rather the other sources I linked. But it’s my understanding that it’s not a hardware issue, but rather a software/system error. What I understand is that C4D is trying to gain access to memory but is failing or is being blocked for some reason. Another source (which I didn’t think I should quote without looking further into it) recommended to either whitelist the app:

“Put in an exception for google the app in gatekeeper:”
sudo spctl --add /Path/To/Application.app

Or to disable Gatekeeper (at least to see if there’s any change):

“Looks like disabling gatekeeper all together seems to work.”

As you mention, Maxon recommended 10.14 but it’s very likely that between .14 and .14.6 tweaked stuff around that has played havoc with C4D. Because we already know Maxon has (absurdly?) relied on private (and very much change-prone) system frameworks for C4D to function, it would’t surprise me at all to learn in a couple of weeks that someone found out it was one such system file that was either modified, moved or even supressed that is causing your issues. All this is actually the reason why I personally am still stuck on 10.12.6… ????

________________________________________
…So this is how I managed to bungle it up today.

[Xavier Bonet]

Hey, thanks, Brian! You’ve helped me out in the past with some C4D-related conundrums, so I’m very pleased I was able to give a little back! ????

________________________________________
…So this is how I managed to bungle it up today.

[Xavier Bonet]

Ok—so, again, remember: “stumbling in the dark”—having said that, if I were you these are the things I would look into:

EXC_BAD_ACCESS (SIGSEGV)—that’s your problem there, it seems to me. At least, from what I’ve found right now, this is the important bit:

“EXC_CORPSE_NOTIFY is irrelevant. The important information is in the Exception Type (EXC_CRASH (SIGABRT)) and the backtrace.”(https://stackoverflow.com/questions/34804117/got-a-exc-corpse-notify-symbol-crash-how-to-track-it)

And here:

“From your description I suspect the most likely explanation is that you have some error in your memory management.” (https://stackoverflow.com/questions/327082/exc-bad-access-signal-received)

Then, the only reference to the crash I see is: “Thread 0 Crashed:: Dispatch queue: com.apple.main-thread”

Can’t find anything specific about that, except that they recommend you use the Crashes Organizer to find out specifics about what the crash codes mean. Maybe this will help: https://help.apple.com/xcode/mac/current/#/dev861f46ea8

I’ll keep looking around to see if I find anything more relevant. But perhaps a forum member better informed about the ins-and-outs of how the macOS works will jump in and save the day!

P.S. Remember to reenable your System Integrity Protection after you’re done moving stuff around. It really should remain enabled.

________________________________________
…So this is how I managed to bungle it up today.

[Xavier Bonet]

Hi Ian!

Sorry about the equivocal “etc.”—probably wrote it late at night and tired of the fight with this issue! ???? I meant all other folder you can think of that holds temp files. It seems like you’ve done a pretty complete housecleaning in that sense… so I think I would safely say that your issue has nothing to do with the same issue we’ve had.

I think it would be good a idea to post the crash report. I’ll surely look over it to see if I can find anything weird, but I myself are very much stumbling in the dark in that area, so perhaps I won’t be of much help—but someone else in the forum might be!

Have a great day! And I hope you manage to resolve this soon!

________________________________________
…So this is how I managed to bungle it up today.

[Xavier Bonet]

Hi, Ian,

I’m sorry to hear you’re having this issue; as sorry as I am to hear this issue is still a thing and that all Maxon are doing to solve it is linking back to this post… I too wondered why they would rely on a private framework, let alone one that has to do with mobile device support.

Anyway, as for your first question: Indeed, I got the error in Console, at the very end of the startup attempt:

WARNING: Could not load dll. Error code: dlopen(/Applications/MAXON/Cinema 4D R19/corelibs/c4dplugin.xlib, 6): Symbol not found: _xpc_file_transfer_create_with_path
Referenced from: /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice
Expected in: /usr/lib/libSystem.B.dylib
in /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice. (file:///Applications/MAXON/Cinema 4D R19/corelibs/c4dplugin.xlib) [osx_dll.cpp(89)] [general.cpp(266)]

The fact that you’re not getting this, that swapping the framework file hasn’t worked for you, and that your issue started after you updated elsewhere makes me think that perhaps your issue isn’t related to the MobileDevice.framework.

Do you get any warnings at all in the Console? Look for the word “error”. What do you get just before the the startup process exits?

If you haven’t already, maybe the following are worth a try:

[Xavier Bonet]

Sorry for the delay! I’ve been traveling shooting material for the last week or so, so I haven’t kept up to date online. You’ve probably solved this by now but, for what it’s worth, to you or anyone else, here goes the working framework file:

13785_mobiledevice.framework.zip

Hope this helps!

P.S. I’ve had to compress it because, otherwise, the CC uploader wouldn’t let me select the file. I hope that doesn’t mean these kinds of files aren’t allowed on CC, only project files.

________________________________________
…So this is how I managed to bungle it up today.

[Xavier Bonet]

Hi, Jake! I’m very glad you were able to solve your issue as well!
And thank you very much for letting me know you found the troubleshoot useful, you’re very kind! I often benefit from the knowledge of others here at Creative Cow but there are so many knowledgeable people around, and then the stuff I do is usually so specific and niche, that it’s not often I get to chime in and return the favor! So I’m very glad something good came of it!
Cheers!

________________________________________
…So this is how I managed to bungle it up today.

[Xavier Bonet]

Hi, Eros! Do you have access to any other Mac running the same or a similar OS? Perhaps a friend’s?If you do, you can get the file you need to substitute. You don’t need to get rid of the entire iTunes folder.

If you haven’t already, check out the step-by-step instructions to solve this issue I posted in my previous-to-last post above.

Hope you can solve this soon, too!

________________________________________
…So this is how I managed to bungle it up today.