Outliner
Version:
2.1.5
Date Updated:
09/13/2012 The Outliner 2.0 is a fast and easy to use scene management tool. It has a wide range of features, including selecting, hiding, freezing, linking and grouping objects in the "Hierarchy Mode". In the "Layer Mode" you can organize your scene by dragging&dropping objects from one layer to the other. What's more, the Outliner offers support for nested layers, to manage scenes more efficiently. The interface is nimble enough to keep it open constantly.
Additional Info:
Compared to the previous version (1.6.1), there are many improvements. Most notable among them are: hugely increased performance, improved stability, nested layer support and many small tweaks to improve the ease of use. For a list of all changes, click here
Version Requirement:
3ds Max 2010
Other Software Required:
.NET 3.5 Framework
Comments
Noted. Will be fixed in 2.1
Noted. Will be fixed in 2.1 beta4 or 2.1, whichever comes first.
Thanks!
using now v2.1 beta3, nice
using now v2.1 beta3, nice work man.
now a little new problem, if you have the main ui buttons and the search bar set on top, they get over each other.
Ok, I spent some time to
Ok, I spent some time to implement this and made a macroscript that does the trick. It will be part of the next workflow tools release that will coincide with the Outliner 2.1.
It should be tested a bit more thoroughly though, so if you (leejk) want to help with that, drop me a line.
I will look into that. Thanks
I will look into that. Thanks for letting me know!
That sounds like an
That sounds like an interesting little tool to add to the workflow tools set.
Adding custom items to the contextmenu is not a trivial thing to implement in the current architecture. I'll have a think about it though. It could be somewhat related to this perhaps: http://script.threesixty.nl/outliner/index.php/blog/2011/03/context-menu
Feature Request
For people who work with imported CAD data, optimizing the hierarchy is key for performance. I think a useful tool would be so that when you right click on a top level dummy or mesh node, you would have the option to collapse all of it's children into a single mesh object. The new mesh object would retain the selected node's name and place in the hierarchy. I think this would be a very productive addition to this already great script!
EDIT: After thinking about it some more, perhaps the better solution would be for the allowance of assigning custom commands to run from Outliner's right click menu. Then a custom MaxScript command could be assigned to the context menu.
Another bug
I stubled upon another bug. One of my top level layers keeps expanding when I make an operation on another layer be it move objects to it or drop another layer in it. I restarted Max and when I loaded the scene a message popped up saying:
--No "getPropNames" function for undefined
I clicked "OK" on this dialog and tried to start the script again another message popped up saying:
-- Unknown property :"expandedNodeHandles" in dotNetControl:tree:(null)
By the way, I am using the latest Beta version (Outliner 2.1 beta3)
EDIT: Ha! I uninstalled the beta and installed back the official release and the problems went away! So it seems it's something to with the beta versions.
"A few questions: -Which
"A few questions: -Which mode
A few questions:
-Which mode does this occur in? I assume layer mode?
-Are you moving both the group and the contents to a new layer?
-Do you have "hide group contents in layer mode" turned on or off?
The expected behavior is as follows:
With "hide group contents in layer mode" off, moving a group node only moves the group head. The visibility of the group head does not affect the visibility of the group contents. This is standard max behavior.
With "hide group contents in layer mode" on, moving a group node moves both the group head and the contents to the new layer. As a result, the visibility setting of the new layer will affect all objects in the group."
With me it's the opposite - With "hide group contents in layer mode" on, when I move a group to a new layer the layer which I moved the group from seems empty but it isn't. The layer which I moved the groups to shows the groups I just moved but when I hide them (or the whole layer) nothing happens. It seems like only the group heads have been moved which is not what I expect. When I move grouped objects between layers I expect them to contain the objects residing in the groups. I think that's the logical it should function.
version 2.1 beta3
For those following the beta updates: I've uploaded a new beta version: 2.1 beta3.
It contains many small fixes and enhancements. For more info, see: http://script.threesixty.nl/outliner/index.php/changelog
A few questions: -Which mode
A few questions:
-Which mode does this occur in? I assume layer mode?
-Are you moving both the group and the contents to a new layer?
-Do you have "hide group contents in layer mode" turned on or off?
The expected behavior is as follows:
With "hide group contents in layer mode" off, moving a group node only moves the group head. The visibility of the group head does not affect the visibility of the group contents. This is standard max behavior.
With "hide group contents in layer mode" on, moving a group node moves both the group head and the contents to the new layer. As a result, the visibility setting of the new layer will affect all objects in the group.