Outliner
-
Hello,
I am having major problems with Outliner. My model is around 50MB but does not seem to strain my workstation (most of the file size is from textures, not geometry). That is until I open Outliner.
- it takes approx. 2 minutes to open the Outliner window.
- if I hide or unhide a component thru Outliner, it takes nearly 4 minutes to perform the function.
- moving components within the component tree also takes a lot of time.
- it takes nearly 5 minutes to close the Outliner window.
Any suggestions would be appreciated. I organize almost exclusively with components and would really be efficient if Outliner worked smoothly!
thank you,
John
-
@3dgraffiti said:
Hello,
I am having major problems with Outliner. My model is around 50MB but does not seem to strain my workstation (most of the file size is from textures, not geometry). That is until I open Outliner.
- it takes approx. 2 minutes to open the Outliner window.
- if I hide or unhide a component thru Outliner, it takes nearly 4 minutes to perform the function.
- moving components within the component tree also takes a lot of time.
- it takes nearly 5 minutes to close the Outliner window.
Any suggestions would be appreciated. I organize almost exclusively with components and would really be efficient if Outliner worked smoothly!
thank you,
John
My guess is: you have too much groups and components (nested). This can happen quickly with tree-components where <leaf> components are nested in <branch> which are nested in.. etc If thats the case, you could try to explode several components to bring the total count down very quickly.
Second guess is: a plugin is having a fight with it (no idea which though).
Could you share a screendump of the <model info - statistics> ?
-
%(#4000FF)[*My guess is: you have too much groups and components (nested). This can happen quickly with tree-components where <leaf> components are nested in <branch> which are nested in.. etc If thats the case, you could try to explode several components to bring the total count down very quickly.
Second guess is: a plugin is having a fight with it (no idea which though).
Could you share a screendump of the <model info - statistics> ?*]
Thank you Kaas. If multi level nesting is an issue with performance, then that could very well be my problem. I do, in fact, have trees with nesting into the fourth level. I can clean that up and I bet you are right with your suggestion. I don't have many plug-ins, most of which I have used for years. I will try cleaning up my components to reduce nesting depths and I will let you know if that helps!
Stats:
edges 4630869
faces 2048718
component instances 121074
guides 48
guide points 2
groups 58621
component definitions 150
layers 6
materials 31Thank you again for your time!
-
@3dgraffiti said:
Stats:
edges 4630869
faces 2048718
component instances 121074
groups 58621
component definitions 150I think there is your problem: the outliner has to sort through 121.074 components + 58.621 groups. I can't imagine it has been build /optimized for those high numbers. No idea what to limit is though...
Advertisement