I’ve actually been testing this recently with Octane 3.08 w/ C4D R19 and due to some issues with our multi-gpu machine we haven’t gotten around to testing if it’s actually respecting what gpus are being set on the command-line.
If anyone’s down for a quick test or two, I’d appreciate it if they could run similar command-line options and try turning on/off gpus the way that’s suggested and post their results here.
I’ve made the changes to the plugin and submission files for C4D (for recent versions of Deadline 10). If you get a chance to test it out, please let us know your results here! Would be greatly appreciated!
Instructions:
Download and un-zip the contents of the attached file
Back-up your existing cinema 4d files that you’re about to overwrite
Copy “Cinema4DSubmission.py” to “DeadlineRepository10/scripts/Submission”
Copy “SubmitC4DToDeadline.py” to “DeadlineRepository10/submission/Cinema4D/Main”
Copy “Cinema4D.py” to “DeadlineRepository10/plugins/Cinema4D”
Copy “Cinema4DBatch.py” to “DeadlineRepository10/plugins/Cinema4DBatch”
From here the Cinema 4D plugins will attempt to set the gpu affinity for Octane. Let me know if you run into any issues!
sorry, still uses all 4 GPUs.
I also disabled Use all GPUs inside C4D scene and submitted as 1 concurrent task 2 GPUs, and it is rendering with all 4 again.
Thanks for taking a look. From what we can tell over here, we’re following what they say to use. Unfortunately, it doesn’t look like they’ve added support for the -help flag, so we can’t see if this format is actually what they expect.
I’ll post or send a message asking about them this.
Would it be possible for you to also do a test render with Cinema4D non-batch? I expect the results to be the same, but I’d definitely appreciate having that datapoint available.
It is 3.07
Sorry was cleaning up deadline tasks and remove d this one but will add it again a bit later and submit log here. no problem.
Just have to clean active tasks a bit
What I’ve found is that the Octane command-line flags for C4D (ie. exporting orbx files) don’t appear to work as expected with the commandline.exe executable or with the -nogui option. I’ve brought this up with the Octane developers but there doesn’t appear to be movement on the issue.
Can you set Cinema4D.exe as the executable in the plugin configuration and see if that works for gpu affinity? I believe it’ll spawn a UI, but confirmation would be good to have.
It renders using all GPUs but the once finished rendering it sets 2 GPUs to active. I also tried putting the -octaneGPU before -render but still the same result.
I contacted OTOY support and they confirmed the problem:
We are also having issues with our deadline test machines and currently investigating.
Please do let us know if you receive any guidance from the AWS team.
I would be very grateful for experience how to solve this problem and ready to conduct tests on my equipment according to your instructions
I just have same issue, it seems like octane use all GPUs regardles worker GPU affinity settings (to be correct you need to use octane 2021.1.7 and higher - older versions has 2GPUs limitation).
Due my research, one worker with multiple GPUs has some benefits:
you need one license per worker (octane/ C4D/ you name it)
its easier to manage/ update
you can build cheaper and more poverful setup with multi GPUs setup vs one latest GPU
I also run some test, but somehow its seems like 2 workers with 2GPUs are faster then 1 worker with 4GPUs (RTX 3070 to be exact)
otoy technical support writes that this problem has not been solved
'in short, they have answered from a C4D point of view, but c4doctane is different, and you cannot control GPU assignment via commandline.exe, or cinema4d.exe, indifferently.
To add specific command-line Octane commands/arguments, the only way is to use Octane Standalone workflow."