Please allow for a 'default view' to be specified and a UI improvement such that users are funneled towards opening in the default view rather than the selection of multiple views or the model tree. The overabundance of options leads to users turning 'on' too much content and being overwhelmed and disappointed. Examples: obstructions, volume clouds, etc are accidently turned 'on' instead of hidden when the correct view is not chosen.
quick thoughts on your questions:
1) project level
2) an interesting expansion but maybe not needed on the FIRST iteration
3) Admin for project level
4) an interesting expansion but maybe not needed on the FIRST iteration
The goal is to guide the less savvy users to a good default rather than overwhelming them with options & choices. The behavior we see is that they turn everything on out of doubt and then get buried in 'undesired' content. It would be good to have an 'unless-you-really-know-what-you-want' default that you are taken to.
happy to discuss. Matt and I can work with you on this.
We'd like to set up a discovery session on this item - things to think about:
1) Is this a default view for an individual user or at a project level
2) Do we want to have multiple default views depending on role
3) Is this an admin function or can individuals do it themselves
4) Would an individual default override a Role default if we did 2)