![]() Manage worksets and maintain the project standards for Workset use. The object resides on a workset that is not visible in the view, that is not loaded in a linked file, that is not visible in a linked file.The object resides on a workset that is not loaded within the project.Why does it need an explanation, because it’s odd and un-editable? Is the view “Discipline” set correctly?Ĭlick here for Autodesk’s description of the tool and view property, Discipline.“Is the element within the view range or is the view hiding the element and its category?” The View Range is important because not only does this range control and limit what is seen, but also what is selectable. There should be minimal scope boxes in the project. Many times, people use Scope Boxes to control the cop boundary of the view. It extends or limits the view range in a polygonal boundary. This changes the ability to see or edit the view’s crop.Ī plan region is used in addition to the view crop. The object is constrained to a scope box that is not visible in the view.The view’s far clip depth is not sufficient to show the object.The object is outside the view’s view range.Is the missing element outside the scope of the view.This is discussed in detail in our Revit Family Best Practices class. ![]() The object is set to not be visible at the category’s detail levelĬreate Revit families with fine detail elements on different subcategories and with different visibility graphic overrides.įor example, door handles should not be visible in plan and only visible in elevation when the view is set to fine.The object is a family and none of its geometry is set to be visible in the view type.Is the view’s detail level set correctly? Some families have elements that are controlled by subcategories and are set not to show at a coarse level of detail.Overriding these properties in a view is counterproductive. The Object Styles dialog is the best way to organize elements and there subcategories. There is a category override in the view.The object’s category or subcategory is hidden in the view.Filters can change color, line weight, and visibility. Elements that match these criteria are selected or controlled by the property of the filter. Is there a filter applied to the view that is causing the element to be hidden?įilters allow the conditional statements to query the model elements in the view.In a training class, I always say, “If you don’t like something about the view, it’s either the view property or the element property that’s causing the issue.” Is the view range set correctly to see the particular element?.It also takes more system memory to manage element visibility overrides. It’s most common and easier to troubleshoot. Element overrides are harder to troubleshoot and use more system resources. Refrain from hiding elements in the view and stick with hiding the category. They check the Visibility Graphic Override dialog and the element’s category is on. Element overrides can be confusing to some. ![]() Both hidden elements and hidden categories will be red while using this tool. Try using the “Reveal Hidden Elements” tool in the view control bar.
0 Comments
Leave a Reply. |