question

@Stephen Blair You are a genius! That indeed worked perfectly. Previously I had been stopping at ".app", and wasn't diving into Contents.

For future use, is it possible to make these paths permanent so the users don't have to go through the terminal each time? Or, is that the preferred method?

Thanks again for all your help, I owe you a taco!

Yup, DYLIB_LIBRARY_PATH is not set in the CINEMA 4D environment.

You start CINEMA 4D from that same terminal, like this?

export DYLD_LIBRARY_PATH=/Applications/Autodesk/maya2018/plug-ins/xgen/lib:/Applications/Autodesk/maya2018/Maya.app/Contents/MacOS

"/Applications/MAXON/CINEMA 4D R20/CINEMA 4D.app/Contents/MacOS/CINEMA 4d"

@Stephen Blair Here are the results of running that command based on the PID:

/Applications/MAXON/Cinema
4D
R20/cinema
4d.app/Contents/MacOS/CINEMA
4D
TMPDIR=/var/folders/wx/cwhm6snn1wdd23pd7zrhk0nr0000gn/T/
TERM_PROGRAM=Apple_Terminal
__CF_USER_TEXT_ENCODING=0x1F5:0x0:0x0
HOME=/Users/tedowens
SHELL=/bin/bash
_=/usr/bin/open
Apple_PubSub_Socket_Render=/private/tmp/com.apple.launchd.Q2C5Ogmajb/Render
SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.IFkOqnvv3f/Listeners
TERM_PROGRAM_VERSION=388.1.2
SHLVL=1
TERM_SESSION_ID=37F25651-4FFC-47C4-AD6F-5C0F3F461381
PATH=/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
LOGNAME=tedowens
TERM=xterm-256color
XPC_SERVICE_NAME=net.maxon.cinema4d.12196
LANG=en_US.UTF-8
USER=tedowens
XPC_FLAGS=0x1
PWD=/Applications/Maxon/Cinema
4D
R20

Also, for what it's worth, here's the line I'm using to set the path, I'm not sure if there's something amiss there. I double-check it with the echo command, and it appear to work, but clearly C4D isn't seeing it:

export DYLD_LIBRARY_PATH=/Applications/Autodesk/maya2018/plug-ins/xgen/lib:/Applications/Autodesk/maya2018/Maya.app/Contents/MacOS

@Stephen Blair I ran the command again, this time doing a render to picture viewer as opposed to IPR. Not sure if it's different, but searching through the log I see MtoA listed, so hopefully that's the information you're looking for.dtruss-2log.zip

@Stephen Blair Hmmm, well, those are the results of running that command. Not sure why they say HoudiniFX, we don't have that installed on that machine. Also, searching through the log file I can see MtoA listed, but not sure what it's supposed to show. I can try it again if you'd like. I followed the instructions to the letter. (FYI, this is trying via the IPR)

Thanks for helping to troubleshoot this, Stephen. Though I'm still not ruling out something that I'm doing wrong.

Attached is the dtruss.log file.dtrusslog.zip

The mtoa particle procedurals don't have any extra dependencies, so they will always load.

The license doesn't matter.

So, it looks like some dependency is still missing when loading xgen_procedural from a running CINEMA 4D

In a Terminal, open two tabs:

• In one tab, set DYLD_LIBRARY_PATH and start CINEMA 4D.
• Load a scene that uses xgen
• In the other tab, start dtruss:
  sudo dtruss -f -n CINEMA 2>~/dtruss.log
• In CINEMA 4D, try to render
• Go back to the terminal, and press CTRL+C to stop dtruss
• Post the dtruss.log so we can check what's happening

Hello Stephen, thanks again for the troubleshooting! Indeed, I am starting from the command line. What's odd, is that in looking through the log I posted, it seems to be accepting the mtoa particle plugins, but it's when it hits the xgen that it reports a warning:

C4DtoA | 00:00:00 799MB | loading plugins from /Applications/solidangle/mtoa/2018/procedurals ...
C4DtoA | 00:00:00 799MB | mtoa_ParticleInstancer_proc.dylib: particleInstancer uses Arnold 5.2.2.1
C4DtoA | 00:00:00 799MB | mtoa_ParticleVolume_proc.dylib: volume_particle uses Arnold 5.2.2.1
C4DtoA | 00:00:00 799MB | mtoa_ParticleVolume_proc.dylib: implicit_particle uses Arnold 5.2.2.1
C4DtoA | 00:00:00 799MB WARNING| unable to load dynamic library /Applications/solidangle/mtoa/2018/procedurals/xgen_procedural.dylib:
C4DtoA | 00:00:00 799MB WARNING| unable to load dynamic library

Both machines tested are using the freshest installs of MtoA and C4DtoA; Maya is also the latest (2018.5), and I've tried in both Cinema R19 and R20. The Macs are High Sierra, though I can try on a Mojave machine tomorrow if it helps. I'm not sure if it makes a difference, but the only other thing worth noting is that our Arnold's are floating and run through a license server, just in case that changes any of this.

I'll bring in my PC laptop this week as well and try rendering from it, just to see if I have more luck there.

You are starting CINEMA 4D from the command line, right? From the same terminal where you set DYLD_LIBRARY_PATH ?

Thanks for checking, Stephen. In the meantime, I tried this on another Mac, and still got the same error. I also tried in R19, with no luck. So, whatever I'm doing wrong, it's affecting multiple machines and multiple versions of Cinema.