Isolation Levels
Date Updated:
05/15/2014 
Create nested isolations, go back and forth between them. Hope it helps.
Additional Info:
installation:
- close all open 3ds Max instances
- remove old versions of this script
- copy scriptfile "isolation_levels.ms" into 3ds Max startup folder (example: "C:\Program Files\Autodesk\3ds Max 2012\Scripts\Startup")
- copy imagefiles "IsoLevels1_16i.bmp, ..." into 3ds Max usericons folder (example: "C:\Users\Username\AppData\Local\Autodesk\3dsMax\2012 - 64bit\enu\UI\usericons")
- start 3ds Max and open menu Customize > Customize User Interface > Toolbars (Category: # Scripts)
- create a new toolbar and drag and drop the commands "Isolation Levels - Backward, ... Forward, ... New Iso, ... Exit Iso" to it
- restart 3ds Max, enjoy
features:
- works as fast as the standard isolate
- number of isolations: infinite
- unlike the standard Isolation Mode, this script hides Xrefs while rendering in isolation
- hint: I find it very useful to put this script on the Alt+Q button and replace the old isolation function of 3ds max
- you can find the current isolation level in the title of the 3ds Max window, behind the scenename
script at work (old user interface, script has no extra window anymore):

to do:
- isolation state should be stored in maxfile
Version Requirement:
tested with 3ds Max 2012 | Attachment | Size |
|---|---|
| isolation_levels_12.ms | 9.07 KB |
| isolation_levels_23.zip | 3.55 KB |

Comments
I updated the script.
I updated the script. Installation is now different, please read in description. I hope to find some more time today to test this version and also to add the ability to store the isostate in the scene.
Thanks a lot!
I agree with headd on both accounts, though navigating through the levels with the dialog works fine.
Initially hidden objects stay hidden, now. :)
There seems to be a bug if the user deletes meshes:
-- Error occurred in shutdownScript(); filename: Z:\software\3dsmax\maxplugs_new\isolation_levels_08.ms; position: 651; line: 34
-- Frame:
>> MAXScript dotNet event handler Exception:
-- Runtime error: Attempt to access deleted scene object <<
Thx for the great work!
I will try to fix this. For
I will try to fix this. For now just click on the button to prevent the error.
Bug
There is a bug if i run the script(Alt+Q) when there's a IsoLevels window already opened. It opens a new window and messes up the original one ( the isolation levels won't work, error in attachment).
Instead, if you hit the shortcut(Alt+Q) it should switch to the next isolation level or create a new one, like you'd hit the --> button.
What do you think?
Thanks
GREAT!
Hidden objects now stay hidden, good work and thanks again :)
I tried to fix bugs and get
I tried to fix bugs and get rid of some points on the todo-list with the version 8. Hope it works, I didnt had the time to test it yet. Now it shouldnt unhide all objects when the dialog is closed and it should always stay on top. Thanks to barigazy for the code!
I agree with Herr Bert, the
I agree with Herr Bert, the fact that it unhides objects hidden before running the script is tricky, especially if you work on someone else's max file and you don't know what was visible or not.
...
Suggestions for 1st and 3rd "to do"
#1 With .net form U can stay Always "On the Top" :)
#3 Why not use CA to store last state of the scene and then add CA to "rootnode"
bga
I know what you mean, I gotta
I know what you mean, I gotta fix that.
Keep initially hidden objects hidden
This is a really great tool! Thank you!
However there is bug that makes it almost useless to me:
On closing the tool or going up to the highest level IL unhides ALL objects, even if they were hidden before using the tool.