Tag Archives: View

Revit 2017 View Range Quirk

Leave a reply

The new features that we received as part of Revit 2017 for View Range were actually part of 2016 R2, with one exception.  In 2017 the factory gave us a 2 key shortcut (VR) to activate it.  This is, maybe I should say was, one of my favorite new little features for this release.  However I found a bug when using the shortcut instead of accessing it through the properties dialog.  If you use VR to access the dialog you Must use apply dialog for it to work clicking OK wont accept changes.  Aaron Maller and I also discovered that you can access the view range via VR even when there is a view template assigned.  Simply applying the view template to the view wont correct the problem you must make a change in the view template and it will then overwrite the settings.  These quirks forced me to no longer say this is one of my favorite small enhancements.

Revit Basics – View Range

Leave a reply

Over the years I have had the question come up on why a level can’t be used as an underlay or be selected for view depth or bottom while in the View Range command.  ONLY levels with a view associated to them can be used in these situations.  If a level needs be generated and used for one of these options just add a plan view, so it can be used.

Level_NoView

Scope Box Quirk

Leave a reply

When placing scope boxes they will come up with a default name Scope Box ??, where the question marks are a number.  If you rename a scope box to say Area 01 then use the scope box command to place a new one, it will come up with the name Scope Box ??.  However if you copy a scope box it will have a value one higher than the previous, so a copy of Area 1 will be Area 2, the same is true if the name was Area A it will be Area B.  So if there are going to be a multitude of scope boxes on the project think about renaming the first one and copying it around, easier to adjust shape than rename, or at least that is how I do it.

View Reference

Leave a reply

One of the new features of Revit 2013 was the added capabilities of the View Reference command.  In the past this command was only available in views that were either a dependent or parent view.  In 2013 this has been expanded to work in most view types, it doesn’t matter if they are dependent or not.  This feature is something that a lot of my clients are starting to take advantage of by creating different view reference families.

By creating different types they can be used in different ways.  The one that looks like a bubble can be used on legend views to call out details of legend components, the one for text can be placed near a text box so that the proper detail can be called out.  I just wish these could be placed in schedules, on sheets, or heck in every view type.I a

I also noticed a quirk that has been fixed in 2013 not sure if it is because of this new feature or not.  When creating a new section, call-out or elevation and using the Reference Other View feature, Revit no longer keeps the drop down list active when using the mouse scroll wheel.  Therefore Revit doesn’t scroll through the list of view options, instead it allows a user to zoom in the view.  Nice added little fix, I always love these little things.

Plan View Types Part 3

Leave a reply

I have posted a few times now about the Revit 2013 new Plan View Types.  I really like this feature, however I found another nuance that everyone should be aware of and hopefully will change with future service packs or releases. 

At first I loved the fact that when levels were created it allowed the Plan Views to all have the same name if they were under different view types.  I still like this, however it seems to be causing issues.

Notice in the image below I have Level 1 and Level 2 views in each plan view type. This is great now if you rename a level or view the capability to rename all of them still exist.

 

Now simply move a view from one category to another. 

 

If that view name already exists then it doesn’t add another number at the end, it simply add up to the next available number. Which seems totally non_Revit like in my opinion why not a (2) at the end?

 I wanted to make everyone aware of this issue. I have already been discussing this with clients to see how they want to impliment and deal with this issue.

Small nuance that could be frustrating however not devastating to a project.  If you want to apply a view template via another view and all of the plan views have the same name how do you choose?  As you can see there are numerous Level 1 views.