Following on closely from the release of Revit 2022, you may have seen updates to the previous 3 releases of Revit have been recently released.

Here are some links to get you started:

Revit 2021

Software embedded in the update executable:
Revit 2021 – version 21.1.30.74
Revit Unit Schemas 2021 – version 21.1.30.74
Steel Connections Content for Dynamo 2021 – version 2.6
Cloud Models for Revit 2021 – version 21.1.30.74
Generative Design for Revit 2021 – version 21.11.1.0
Personal Accelerator for Revit – version 22.0.1.0
OpenStudio – version 0.1.17

Issues Resolved

DirectShape Elements
Fixed an issue that could produce very large journal files during upgrade of models with many DirectShapes.
Improved upgrade of some families created in Revit 2018 or earlier to preserve some geometry created via import operations or API.
Duct/Pipe Display
Fixed an issue that incorrectly filtered out detail lines and masking regions when they conflicted with model lines at a specific detail level.
Electrical Circuits
Fixed an issue that the load can’t be propagated properly through a single phase transformer.
Electrical Panel Schedule
Fixed an issue where the Phase doesn’t display correctly when assigning a spare in single phase panel.
Energy Model
Fixed an issue that caused interior spaces to be excluded from an energy analysis.
Export DWG/DXF
Fixed an issue where small objects would not export correctly to DWG at large drawing scales.
Licensing
Fixed an issue where user license expired unexpectedly causing Revit to fall into a 10 minute grace period, after which Revit is automatically terminated.
Materials
Fixed an issue where the Material browser would load thumbnails unnecessarily.
Fixed an issue that material texture not found after moving textures to a new assigned render path folder.
MEP Fabrication
Fixed an issue that caused costing data to be lost after exporting parts to a .maj file.
Fixed an issue with kerf values resetting to 0 after importing a job file.
Open/Save
Fixed data corruption message displayed in error when opening a model.
Properties Dialog
Improved performance when using the type selector.
Reinforcement
Fixed an issue where the concrete cover of a model in place element cut by another element is reset after finish editing without any changes.
Revit Cloud Model (workshared)
Fixed issue that mirroring fails if a new workset has been added to the model but has not been saved to the cloud.
Fixed an issue where the Activity Indicator would show that the model is not being actively synchronized if the synchronize time is longer than 5 minutes.
Steel Connections
Fixed an issue that caused steel connections to become invalid after performing a Roombook addin calculation.
Improved performance for worksharing synchronization actions when the central model has link models attached that contain or have contained steel fabrication elements such as steel connections.
Units
Corrected symbols for Russian translated units.

Important Notes

Content
Updated Content for Revit 2021.1 is not included in the patch deliverable and is provided on the Autodesk Knowledge Network, link.
Update installation may fail if the original Content path location is not accessible.
Install
After applying the hotfix, Generative Design command may cause a “RestDynamoCore.exe – This application could not be started” errors. A reboot of the system should resolve the errors.
In some scenarios the original RVT.msi may be required to install the hotfix. If you are prompted for to specify the RVT.msi version and do not have access to the original installation files you may download the RVT.msi as follows. There are several unique Revit 2021 full product installers which have been released and each includes a unique version of the RVT.msi file. The following is the simplest way to identify which full product installer was used to install Revit 2021 on a workstation:
1. Open the Windows Registry Editor.
2. Browse to and select the HKEY_LOCAL_MACHINESOFTWAREAutodeskUPI2{7346B4A0-2100-0510-0000-705C0D862004} registry key in the left column.
3. In the right column, make note of the BuildNumber value.

If the BuildNumber is 21.0.0.383, then the installation used the initial Revit 2021 full product installer and the required RVT.msi is available here: link

If the BuildNumber is 21.1.1.109, then the installation used the Revit 2021.1 full product installer and the required RVT.msi is available here: link

If the BuildNumber is 21.1.11.27, then the installation used the Revit 2021.1.1 full product installer and the required RVT.msi is available here: link

Uninstall
Revit 2021 updates can be uninstalled to revert Autodesk Revit 2021 to its pre-update state.
Uninstalling this update after being applied to a Revit 2021.1 installation may require the original installation media to complete without error.
Uninstalling this update after being applied to a Revit 2021.1 installation may cause the Revit version displayed in Windows>Add/Remove Programs to be blank.

Revit 2020.2.4

Software embedded in the update executable:

  • Revit 2020 – version 20.2.40.65
  • Autodesk Cloud Models for Revit 2020 – version 20.2.40.65
  • Personal Accelerator for Revit – version 21.0.11.0
  • OpenStudio – version 0.1.9

Issues Resolved

DirectShape Elements

  • Fixed an issue that could produce very large journal files during upgrade of models with many DirectShapes.
  • Improved upgrade of some families created in Revit 2018 or earlier to preserve some geometry created via import operations or API.

Duct/Pipe Display

  • Fixed an issue that incorrectly filtered out detail lines and masking regions when they conflicted with model lines at a specific detail level.

Electrical Cable Tray and Conduit

  • Fixed an issue that caused cable tray fittings to not display in a plan view with annotation scale turned on.

Export DWG/DXF

  • Fixed an issue where small objects would not export correctly to DWG at large drawing scales.

Help

  • Fixed the issue that F1 keys do not display the correct help page in browser.

IFC

  • Fixed an issue that caused steel elements with fabrication to change GUID on IFC export.

Materials

  • Fixed an issue that material texture not found after moving textures to a new assigned render path folder.

MEP Fabrication

  • Fixed an issue that caused costing data to be lost after exporting parts to a .maj file.

Properties Dialog

  • Improved performance when using the type selector.

Revit Cloud Model (workshared)

  • Fixed an issue which could cause BIM 360 links to fail to load when the user had their permissions on the linked model forcibly relinquished.
  • Fixed an issue where the Activity Indicator would show that the model is not being actively synchronized if the synchronize time is longer than 5 minutes.

Steel Connections

  • Fixed an issue that caused steel connections to become invalid after performing a Roombook addin calculation.
  • Improved time performance for worksharing synchronization actions when the central model has link models attached that contain or have contained steel fabrication elements such as steel connections.

Tags

  • Improved the stability when selecting material tags in 3D, section, or elevation views when there is a linked topographic file.

Important Notes
Dynamo for Revit

  • In some cases Dynamo will not be visible within the Manage tab after 2020.2.4 Hotfix is applied. To restore Dynamo, replace DynamoRevitDS.sig and DynamoRevitVersionSelector.sig in the following location: C:Program FilesAutodeskRevit 2020AddinsDynamoForRevitRevit .

Content

  • Updated Content for Revit 2020.2 is not included in the patch deliverable and is provided on the Autodesk Knowledge Network, use this link.

Licensing

  • For Vault 2020 users, after the 2020.2.1 Hotfix is applied replace AdskLicensingSK_2.dll in Revit 2020 install location: C:Program FilesAutodeskRevit 2020 .

Uninstall

  • Revit updates cannot be uninstalled to revert Autodesk Revit 2020 to its pre-update state. If you need to remove the update, please uninstall Autodesk Revit 2020 and then reinstall it.

Revit 2019

Resolved Issues

    • Improved upgrade of some families created in Revit 2018 or earlier to preserve some geometry created via import operations or API.
    • Fixed the issue that F1 keys do not display the correct help page in browser.
    • Fixed an issue where a Revit Cloud Worksharing link path could incorrectly resolve to the Collaboration Cache directory.
    • Fixed an issue that caused steel elements with fabrication to change GUID on IFC export.
    • Improved stability for Revit Server models and Revit cloud models with new extensible storage schemas.
    • Fixed an issue which could cause BIM 360 links to fail to load when the user had their permissions on the linked model forcibly relinquished.
    • Improved performance when using the type selector.
    • Fixed an issue where small objects would not export correctly to DWG at large drawing scales.

The IFC for Revit addins that improve IFC import and export functionality are maintained at this GitHub site for versions newer than Revit 2018. In the past 2 weeks, updates have been release for all current Revit versions, and I have collected the direct links for you below. Note that the GitHub versions can be more up-to-date and current than the ones listed on the App Store.

If you want to check which version you currently have, you could use Start – Add or Remove Programs to do that without opening Revit:

checking Revit version in Add or Remove Programs
checking Revit version in Add or Remove Programs

If you are inside a Revit model, you can use File – Export – IFC and check the version in the dialog box header:

If you are looking for Revit 2018 and older versions of the IFC for Revit addins, check out the SourceForge site instead.

The update for Revit 2019 was particularly significant. Release notes copied below:

General:

  • This version marks a significant milestone for IFC Exporter as it is now IFC4 Reference View certified (for Architectural Export and Structural Export Exchange Requirements)

New Features/Improvements:

  • Export of Area can now be assigned to IfcSpatialZone in addition to the default IfcSpace using IfcExportAs
  • Support exporting IfcGroup using ZoneGroupName parameter
  • Improved heuristic for assigning color to polygonal face sets
  • Improved handling to support for direct export of polygonal face geometry in IFC4
  • Support for IfcShapeAspect in other objects that have part geometries
  • Improved handling of Complex Property in the PropertySet definition
  • General improvements to support IFC4 based geo-referencing information with addition UI in export, and integration to the information found inside Revit file (usually comes from AutoCAD or Civil3D)
  • Reorganize the location for Exchange Requirement setting in the header of IFC File to be less hidden (now located right after the IFC version in export option UI)
  • Updates shared parameter definitions and Property set definitions based on the latest IFC4 (4.4.0.2.2) specifications
  • Support allowing a predefined type for standard walls on export
  • General improvements dealing with objects with many holes
  • Added basic support to export Area as IfcSpatialZone entity

Bug Fixes:

Export bug fixes:

  • Fixed error during export for a specific object that became invalid in the export process with “Store the IFC GUID in an element after export” option
  • User defined property set can now be exported for IfcGeographiElement
  • Fixed export failure when ZoneClassificationName is set to Room for exporting IfcZone
  • Corrected GrossVolume quantity information with the correct unit
  • Fixed exporting issue for a Ceiling containing Arc geometry
  • Fixed issue with duplicate steel connection geometries or missing connection
  • Fixed issue with IFC export – steel connection steel connection elements missing or wrongly exported
  • Fixed issue on missing ceiling geometries in IFC4 RV export mode
  • Fixed issue on objects with Parts that is below the first (lowest) level
  • Fixed issue with export Roof in some cases
  • Fixed crash issue if the “Rasters” are set to be exported to “IFCGrid”
  • Fixed issue with IFC option “export links as separate models” causes wrong object placement
  • Improved export Parts functionality
  • Fixed issue that IFC Version doesn’t update when changing the “In-Session setup”
  • Fixed IsExternal calculation on element types to correctly determine value
  • New shared parameter assigned to Curtain walls is now exported when exporting from Revit to Navisworks
  • Update category mapping to deal with IfcSpaceTypes and IfcOpeningTypes
  • Fixed issue with incorrect slab thickness when Opening IFC in Revit
  • Fixed some issues on export with different coordinate base
  • Fixed some issues on exporting Wall elements
  • Improved handling reserved Windows name
  • Export HVAC_HEAT_GAIN with current units (Watts)
  • Removed duplicate base quantity NetSideArea exported for walls
  • Improved export with the Property Set option “Export schedules as property sets”
  • Fixed issue with IFC4 Reference view, which fails for some models from Factory Live
  • Update the CSIORG link in the IFC exporter
  • Changed IfcGeometricRepresentationContext from “Annotation” to “Plan”
  • ClassificationCode(2) is now processed during export even if ClassificationCode is missing
  • Corrected Area quantity property of doors
  • Improved Materials export, that works for some floors but not others of the same type
  • Fixed issue with wrong Base Quantity information in some scenarios in IFC export 2×3 Coordination View
  • Fixed issues with warnings are shown when exporting to IFC4RV in some models
  • Improved Railings import to Revit via IFC
  • Properly convert this Flow_Rate parameter on Export
  • Corrected 2D CurtainWall door swing on IFC Export
  • Nested curtain wall element now will get proper parameters while export to IFC
  • IFC-Export configuration will now remember the previous settings including: “Project Origin/Coordinate Base”
  • Improved exporting of Material parameter
  • Improved IFC4 RV Exchange Requirement, which may be missing when File Header is not initialized
  • Support allowing a predefined type for standard railings on export
  • Fixed IFC4 “opening as recess” code for ReinforcingMesh case
  • Fixed issue with IFC export where some geometries are exported slightly longer extrusion
  • Fixed issue with IfcGeographicElement not exporting user-defined PropertySets

Import bug fixes:

  • Improved Rebar import
  • Improved import of Windows that are not cutting a wall in a linked or opened IFC
  • Recognize the angle between Project North and Survey Point properly in Revit IFC import/link
  • Improved import of Columns that may be placed in the wrong location on IFC Link in some cases
  • Improved import of beam cover
  • Fixed issue with Certain Tekla IFC geometry not visible when using Link IFC
  • Improved link IFC that may have incorrect geometry imported for some cases
  • Improved Link IFC file in Revit that in some cases failed with the model empty and an error appears in log file
  • Fixed issue with translation IFC having mm units using Revit IFC loader makes default model view small unexpectedly on LMV
  • Fixed issue related to invalid/corrupt IFC files that “load” without any errors
  • Improved link IFC file properly inside Revit 2020
  • Grids placed by IFCOFFSETCURVE2D will be placed at open IFC in the correct unit
  • Fixed issue with multiple versions of the same IFC file get loaded into Revit Cloud Worksharing Host resulting in duplicate geometry
  • Improve the structure in Link IFC that may end up upside down
  • Fixed missing material information upon import IFC
  • Recreate IFC/Import_Quantities/Import_Quantities.txt
  • Support IfcGridPlacement for Link IFC
  • Avoid duplicate instance and type names when linking in an IFC file
  • Improved creation of Geometry which may be missing for some IFC models
  • Fixed issue for some IFC files that failed to show in BIM 360 viewer
  • IFC link – model is now correctly positioned when there is rotation component in IFCSite local placement
  • Improved issue due to “bad” data involving Wall with zero thickness inside the IFC file that caused differences between IFC from Allplan opened/imported vs linked in Revit
  • Improved handling of detailed geometry containing IfcAdvancedBrep in REVIT 2020 and 2021
  • Improved slab elements import which may be missing in some IFC file
  • Corrected IfcPort ConnectedTo IfcGUID information that contained its own GUID instead of the GUID of its connected Port

Known Issues/additional notes:

  • This release still contains issue that Steel Connections may not be exported correctly
  • Export configuration “IFC2x2 ePlan Check” has been removed as it is already obsolete. If there is any saved configuration, the option will be automatically assign to IFC2x3 as default

Revit lets you model things that you can’t necessarily build, which shouldn’t surprise us given that “Revit was intended to allow architects and other building professionals to design and document a building” 🙂 wiki

However, in recent times Revit is getting used more and more for fabrication workflows, with core Revit features, addins, and Dynamo scripts developing to make that happen.

With that in mind, I was shared something recently and simply had to share it… check out the video below:

Basically it shows how we can quickly cut up impossibly long modelled Revit elements (like Pipes) into more ‘buildable’ fabrication lengths. Cool! The video also discusses how appropriate generic fabrication content could really begin to bridge the gaps between Revit models and actual things you can buy off the shelf.

Thanks to Nathan Moore for sharing this! And credit also to Jeremy Tammik and Pablo Derendinger.

 

I think we will inevitably see more and more automations like this that connect Revit to real fabrication and procurement workflows. Feel free to share your thoughts and ideas in the comments!

 

From the video comments:

Are you paying for a Revit M/P Fabrication add in or using ITMs to route and coordinate to LOD400? I think there is an opportunity to use native Revit to accomplish this. A properly “parameterized” fitting family combined with the correct pipe types and routing preferences would allow native Revit to produce what you need.

Dynamo Script here:

https://github.com/natethegrate1/MEPTools/blob/master/place_coupling.dyn

Credit to Jeremy Tammik and Pablo Derendinger:

https://thebuildingcoder.typepad.com/blog/2020/03/splitting-a-duct-in-more-depth.html

https://engworks.com/revit-dynamo-script-to-cut-pipes-and-ducts/

Some related thoughts and ideas from Nate here, pointing out a common problem with modelling generally (that in order to model accurately, you often have to select some kind of proprietary brand / make / model first):

I am in a situation (and I think most other companies are in similar situations) where I am not necessarily the final decision maker on the “BRAND” of pipe/fittings that we end up buying. There is a fundamental disconnect I think in the industry that fabrication software providers want to provide MANUFACTURER SPECIFIC items to help streamline the downstream purchasing/install/warehousing operations… My solution is to create a “SPEC DRIVEN” family library (similar to how duct works) so I can simply have an “ASTM SCH40 Welded” system or a similar Grooved system etc. That way the families placed will adhere to the spec and allow more flexibility downstream for the buyers/warehouse.

Every now and then you come across a project that is still using a super-old version of Revit (remember Revit 2017? Yeah, it was released about 5 years ago…)  You might have found that your old versions of Revit have actually stopped working or stopped activating due to Autodesk license system changes.

So… how can you get access to Revit 2017 or other old Revit versions? As recent as November 2020, Autodesk enabled access as shown below:

“As on November 2020, Autodesk expanded “previous versions” back to 5 versions for all Subscription customers. https://customersuccess.autodesk.com/articles/expanding-previous-version-access-to-5-versions-back-for-all-customers

So you can use, at this point back to 2015 and next year and when the software advances to the new version in April, this will change to 2016.

There shouldn’t be any need to apply for the extra previous licenses. The seats won’t show up in the Autodesk Account however and you need to access the installers via AVA. https://ava.autodesk.com/

Please note that 2017 Autodesk software supports the login method. That means that you will not use a serial number when the install the software. You should gain access to 1 seat of the 2017 Revit for every applicable Revit product that you own on subscriptions. By assigning Revit to a user you will effectively grant them access to all versions so you don’t need to specifically assign 2017.”

As simple as that! Just use AVA to download and install the older version. See the short video below:

 

Thanks to Dave Murray from McGregor for the heads-up!

I was recently working on a multi-vector dataset comparison in Deep Space. We had received Revit, Navisworks and tabular data, and I was comparing 3 different data drops of that information, particularly for changes in the quantities of specific types of elements. A ‘data drop’ is a set of data or files that you receive at a given point in time.

In the course of exporting the Navisworks data through to CSV, I came across a specific problem – the number of rows in imported CSV did not match the number of elements processed. Why?

As you may know, you can store line breaks inside parameters in Revit. There are very few good reasons to do this, but it still does happen. Once this happens, those line breaks need to be processed by tools down stream. I spent a lot of time in the early days of Deep Space figuring out how to ‘clean’ bad Revit data so we could still bring it into the platform for analysis. Usually, if the CSV writer or reader are smart enough, they should be able to deal with this problem. However, I discovered a bit of a gap in the available tools this time. What was the problem?

It turns out that the CSV was malformed, it was actually dirty or bad data. While it did have the line breaks, it did not consistently use double quotes to contain fields. So we had the situations where there would be line breaks that were inside the CSV fields or columns, but not inside double quotes. I tried a lot of different CSV readers, including Excel, LibreOffice, Google Sheets and PowerBI / PowerQuery, but they all tripped up at this data. Because they were using the rule ‘new line = new row of data’, the imported CSV information was coming in mangled.

How can we clean this data? We generally know there should be 17 fields or 16 commas per row of data. But we also know there can be line breaks inside fields… so it is a challenge to map a data row to CSV lines. In some cases 2 or 3 lines of CSV data might still just be one row of actual data.

After trying to use various out of the box solutions, I decided to build some Python code to try and solve this. I used Dynamo Sandbox 1.3 to do this, primarily out of habit, not because it is the best Python IDE out there 🙂 I ended up with a kind of line-merging iterator, here is some of the Python code below:

biglist = IN[0]

commact=[]
for ctr in range(len(biglist)):
    astr=biglist[ctr]
    strct=astr.count(',')
    commact.append(strct)

counted=range(len(biglist))
fixedstr=[]
bad=[]
skips=[]
incr=0

for ctrx in range(len(biglist)):
    if ctrx==skips:
        pass
    elif commact[ctrx]==16:
        fixedstr.append(biglist[ctrx])
    elif commact[ctrx]>16:
        fixedstr.append(biglist[ctrx])
    elif commact[ctrx]+commact[ctrx+1]==16:
        jnr=[]
        jns=biglist[ctrx]+biglist[ctrx+1]
        fixedstr.append(jns)
        skips=ctrx+1
    else:
        bad.append(ctrx) 
        
OUT = bad, fixedstr, commact, counted

What does it do? Essentially, it counts the number of delimeters (commas) on one line, then it processes or merges lines based on that information.

This actually got me around 90% of the way there. Then I still had to do some manual fixes of things like ‘double double quotes’ that were also tripping up the CSV readers.

Above is a snapshot of the Dynamo script. And here is the script for download:

CSV Line Merge for Malformed CSV

What the the lessons here?

  1. Try and fix the source or native data if you can. Dealing with messy data downstream can be a real pain.
  2. If you need to solve this problem, you can pick up my code or work above and advance it a bit further to build a more robust ‘malformed CSV reader’
  3. Don’t let problems like this distract you during the holidays 🙂

I have recently developed a few Material and Object Procurement and Tracking solutions, primarily using Deep Space and Revizto together. These workflows also involved IFCs converted into Revit, so we could automatically set tracking parameters from Deep Space data back into Revit, and colourise the models. When converting Revit to IFC, I usually use IFC Link functionality, primarily for speed and geometric integrity.

 

However, some DirectShape objects created by IFC Link cannot be overridden in Revit using traditional methods. Even after setting Revit parameters from Deep Space, and using Visibility/Graphics Filters, the elements simply will not allow their colours to be overridden using a Shaded Surface pattern. So, we have to find another way…

 

It turns out that Phase Filters are really the only way to solve this problem, as they override the elements at the Material level. There are a few pieces to the puzzle:

  1. Set up the necessary Phase Filter, with each item set to Overridden (this allows for basically 4 status overrides in total)
  2. Set Graphic Overrides – Material definitions to have the colours you want (by changing Phase – Exist material etc to the desired colour / material)
  3. Set the Revit view to the correct Phase and Phase Filter, and Realistic view mode

Here are some screenshots of the above steps:

1 - Create Phase filter for visual Overrides
1 – Create Phase filter for visual Overrides

Next…

2 - Edit Revit Material to match desired visual Overrides
2 – Edit Revit Material to match desired visual Overrides

Then…

3 - Set the View Settings
3 – Set the View Settings

 

Also…

Keep in mind if you are using Container Files you will need to Transfer Project Settings and bring across your

 

Finally…

Make sure your View is set to Realistic in Revit, if you truly want to see the Material Phase override in the Revit view.

You might receive a message like this when opening a model in Revit:

Missing Third Party Updaters
Missing Third Party Updaters

 

 

An Updater is a piece of code that basically works to continuously sync a Revit model with some external properties or logic. In this case, the updaters missing included:

  • REXExtension: DReinfFootingSpread
  • REXExtension: DReinfWall
  • REXExtension: DReinfColumn

This was in a Structural design model that I received in Revit 2017 format, and I then upgraded to Revit 2018.

I then tried to install the “Structural Precast Extension” for Revit 2018 – but the error still appeared.

After that, I installed the “Revit Extensions for Autodesk Revit 2018” package.

Which appears on this Extensions Ribbon:

This solved the problem – the “Missing Third Party Updater” message did not appear again when opening this model in Revit 2018.

You can download Revit Extensions from:

  • then Filter or Search for Extensions
  • and Download and Install

On this particular project, I’m acting in my usual Strategic BIM and VDC Implementation capacity, and we are rolling out our typical software stack to a large project team. This includes:

  1. Setting up BIM360 for Revit cloud worksharing, federating models in Revit and creating control model/s
  2. Syncing data to Deep Space – we will immediately use Deep Space for project quantification, compliance, and model compare between Tender dataset and current Revit dataset
  3. Exporting models to Revizto for team review and collaboration

You can get the Revit 2020.2.2 Hotfix direct download here.

Here are the Release Notes

Release notes (reproduced below):

The Revit 2020 updates and hotfixes are cumulative and include all changes from previously released Revit 2020 updates.

After this hotfix is applied successfully, the build number specified on the Help > About dialog will be:

  • 20.2.20.31
  • 20200426_1515(x64)
  • 2020.2.2
Software embedded in the update executable:
Revit 2020 – version 20.2.20.31
Autodesk Cloud Models for Revit 2020 – version 20.2.20.31
Personal Accelerator for Revit – version 21.0.11.0
OpenStudio – version 0.1.9

Issues Resolved

Annotation – Dimensions
Fixed an issue when upgrading a model with an incorrect dimension leader style.
Beams, Braces
Fixed an issue that structural framing elements might be incorrect for cloud rendering.
Fabrication – MEP
Fixed an issue that could lead to product instability when dragging to connect open ends of inline fittings.
Fixed an issue with the Optimized Straights feature which was occasionally incorrectly altering the length option from Auto to Value.
Family Editor
Improved stability when using Create Similar with certain families.
File Open/Save Internals
Improved stability when saving a family file from a cloud model after changing the Maximum backups in File Save Options dialog.
Floor
Improved stability when orbiting or editing elements in a 3D view.
gbXML
Fixed an issue that caused exterior wall surfaces to be assigned to a space without a spaceIdRef when exported to gbXML.
Import/Export Other
Updated Revit to use FBX Toolkit version 2020.0.
Licensing
Fixed an issue which caused Revit to become unresponsive.
Link Topography
Fixed an issue where coordinates were changed when the linked topography was reloaded.
MEP Other
Improved stability when editing a family that had been corrupted.
MEP Pipe
Fixed an issue that caused instability when switching views while editing a pipe’s diameter.
Reinforcement – Shape Driven Rebar
Improved stability when upgrading a Revit project containing rebar.
Improved stability when editing rebar constraints.
Revit Home
Fixed an issue where the name of the local copy instead central model was displayed on the Recent Files page.
Startup/Shutdown
Removed potential security vulnerability.
User Interface
When an unrecoverable error happens, a clear link from Revit to the self-service support page is provided.
View – Analysis Visualization
Improved the performance of the display of Analysis Visualization entities when more than one set of independent results is added to a view simultaneously.
ViewCube Navigation
Improved stability when click on the navigation bar.

Important Notes

Dynamo for Revit
In some cases Dynamo will not be visible within the Manage tab after 2020.2.2 Hotfix is applied. To restore Dynamo, replace DynamoRevitDS.sig and DynamoRevitVersionSelector.sig the following location: C:Program FilesAutodeskRevit 2020AddinsDynamoForRevitRevit
Content
Updated Content for Revit 2020.2 is not included in the patch deliverable and is provided on the Autodesk Knowledge Network, link.
Uninstall
Revit updates cannot be uninstalled to revert Autodesk Revit 2020 to its pre-update state. If you need to remove the update, please uninstall Autodesk Revit 2020 and then reinstall it.

In the old pre-BIM360 days, if you really had a problem where a Revit user didn’t relinquish elements in a workshared model, you could either

  1. Pretend to be that user and sync (yes just by changing your user name in Revit Options), or
  2. Detach that Central model and Save As.

Modern day BIM360 Revit Collaboration doesn’t allow either of those to happen easily…

So how do you relinquish elements in a BIM360 cloud Revit model?

Here’s how:

  • Open Revit and a model
  • Then go to Collaborate and Manage Cloud Models.
  • Browse to your BIM 360 Project and then the actual Model
  • Use the icon to view the model Actions menu and choose “Relinquish”
Screenshot from Revit 2018
Screenshot from Revit 2018

When prompted, choose “Force Relinquish”

Choose the User and then click Relinquish
Choose the User and then click Relinquish

and Continue

Confirm by pressing Continue
Confirm by pressing Continue

Then, wait for the process to complete.

Finally, it is probably a good idea to Sync with Central 🙂

 

Revit Help Links (note, the process is basically the same for all current versions):

Most experienced Revit professionals are somewhat wary of brand new versions of Revit, and they might wait a year or so before actually deploying a new version of Revit. The Revit 2021 release season is nearing in the next month or two, so it is somewhat surprising that a serious issue with Revit 2020 (specifically with update 2020.2) has surfaced in the last couple of weeks…

cue scary Jaws music da-dum da-dum

Some of you may have been tracking the Family Corruption issue with Revit 2020.2 update, the Autodesk Hotfix for that issue, and then some of the possible problems with the Hotfix. Below you will find some further detail on this, including download links.

Initially Autodesk released a hotfix (around 4mb), but I believe that has now been replaced with a new combined 2020.2.1 installer (around 378mb) that includes 2020.2 and the hotfix in one installation. You can no longer download the previous *bad* version of 2020.2 (such as was linked here). Screenshot below shows the actual mini hotfix file:

 

File Name: Autodesk_Revit_2020_2_1.exe

Direct Download Link: Revit 2020.2.1 Download (full 378 mb package)

Release Notes: link here

 

Some users have experienced an issue where Revit does not launch after the application of 2020.2.1

 

Here are the full details on the Family Corruption issue, including “how can this happen” and “how you might try and fix it”:

To check existing projects for corruption

Go through the steps in the following article to Audit and then review the Revit journal:
File will not synchronize in Revit

To repair the corruption

Use the instructions in the article above to reload the families called out in the Revit journal.

Question/Answer:

Q. What is the issue?
A.  A change in the way that Revit 2020.2 processes families can cause family content to go missing from workshared central models created in previous versions if the families have existed in an active project for a long time without being modified. The defect results in the deletion of the family content from the central model.

Q. Which versions/models are affected?
A. This issue affects only Revit 2020.2. Previous versions are not affected.

Q. What models are affected?
A. The issue can affect workshared models that were created or upgraded in Revit 2020.0 or 2020.1 which are then repeatedly modified in Revit 2020.2. This issue can impact central models stored locally, on Revit Server, or in Revit Cloud Worksharing. The following models are NOT affected:

  1. Non-workshared models
  2. Workshared models created and exclusively modified in Revit 2020.2
Q. What is Autodesk doing to resolve the issue?
A. Hotfix was released 02/07/2020. A full install of Revit will be updated to include the hotfix in the next few days.Q. Revit 2020.2 has been available for months – why didn’t Autodesk communicate anything previously?
A. The Revit team was first made aware of a possible issue by our customers a few weeks ago. Since these kinds of issues can be difficult to reproduce from scratch, from the time a concern was raised we have been working closely with those customers to reproduce the issue. We were finally successfully able to reproduce, and therefore confirm, the issue at the end of last week when we took action to limit the availability of Revit 2020.2. We have been working diligently to clarify the full scope of the impact and the possible workarounds in order to write this communication.Q. Why didn’t the Revit team discover the issue during pre-release testing?
A. Unfortunately because this issue requires a combination of model creation and modification of families in a previous version and then extensive modification to the same model in 2020.2 it does not lend itself well to typical testing practices or automated regression tests. This means that unfortunately, despite rigorous Revit 2020.2 testing, we were not able to identify the issue before it affected customer models. We sincerely thank the customers that escalated the issue to us so that we are now able to take appropriate action.

Q. What actions will the Revit team take to prevent this kind of issue from happening again?
A. After the Revit team resolves the immediate issue, we will be holding a retrospective to clarify how the defect occurred and what specific actions we can take to prevent similar issues in the future. As much as possible we will look to create automated tests to cover this kind of situation as that means that every future Revit code submission will be scanned for similar problems.

Related blog posts: