[Closed] Kill Max

Kill’em All…

I mean “There can be only one.”…That’s my motto… running multi instances of max can confuse the autobak… which isn’t an issue for big shops I guess, but can be a half day loser for me…

Yeah, my technique is definitely brute, but I like it that way… Some people think running anti virus is a good use of clock cycles too…

If that works for you, go for it. But since I’m maintaining tools for a whole group of artists, I’d be lynched if every time one of them close one copy of Max, all of them got closed.

Hummm… never thought of shutting down ALL of them… I just thought of pairing this with pstools. One could REALLY… kill ALL max ! ! !

I’m down to supporting only 5 artists and having to do more production work…

I’m a maxscript newbie. can inform me how compile the script? Do I simply copy that code above into a text document and rename the file extension into .ms?

Thanks

If you are using VRay, stop the VRayspawner service (and any other Autodesk / Max related services for that matter). By doing that the process will probably stop on it’s own. If it doesn’t, kill it again and see what happens.

Executables popping back up right after you kill them are 9 out of ten times related to some other service / process that’s still running.

Hope this helps

Thanks!
a few of the guys at work noticed our 3dsmax.exe process hanging around a little too long
good stuff

My case is this:

I am running a bunch of renders on 3dsmax 2011. I also have 2012 installed – so the renders are going through the newer backburner – so maybe that is the culprit.

At the end of each completed render job the queue hangs. I come and see that the other jobs did not start after the completed job, and that my task manage shows about 10 open 3dsmax.exe processes that do nothing. The other jobs in backburner report that they failed due to a timeout. (makes sense if there are 10 open max instances).

I end up needing to babysit my render queue and once every job is complete – kill the 10 instances of max and restart the remaining jobs.

I tried removing the Color Correct plugin – still does this problem.
I tried the script mentioned in this thread – in the startup folder – still does this problem.

I am rendering with Mental Ray so I don’t think it’s Vray related.

I have no idea why 3dsmax just hangs after a completed job – or – why so many open up after it. Maybe it doesn’t hang but backburner gives the next job to many instances of Max?! I have no idea. There are more instances of 3dsmax.exe than my jobs so I’m not sure why that is. Maybe from the numerous attempts for every job…

Anyone else experienced this behaviour?

I have the same problem here. I’ll investigate next week waht could be the problem, because it doesn’t happen on every render server. I’ll compare plugin directories and try to narrow down the list of suspicious plugins

In the meantime, if you found an answer to the specific “killmax” problem of process preventing backburner from doing his job, I’m intrested ! Even if it’s a workaround.