Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Yes, that is how i hide the user planes, but I want to be able to save the model with the planes hidden without having to create a new view representation.
Hi @mathias_bylow897L2. The design view representations are there to help prevent visual chaos at higher level assemblies & drawings by allowing us to define how we want those aspects of the design to look at that document level. Even parts have them, so that we can represent the same part in multiple different colors/finishes, and can show/hide bodies in multi-body designs, as well as to help us tidy up 'construction' stuff like the visibility of 2D & 3D sketches, work features, & UCSs. So, what I did that helped us out a lot was, edited all of our part templates and assembly templates, and added a custom (unlocked) view representation named something like "Default" or "DEFAULT", then activated it, then saved the template. That way every 'New' part, and every 'New' assembly already has a custom view representation, and it is already the active one. Then everything I do as far as changing color/appearance or visibility of stuff in those model files is 'recorded/saved' as I work, right from the start, without having to think about it.
The problem I hear about most often though, is folks wanting to implement 'top down' designing tactics after all the parts and sub assemblies already exist in a large assembly, which often does not work very well when it comes to view representations, because of how they work. Its almost like a pyramid that needs to be built from the bottom foundation up to the tip. The custom view representations should exist in the bottom most parts first. Then the custom view reps within the lowest level sub assemblies will record which view reps each of its component occurrences are set to, as well as its own internal visual elements. Then on up the ladder to the top/main assembly. When the visual details are defined at the part level (lower level), that makes everything easier at the higher levels. If we set all the visual details from the top assembly, then every other/new assembly we use those parts and lower level assemblies in will need to be 'managed' that same way, instead of just being set to their defaults.
