Showing posts with label Navigation. Show all posts
Showing posts with label Navigation. Show all posts

Saturday, March 13, 2021

Large Extents -Can't Navigate in a View and-or View Will Only Show Wireframe

I've written about Revit's fussiness regarding large extents numerous times over the years. In some of those posts I mentioned a related view issue. A view that refuses to show the model in anything other than wireframe is a symptom of the large extent issue.

I recently encountered a project that didn't have any DWG files to blame for it. Not only did the view not show according to graphic style settings it didn't allow navigation of any sort. The view was frozen. We could open or close it but nothing else. I noticed I could use a crossing selection window but then using Filter to focus my troubleshooting effort was still too coarse.

I've been meaning to mention how much I like IDEATE Explorer (IE). It has been very useful to examine projects and track down issues. It permits examining a model in ways that Revit can't. for example, I can select a category of elements or instances of each family/type within the category.

I use it routinely to check for excess DWG imports (resulting from exploded DWG content), workset assignment, reviewing warnings (more effectively than Revit's own), phase assignment/usage, content naming/usage and resolve line style usage (and more).

After using the crossing selection window in various parts of the view I realized some structural elements seemed quite far apart. Keep in mind the view was a white screen of nothing...imagining gazing toward Earth from Mars and trying to pick out where California is or my house. The Project Base Point and Survey Point didn't even show up in the view.

I started with trying to isolate where in this vast white space the structural element was but no matter what I tried I seemed to always select some structural framing.

Once I knew which category to hunt in I used IE to look at individual framing elements. I found a single framing (W Beam) was 2+ million feet long. I expected to find a family very far away, not one that was just very long. I realized that a Structural Framing schedule could have revealed this element too, if I knew which category and to look at Length. I did make a schedule just to see if I missed any other really long framing.

One Beam, one verrrrry looonnng beam killed any view it was visible in. 3D views are where we were confronted with the problem but other views whose extent permitted the beam's true extent to affect the view were also victimized. In the end we rolled the project back to just prior to the beam being added. 

The views didn't "recover" from the harm when the offending beam was deleted. I surmise other aspects of the model were altered by the extent of the beam, perhaps scope boxes, crop boundaries, a connected or joined element...not sure. That will remain a mystery.

May your troubleshooting be quick, effective and "trouble" free.

Thursday, July 31, 2014

Opening a View and it Appears Empty

I wrote THIS POST about Revit's behavior when you open a new view. There are times when you open a new view and Revit seems determined not to show you what is there. You get an empty view, or at least it looks empty, until you use Zoom to Fit.

It's been my observation that this happens when you are opening a new view with another view open that is cropped or at least looking at a very different portion of the model where there isn't anything to see in the new view. This happens because Revit is trying to focus on the same location in the new view, based on the location within the model you were already looking at (the view you were just using).

In a simple model this automatic zoom/focus works pretty well. As soon as we introduce linked files, scope boxes, cropped boundaries etc... it gets less reliable or helpful. Just something to consider next time you are greeted by an empty view. It might help to close down your current view first and use a simpler view or a schedule to start from instead. Then again, using Zoom to Fit isn't hard.

Wednesday, July 08, 2009

Dept. of Subtle - Pan/Zoom Insensitivity

This is really very subtle but with 2010 if you should happen to start with the really "dumb" template called "none" the pan/zoom functions don't work unless you have something in the view. This might makes sense except I wanted to turn on the new Project Base Point and Survey Point graphics and then Zoom to Fit. Revit won't Zoom to Fit or pan for that matter if they are visible when nothing else exists in the view.

If you add some text, a wall segment, an elevation view, a line...something pan/zoom come back to life. Apparently the graphic icons for these aren't "real enough" elements that pan/zoom recognize. Fortunately most people won't encounter this because they'll be working with a template that has "stuff" in it!

This "condition" is also true for earlier releases but 2010 now has something that you might actually want to use Zoom to Fit to see even if other elements don't exist yet.

As you were...