3dsmax with Vray 3.4 does not inherit CPU assignment anymore

[baumgore]

We used to take away some CPUs plus lower the CPU-affinity for the network-render-manager clients on the workstations, which in turn inherit this to the started network rendering 3dsmax, allowing the artists to work flawlessly while rendering with their local 3dsmax. We always have enough ram in the workstations for local and network render simultaneously.
With the 3.4 upgrade network-3dsmax renders with Vray with all CPUs and don't inherit the decreased CPU assignment from the network-client-software.
I didn't even know Vray can change this, cause I it is a Windows OS behavior/feature that child processes inherit parents properties.

Nevertheless could you please change this CPU override back to standard?

3dsmax 2016 on Windows 7-10, Vray 3.40.01

[vlado]

We will not change it back as it will prevent V-Ray to work with more than 64 threads by default. You can disable this functionality yourself if you set the environment variable VRAY_USE_THREAD_AFFINITY=0

You can also control how many threads V-Ray will use through the VRAY_NUM_THREADS environment variable - this is generally preferred to tinkering with CPU affinity.

Best regards,
Vlado

[baumgore]

Ok, I understand and I thank for the quick answer. Will set it by hand, our workstations have max 48 threads.

[crazy homeless guy]

It would be best if there should be an option to set the environmental variable when you install Max.

The reality is the number of people with 64 thread machines are the vast minority. My vote would be that the setting in the installer would enable 64 threads or greater and that by default it installed the way it did before.

[vlado]

It could be done, for sure... will think about it.

Best regards,
Vlado