I've looked into this a little bit, and the issue is with maxscript itself. The maxscript command used to delete layers doesn't trigger any callbacks that other scripts (i.e. the Outliner) can react to. So the Outliner can never be aware of layers being deleted. The integration of the Layer system with maxscript on the…
"Copying new files failed. Please see the Maxscript Listener (F11) for details." Then in the listener: "Installer exception: copyScriptFiles -- Runtime error: dotNet runtime exception: Access to the path 'C:\Program Files (x86)\Autodesk\3ds Max 2010\scripts\outliner\' is denied." Running the script through the menu worked…
I will look into this and see if there's something I can do to fix it. I don't think it's because the scene was saved without the Outliner. But I'm not sure what it could be. Does it happen with specific scenes, or 'at random' ? I know that it doesn't work with that layer cleaner script, and there's nothing I can do about…
Pjanssen: Use the userScripts folder instead of the scripts folder. you can access that folder in Maxscript using:pathConfig.GetDir #userScripts it behaves the same as the scripts folder but was added after Microsoft asked devs to avoid admin privileges and use the user folders for that kind of stuff. There are other user…
Thanks PJanssen, been waiting for the new release to come! :) Hope this 2 scripts can work side by side nicely in the future release. Btw, I contact one of the author of that layer cleaner script and he said probably Outliner use it's custom attributes, not the Max's build-in layer system, that's why it didn't detect the…
Hi Pjanssen, I found this script from ScriptSpot which automatically delete empty layers from the layer manager and it works. But the thing is, Outliner didn't detect the layer manager's layer list changes and I have to close and reopen Outliner for it to display the updated layer list in layer manager. I notice that from…
No changes to the UI in that session. It happens each time I install it. I installed it on 2 different machines and the same thing happened. Both machines had the script previously installed and I opted to download/update after the prompt came up that there was an updated version. If it helps I can uninstall it and try…