It’s not what you think.
I’ve had problems for a while now with Max not completely shutting down when closed, but hanging around as a background task. I’ve finally found a way to make sure that it exits completely and cleanly when you want it to. Just create a startup script with the following post shutdown callback…
callbacks.addScript #postSystemShutdown "((dotNetObject \"System.Diagnostics.Process\").GetCurrentProcess()).Kill()" id:#killMax_CBK
It’s been working great, and without any negative side effects as far as I can tell. The only thing you’d have to be careful of is making sure this doesn’t stomp on any other post system shutdown callbacks you may have (there aren’t any installed by default as far as I can see).
I would like to know, though, if anyone can think of any potential down sides to this.l
Not that I’m aware of, I think that you just need to test it out. I haven’t had the same problem so I can’t really test it for you.
Yeah, I’ve been using it for a couple of weeks now without any problems.
We were having a similar problem with max staying ‘open’ after close, but narrowed it down to a specific plugin, and no longer have the issue (after removing it from the ini).
I know at one point Cuneyt Ozdas Color Correct plugin had that problem, but not sure if that was ever resolved or if that is the plugin in question.
-Eric
How’s it going Ian?
Yeah, I’ve found there multiple things that can cause Max to hang around. In my case it’s using ‘DialogMonitorOPS’, to auto-close certain windows on file open. And I don’t want to stop using it, hence the workaround.
Hey m8! Things are going… I’m up north again… In Vancouver now… will have to make a trip down and say hi some time!
Thx for the infos…good to know there are multiple reasons for max not to close.
Working great here! Consider yourself one step closer to world domination
Thank you.
I’ve read the new beta color correct plugin for max 2010 will make this happen as well.
Just a little bit of info for future reference
-B
we’ve something similar… it’s just a dos bat with this…
taskkill /F /IM 3dsmax.exe
Doesn’t run everytime, but put a shortcut to it on your quickstart or start menu and you can get out of max lockups quickly too…
… or it will kill another version of max that is currently opened to the purpose
Before killing any process it’s better to ask this process for responding.
fn getNotRespondingProcesses name:"3dsmax" =
(
local processes = (dotnetclass "System.Diagnostics.Process").GetProcessesByName name
for p in processes where not p.Responding collect p
)
… after that it’s safe to kill them
My first attempt at this was to use hiddenDosCommand to run killMax.exe. The problem there was that it killed every instance of Max, and some artists like to run multiple instances at once. So looking for ones that aren’t responding is a good idea.