New updates are available for both Revit 2015 and 2016 now. The latest for 2015 is Update Release 13 and we're up to Update Release 3 for 2016. Hopefully the Autodesk Application Manager let you know already, it did for me this time. Visit your Autodesk Account page to download them if not.
These are the three related release note files that The Revit Clinic shared the other day.
Revit 2015 Update Release 13 readme and release notes
Revit 2015 Update Release 13 for R2 readme and release notes
Revit 2016 Release 2 Update 3 readme and release notes
Showing posts with label Revit 2016 R2. Show all posts
Showing posts with label Revit 2016 R2. Show all posts
Tuesday, March 15, 2016
Tuesday, November 10, 2015
Revit 2016 R2 - Changes to Underlay
They've reconfigured the Properties Palette and changed how they describe and provide access to the Underlay concept.
As you can see above, the Underlay concept now has its own Group Header in the Properties palette. They've renamed the Underlay parameter itself to Range: Base Level. The new Range: Top Level is a read-only value that just reports the next level above the Base Level. That can be helpful when it isn't the one you expected, for example when there is an intermediate level for a stage .
Keep in mind that if a view is created for a level we can't prevent that level (like Stage above) from being the next one, the one that appears in Range: Top Level. I think it could be better if a Level's Building Story parameter could influence this condition so a view could exist for the level but not be factored into the Underlay's display process, allowing it to skip past or ignore the Stage level.
The Underlay Orientation parameter kept its name but the words used to describe its choices are now Look up and Look down. The plainer language seems to help people understand what Underlay is really doing. At the very least Look up is more accurate than implying it is really generating what we have learned is meant by Reflected Ceiling Plan.
Also very worthy of a mention is that new plan views have their Underlay - Range: Base Level assigned to None instead of the Level Below like in earlier versions.
Hmm, writing that last section, it occurs to me...this feature used to just be called Underlay, a parameter AND concept on its own with a second related Underlay Orientation parameter. Now we have a concept of Underlay with three parameters.
Experienced users will now confuse new users by asking them, "What's the view's Underlay assigned to?" or telling them, "You need to change your Underlay setting." ...ah progress...
Oh, and Hat Tip to Niklas Strannefors, an Autodesk Application Engineer in Sweden, for prompting me to write about this subtle change.
As you can see above, the Underlay concept now has its own Group Header in the Properties palette. They've renamed the Underlay parameter itself to Range: Base Level. The new Range: Top Level is a read-only value that just reports the next level above the Base Level. That can be helpful when it isn't the one you expected, for example when there is an intermediate level for a stage .
Keep in mind that if a view is created for a level we can't prevent that level (like Stage above) from being the next one, the one that appears in Range: Top Level. I think it could be better if a Level's Building Story parameter could influence this condition so a view could exist for the level but not be factored into the Underlay's display process, allowing it to skip past or ignore the Stage level.
The Underlay Orientation parameter kept its name but the words used to describe its choices are now Look up and Look down. The plainer language seems to help people understand what Underlay is really doing. At the very least Look up is more accurate than implying it is really generating what we have learned is meant by Reflected Ceiling Plan.
Also very worthy of a mention is that new plan views have their Underlay - Range: Base Level assigned to None instead of the Level Below like in earlier versions.
Hmm, writing that last section, it occurs to me...this feature used to just be called Underlay, a parameter AND concept on its own with a second related Underlay Orientation parameter. Now we have a concept of Underlay with three parameters.
Experienced users will now confuse new users by asking them, "What's the view's Underlay assigned to?" or telling them, "You need to change your Underlay setting." ...ah progress...
Oh, and Hat Tip to Niklas Strannefors, an Autodesk Application Engineer in Sweden, for prompting me to write about this subtle change.
Thursday, November 05, 2015
Revit 2016 R2 - Detach from Central Filename
When you use the Detach from Central option Revit will append the word _detached to the filename if you decide to save the file.
You'll also find that the Titlebar shows the original file name with _detached appended to it instead of the blank description it displayed in the past.
How's that for subtle? Thanks to Jean-Marc for the push to post this.
You'll also find that the Titlebar shows the original file name with _detached appended to it instead of the blank description it displayed in the past.
How's that for subtle? Thanks to Jean-Marc for the push to post this.
Thursday, October 29, 2015
Revit 2016 R2 - New Family Types Dialog Format
My friend Rolly sent me a screen capture of the new Family Types dialog. It's been revised to use similar buttons as some of the other dialogs, like the Filters and View Templates dialog for example.
It is slimmer now. I liked the larger buttons with words personally. I struggle (a little) with the tiny pictures (see what I did there) on these icon only buttons. At least I can rely on muscle memory to click on them after awhile. It will be helpful require less screen real estate for the interface and allow for more practical editing of those really long pesky conditional formulas...if dabble with those.
It seems I have a growing number of friends who are concerned about my lack of new blog posts :) Thanks Rolly! It's so much easier when you send me pichurs :)
It is slimmer now. I liked the larger buttons with words personally. I struggle (a little) with the tiny pictures (see what I did there) on these icon only buttons. At least I can rely on muscle memory to click on them after awhile. It will be helpful require less screen real estate for the interface and allow for more practical editing of those really long pesky conditional formulas...if dabble with those.
It seems I have a growing number of friends who are concerned about my lack of new blog posts :) Thanks Rolly! It's so much easier when you send me pichurs :)
Friday, October 23, 2015
Revit 2016 R2 - Positioning by Auto - Project Base Point to Project Base Point
This is an interesting development for reconciling the misalignment of models. This gives us the option of linking a RVT model according to the location of its Project Base Point (PBP) and aligning it with our own.
Let's imagine a scenario where our structural engineer decides to mock-up a preliminary model but does so without the benefit of having the architectural model linked in yet. This new feature allows the engineer to either move the PBP un-clipped (see warning below) to an agreed upon grid intersection or to start by placing their grids at the default PBP location in their model.
All I have to do to get their model to align with my model properly now is make sure I move my PBP un-clipped (again see warning below) to our equivalent grid location or be grateful I was lucky to have guessed that we'd start our grids at the same location to start with. If I didn't guess correctly then moving it un-clipped puts it in the correct location and the link lines up nicely.
Being able to move the PBP un-clipped is helpful for Revit to Revit alignment. It DOES NOT address exporting to DWG however (nor appending to Navisworks). If each model is exported using Coordinate System Basis: Project Internal they will not line up with one another because the model's file origin is not altered. If each trade is careful to start modeling the agreed upon grid intersection at their templates's default PBP location (not moved at all) then they'll line up when their exported files are opened in AutoCAD or Navisworks.
I'm not sure we can rely on that if we can't count on them waiting for our model to use as a linked reference first? Still it is an interesting development. Hopefully it doesn't just contribute to the existing confusion regarding linked RVT file positioning.
My recommendations?
Let's imagine a scenario where our structural engineer decides to mock-up a preliminary model but does so without the benefit of having the architectural model linked in yet. This new feature allows the engineer to either move the PBP un-clipped (see warning below) to an agreed upon grid intersection or to start by placing their grids at the default PBP location in their model.
All I have to do to get their model to align with my model properly now is make sure I move my PBP un-clipped (again see warning below) to our equivalent grid location or be grateful I was lucky to have guessed that we'd start our grids at the same location to start with. If I didn't guess correctly then moving it un-clipped puts it in the correct location and the link lines up nicely.
Being able to move the PBP un-clipped is helpful for Revit to Revit alignment. It DOES NOT address exporting to DWG however (nor appending to Navisworks). If each model is exported using Coordinate System Basis: Project Internal they will not line up with one another because the model's file origin is not altered. If each trade is careful to start modeling the agreed upon grid intersection at their templates's default PBP location (not moved at all) then they'll line up when their exported files are opened in AutoCAD or Navisworks.
I'm not sure we can rely on that if we can't count on them waiting for our model to use as a linked reference first? Still it is an interesting development. Hopefully it doesn't just contribute to the existing confusion regarding linked RVT file positioning.
My recommendations?
- Make sure all trades agree to begin their work referencing their own PBP with the same understanding. For example, agree in advance that the bottom left grid intersection shall occur at the PBP location (like shown in my images). This will ensure that exported data will have the same file origin.
- Don't move the PBP un-clipped to reconcile the PBP location IF you want to be able to export using Project Internal.
- Only move the PBP un-clipped if you will rely on Shared Coordinates to deal with external model alignment in other applications.
Thursday, October 22, 2015
Revit 2016 R2 is Available and Update Release 10 for Revit 2015
When I wrote about Revit Sunrise earlier I hinted that we might see a repeat of last year when Revit Sundial was followed by Revit 2015 R2. That's come true today.
You can CHECK OUT some VIDEOS about what is new in this subscription customer only release.
These are the features they've chosen to provide videos for:
You can CHECK OUT some VIDEOS about what is new in this subscription customer only release.
These are the features they've chosen to provide videos for:
- Draw Visible Elements Only (performance)
- Global Parameters
- Family Element Visibility Setting (Family Editor)
- Thermal Zoning (Analysis)
- Enhanced Revit Links
- Cancel Multi Sheet Print or Export
- View Filter UI Improvements
- Revision Enhancement
- Isolate Solids/Voids with Filter Tool (Family Editor)
- Per User RVT Link Unload
- Improved Project Browser
- Name Reference Plane
- Autodesk Raytracer
- Railing Preview
- View Underlay and Orientation Improvements (descriptive language)
- Enabled Copy Paste in Perspective Views
- Choice to Select Wall Join Type (behavior) during Wall Creation
- Fabrication Part Modeling Enhancement
- Electrical Design Enhancements
- Mechanical Design Enhancements
Subscribe to:
Posts (Atom)