C4D_PLUGINS_DIR Multiple path



  • On 03/08/2018 at 07:10, xxxxxxxx wrote:

    Hi, I wanted to update this topic because I encounter the same problem and it gets very problematic.
    Isn't it possible to bypass this issue, since it's corrected in R20? 
    (I'm working on R19.053)

    Thanks



  • On 03/08/2018 at 07:23, xxxxxxxx wrote:

    Hi all,

    sorry I forgot to report back, but as Alex says, it still does not work;

    In my case (also R19.053) I load the plugins from a network server, the C4D_PLUGINS_DIR environment variable looks like:
    C4D_PLUGINS_DIR=\\network\server\plugins\xparticles\4.0.0535/X-Particles;\\network\server\plugins\arnold_for_cinema4d\2.3.1/C4DtoA-2.3.1/plugins

    I don't think it's the path per se, since if I load them over the network separately they do work, it's the moment you've more than one that Cinema4D will crash and get stuck on the splash screen.

    In my case, I ended up bundling cinema4d with the plugins and server that over the network 🤷

    But really, it would be great if this worked.

    Cheers,

    Oscar.



  • On 06/08/2018 at 02:27, xxxxxxxx wrote:

    Thanks OscarD ;

    I should have given more details about my situation too :

    I work on osx, and both plugins work perfectly when added alone to C4D_PLUGINS_DIR ;

    My C4D_PLUGINS_DIR variable looks like this when both plugins are added :  **[path_to_plugin_1]:[ path_to_plugin_1]
    **
    When both are added simultaneously, C4D does not crash but simply opens without loading any of the two plugins (and I get a beautiful "_ Error: Additional plugin directory doesn't exists: [path_to_plugin_1]:[ path_to_plugin_1]_" in the terminal, since I launch C4D with it)



  • On 06/08/2018 at 02:36, xxxxxxxx wrote:

    Hi Oscar,

    so far we have no idea, yet, what could be causing this.
    And I'm not able to reproduce it here. On Windows with R19 SP2 (19.053) I can set C4D_PLUGINS_DIR as follows and plugins from both directories get loaded without issues.

    C4D_PLUGINS_DIR=\\server\mypath	est_plugins_1;\\server\mypath	est_plugins_2
    

    Could you provide us with some more details, please:
    Are you working on Windows or on macOS?
    You say, C4D crashes and gets stuck. Is it sometimes crashing and sometimes getting stuck? If there's a real crash, we'd be interested in the crash report (C4D offers to send one on next start). If it's only getting stuck, how long did you wait? Could it be just a matter of network speed?



  • On 29/08/2018 at 09:01, xxxxxxxx wrote:

    Originally posted by xxxxxxxx

    Hi Oscar,

    so far we have no idea, yet, what could be causing this.
    And I'm not able to reproduce it here. On Windows with R19 SP2 (19.053) I can set C4D_PLUGINS_DIR as follows and plugins from both directories get loaded without issues.

    C4D_PLUGINS_DIR=\\server\mypath	est_plugins_1;\\server\mypath	est_plugins_2
    

    Could you provide us with some more details, please:
    Are you working on Windows or on macOS?
    You say, C4D crashes and gets stuck. Is it sometimes crashing and sometimes getting stuck? If there's a real crash, we'd be interested in the crash report (C4D offers to send one on next start). If it's only getting stuck, how long did you wait? Could it be just a matter of network speed?

    Hi Andreas,

    sorry I must haven't seen the notification of the reply.

    We use Windows 7 (6.1.7601. SP1 ) and rez to load/launch the packages.

    At the moment I load Cinema4D R19.053 (Build RB224935) over the network as well;

    when launching Cinema, it shows the splash screen, "Loading Plugins" works, then starts "Initializing Plugins", and seems to load all all the way (the dots) and then it just says the standard windows error:
    "CINEMA 4D has stopped working - A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available" with the "Close program" as only option.

    When then I restart it I don't get any error report or similar (with only one plugin works).

    I just tried it with a Cinema4D installed locally, and still facing the same issue.

    I've seen that there is another update, I'll update and give it a go, although the changelog doesn't mention anything regarding this.

    Thanks,

    Oscar.


Log in to reply