I'm on OSXaoktar wrote:All you need is to add a "-parallel" parameter to "CINEMA 4D.exe" when you run it. I can do it easily from my old friend "Total Commander". Also you can use a "*.bat" file to run C4D or any other method. You can run many copies of C4D at same time.Yambo wrote:Ahmet, can you give please some short explanation on how to run 2 instances on cinema and render simultaneously?
Cooldown 52 mins...
Moderators: ChrisHekman, aoktar
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
Still waiting to hear how to get this working again in OSX. I cannot afford an hours downtime again today.
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
This is not expected issue. Maybe releated with something about with your network adapter.sdanaher wrote:Still waiting to hear how to get this working again in OSX. I cannot afford an hours downtime again today.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Its only happened with the latest version, all previous ones have worked fine in multiple instances of cinema.
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
I have to point this topic to investigate more. It can be related with some modifications on licensing system.sdanaher wrote:Its only happened with the latest version, all previous ones have worked fine in multiple instances of cinema.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
You mentioned a variable to edit on Windows... is there a corresponding one in OSX somewhere, or do you mean that it is not necessary in OSX (I know it wasn't necessary before but something in licensing seems to have changed)
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
Sounds like you are trying to run two separate installs of Cinema 4D at the same time, could you check to make sure both Cinema 4D installs are running the same version of the plugin?Still getting the 'its activated on another machine' error in R16.
It's running in R17, and I don't want to risk breaking that again.
There was an update to the licensing system for 2.24 on OSX, so switching between a 2.24 plugin and a 2.23 or earlier plugin or Standalone will cause this issue.
Yep that was it, thanks!hellguy wrote:Sounds like you are trying to run two separate installs of Cinema 4D at the same time, could you check to make sure both Cinema 4D installs are running the same version of the plugin?Still getting the 'its activated on another machine' error in R16.
It's running in R17, and I don't want to risk breaking that again.
There was an update to the licensing system for 2.24 on OSX, so switching between a 2.24 plugin and a 2.23 or earlier plugin or Standalone will cause this issue.
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3