3dsMax process not "killed" after rendering!

Hi,

I am having some issues with the 3dsmax process not closing after rendering. I guess it is on files that use over 100G RAM and therefore need some longer time to shutdown. I can see that Pulze is starting the new job before the previous process is “killed” often leading to error messages the system is running low on RAM. I also think that because of the simultaneous running of the memory hungry processes, the previous process does not close completely. Wouldn’t it be possible to make pulze wait starting the next job, before the previous process is completely closed? When rendering from Max, everything works OK, but I also see that closing a memory hungry process could take 5-10 minutes; especially when there lots of Forest Pro instances with lots of proxies are being used.

RAM 128G, Max2020, VRay5

1 Like

Well, it seems this may be the result of running Max as administrator! So, no-go there!