We’ve been noticing that the CPU affinities are not being respected on our machines. We have the affinities set so that it leaves one core for the system to avoid lockups. As you can see in the screenshots, it looks like 3ds max is not respecting it.
Deadline Build: 8.0.4.1
Thanks for reporting this, we’ll try to get this fixed asap! Was this with the Plugin Sandboxing turned on? I’m wondering if that’s where the regression was introduced, or if it’s across the board…
Hey Robert,
Unfortunately we’re having issues replicating this issue on our end 
, would you be willing to send us more information to help identify the issue? What version of 3ds max are you using? Does this happen on more than just 3ds max? What kind of settings are you submitting on the jobs that fail to have the proper affinity? Are all slaves for that machine configured to ignore that cpu? Was this exact same setup working on a previous version of Deadline?
Does this older forum post hold any positive results for you? Having that on or off didn’t end up affecting me on my end, but maybe it’ll affect you…
Thanks!
Hey,
We are using 3ds Max 2015 SP3. We’ve taken a look at our Maya and Nuke jobs and they are setting CPU affinities correctly. Taking more of a look at this, we are seeing some machines are getting the CPU affinities set correctly and some are still working properly. All running 8.0.4.1. We’ll take a look to see if it’s a certain type of job that’s hitting our farm which is not getting the proper affinity.
We have two slaves running on our machines, one slave told to not use core 0, the other slave told not to use core 1.
This was working in Deadline 7.
Hmm, a few more questions at the top of my head then…
For the Maya/Nuke jobs, does the CPU Affinity work correctly on a machine that doesn’t have the 3dsmax CPU Affinity working?
Does the same 3dsmax job that doesn’t respect CPU Affinity work fine on another machine?
Does a machine with CPU Affinity not working for 3dsmax jobs consistently fail to set it properly (for the same job or different jobs)? Or is it intermittent?
Which renderer are you using?
Hey Robert,
Are you still experiencing issues with this?
Thanks
Update for folks here. We’ve got a fix merged into 8.0, so it should be included in the next release. Keep your eyes open for SP8 
