I’m very excited to report that the Deep Space platform continues to rapidly evolve, bringing exciting updates that empower civil and infrastructure projects. In a recent release, Deep Space introduced new and enhanced existing synchronization plugins and tools, revolutionizing data acquisition, analysis, and compliance checking. This blog post delves into the key new features of the Deep Space Sync add-in, focusing on its IFC integration and LOI (Level of Information) Report capabilities. Jump straight to the video here.

Simplifying Data Acquisition and Storage

Deep Space now offers a user-friendly IFC Sync plugin, enabling users to effortlessly load data from IFC (Industry Foundation Classes) files into the platform. By selecting the desired IFC file, workspace, and project, users can seamlessly upload the information to Deep Space. This streamlined process ensures that different data and model formats, such as IFC and Revit files, are easily accessible and integrated within the platform.

IFC Sync

Exploring Data and Parameter Analysis

Once the data is uploaded, users can navigate to the Deep Space Explorer platform to explore various applications. The Data app provides a comprehensive overview of the acquired information from the IFC file. Users can visualize the data, including the element count, parameter summaries, and individual parameter values. By clicking on specific objects, users can access detailed parameter data, facilitating a deeper understanding of the model.

Efficient Compliance Checking with LOI Reports

Deep Space’s LOI Report app is a powerful tool for compliance checking, particularly for projects adhering to government requirements like the Transport for NSW Digital Engineering Standards. The app automates the verification process, comparing the required parameters against the actual data within the IFC and Revit-based models. By unifying both types of data, Deep Space provides a single platform for comprehensive checking, streamlining the compliance process.

Advanced Analysis and Customization

The LOI Report offers an array of functionalities for in-depth analysis. Users can check the existence of parameters and validate the presence of data within those fields. Deep Space also supports the verification of shared parameter GUIDs and duplicates, ensuring the uniqueness of asset IDs. Through drill-down capabilities, users can access specific files, view available information, and explore the requirements tied to each parameter set.

Configuration and Automation

Deep Space provides a robust configuration engine (we call it DS Command), allowing users to modify templates, load parameter standards, and create a master parameter set for consistent use across projects. Additionally, the platform offers scheduling capabilities, enabling users to automate the export of models at predefined times. By simplifying configuration and scheduling tasks, Deep Space optimizes efficiency and reduces manual effort.

Conclusion

The latest Deep Space release showcases its commitment to overcoming industry challenges related to diverse data formats, data acquisition, and analysis. With the IFC Sync add-in and updated LOI Report app, Deep Space provides a comprehensive solution for integrating IFC files, performing compliance checks, and ensuring predictable outcomes. By leveraging Deep Space’s powerful features, Digital Engineers and Design and Construction teams can accelerate project delivery, reduce risks, and enhance overall quality.

Watch the release video here

As part of a very bad Cloud Model upgrade experience (a story I will tell some other time…) some models failed to upgrade.

I was trying to upgrade a file from Revit 2018 to Revit 2022. After upgrading, I was unable to save this file, even though I have a machine with 192GB RAM.

Revit reported this message:

“This computer does not have enough memory to save…”

“Increase the available memory or contact Autodesk Support for more information”

 

I contacted Autodesk Support, and eventually got this reponse:

Due to the “Multi-category Schedule”, the Revit file was failing to save in Revit 2021 or Revit 2022 version as the schedule view is large. 

After deleting the schedule view we are successfully able to save the file. Attached is the fixed model…

 

Sounds good! Let’s give it a go:

  1. Open the model in Revit 2018
  2. Identify the Multi-Category Schedule
  3. Let’s back it up while we can using “Save…”

  4. Now delete the Multi-Category Schedule

  5. And then Save the Revit 2018 File somewhere
  6. Open Revit 2022
  7. Manually upgrade using Revit 2022. Detach, Audit and Specify worksets (All Closed) on Revit 2022 open settings:

  8. Does it save now – yes!
  9. Initiate the Model into the correct folder on the (now upgraded) Revit 2022 BIM360 site.
  10. Finally, I tried using “Insert Views from file” to load back the Revit 2018 Multi-Category Schedule into the upgraded project – but it still would not save if that schedule exists:

  11. I guess we have to do without that Schedule for now – it saved fine again after deleting it. Happily the project uses Deep Space so we have access to all Revit data anyway!

One day, when I recover from the experience, I will write about the overall Revit Cloud Model Upgrade experience when dealing with hundreds of models and trying to jump from Revit 2018 to Revit 2022…

Back in 2016 I put this simple, messy sketch together to describe some basic terminology around Revit models and how they are structured:

model_hierarchy_lj

 

Revit Model:

  • Category
  • Family
  • Type
  • Instance (also known as “Element”)

 

May be hosted by:

  • Levels
  • Grids
  • Reference Planes
  • Faces
  • Special Categories (Floor, Ceiling etc)
  • Nothing

 

May belong to:

  • Phases
  • Worksets
  • Design Options
  • Groups
  • Other Families (nested)

Problem:

I was recently trying to link Revit models to a federated file on Revit 2021. The models were failing to link, but no error message or warning was provided. The federated host model and the links were all initiated and ‘live’ collaborated models on the Autodesk Construction Cloud.

 

Resolution:

I had previously used this method ( Moving the Revit BIM360 CollaborationCache Folder to a Secondary Hard Drive ) to move the cache for BIM 360 / ACC Docs to a secondary hard drive. Windows Explorer showed this hard drive was essentially running out of space. So Revit was failing to link the model, but wasn’t providing a ‘insufficient hard drive space’ warning.

But why was the hard drive filling up?

I reviewed the files and folders and discovered that one particular program was generating massive log files:

The final resolution was quite simple – delete the massive log files, and then the files linked to Revit fine. I used 7-zip with the “Fastest” and “Delete files after compression” option to archive and delete those logs.

To future-proof this scenario, I’m considering writing a Powershell script to detect and possibly archive and delete the existence of massive log files.

I have been receiving a few requests for access to files that were previously linked to What Revit Wants via Google Drive. Somewhere along the line, Google (in its wisdom) decided to change security requirements and now my inbox has been filling up with ‘Share requests’. My opinion on Google business practices in general is pretty well known after this saga.

Some of the more popular files requested in recent times have been:

  • CurvedMullionLJ.zip – from post here about Curved Mullions
  • SetMarksToElementID.zip – from post here
  • PointCloud.zip – from post here
  • Generic Label.rfa – from post here
  • URL Text Symbol Annotation D download.rfa – from post here

In any case, I have now decided to move the hosting of What Revit Wants files and resources to wrw.is and you can view and download them all below.

Note: you will need to login to this site FIRST to see and download the files.

 

If we head over to IFC 2020 | Revit | Autodesk App Store we can see the latest listed version of the IFC Addin for Revit 2020, which is 20.3.2.

2022-03-31-12-33-25

However, if we head over to revit-ifc Releases page on Github – Releases · Autodesk/revit-ifc · GitHub – then we see that there is a prerelease build for Revit 2020 that is version 20.3.3.0.

 

So this post is just a little reminder to check the releases on Github if you want the very latest IFC addins provided from Autodesk.

2022-03-31-12-34-42

First, let’s manage some expectations – Aconex is generally viewed as a closed platform. They seem to deliberately resist platform-level integration with other tools like BIM 360 and Revizto. However, you can achieve the promise in the title of this post – with a bit of work!

The basic steps are:

  1. Setup a sync between the Aconex Doc Register and Autodesk Docs (BIM 360 Document Management), using the Aconex PIF and Autodesk APIs
  2. Connect the BIM 360 project to the Revizto project and connect your BIM 360 ‘official Aconex’ PDFs to Revizto 2D Sheets.

Step 1 – Aconex Document Register sync with BIM 360 Document Management

Aconex provides a PIF (Project Integration Framework). This essentially acts as an API, and clients are able to build integrations between Aconex and other tools using their own budget.

aconexpif
The Aconex PIF is hard to find on the inter-webs…

As part of my strategic consultancy work as a Director at Virtual Built Technology, I have assisted clients in setting up the Aconex to BIM 360 sync. This will require considerable time, effort, $$ and planning. Although the scope is basically the same for every Aconex client that wants this, it seems individual Aconex clients will be charged significantly for this development to occur and operate on their ‘own’ PIF.

Once complete, you will begin to see PDFs arriving in Autodesk Docs from Aconex on a daily / nightly basis. Depending on how you have briefed the Aconex development consultants, you may end up with some interesting PDF file naming in the BIM 360 environment – so how can we deal with that?

Step 2a – BIM 360 Preparation Script for Merging Filenames to a single Folder

Let’s say you have your Aconex-to-BIM360 sync running, and you have PDFs arriving in 360 into “Discipline” folders like Architectural, Structural and so on. Not bad! But what if your PDFs are named like this:

  • SheetNumberX_Rev_1.pdf
  • SheetNumberX_Rev_2.pdf
  • SheetNumberY_Rev_1.pdf
  • etc

When thinking about downstream applications like Revizto, this is really sub-optimal. Why? Because a Revizto 2D sheet will want to connect directly to a SINGLE BIM 360 PDF document with Versions – not to a mangled set of ‘revision suffixed’ pdfs like the above. So we need to clean this up! And it needs to be repeatable and automated

For this, I have created a PowerShell script. Here is a description of the logic in the script:

  • it takes a list of BIM 360 Docs folder paths (the local folder path from Windows Explorer address bar), these are ‘monitored folders’
  • those folders need to be ‘synced’ prior to the script running (I’m still looking for a way to call the Autodesk Desktop Connector sync from a Powershell script, for now you have to right-click in Windows Explorer first)
  • it will process the folder list and:
  • create a subdirectory called “Current”
  • create a logfile in that subdirectory called deepSpaceSync.log
  • split the filenames at the _REV_ part
  • process each available Revision number individually in a loop (to ensure Aconex revisions are stored sequentially into BIM 360 versions)
  • check if the file was already copied – and skip it (using existence of that filename in the log folder)
  • or, copy the file to the “Current” subfolder
  • Sleep 5 minutes between each loop to allow Autodesk Desktop Connector sync to catch up.

So this script essentially merges the messy “REV” filenames into a nice clean SheetNumber.pdf filename structure AND actually creates BIM 360 file versions in the cloud (due to the sleep functionality).

We have released this script as a publicly available Deep Space Automation at this link.

egoutput
example output from the PowerShell script

Step 2b – Revizto 2D Sheet to BIM 360 PDF Connection

Now that we have a nicely named, version-rich PDF on BIM 360 Docs, its time to connect that up to Revizto.

Firstly – you should always publish 2D sheets from Revit BEFORE setting up the Docs connection if possible, as this is the only way to get the automated viewport overlays (Note – you can export with “Sheet coordinates only” option in Revizto Sheet Exporter from Revit).

Secondly – you then

  • open Revizto
  • ensure you have connected Docs to the right BIM 360 hub in Revizto
  • browse to the “Current” folder for a specific disciplines PDFs
  • click “Send to 2D”
  • select all and Done

    syncrev1
    Connecting Docs to Revizto 2D Sheets
  • then review that the correct sheets are going to be replaced and connected to the BIM360 PDF
syncrev2
Confirm that sheets are correctly connected using the Sheet Number

 

Final steps

Once your PDFs are flowing well between platforms, you may want to automate further. For example, the PowerShell script provided above could be set to run as a Windows Task. You would want it to run as soon as possible after the Aconex scheduled sync to BIM 360. As always, you should monitor your inputs and outputs for any problems or gremlins.

Done! You now have official documents from Aconex flowing regularly into Revizto via BIM 360. This means your site teams using Revizto on the iPad can now be accessing the official For Construction PDF Drawings (synced from Aconex Doc Register) while in the Field!

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.

When a recent update to Autodesk Desktop Connector forced a migration to Autodesk Docs, file paths were generally change like this:

FROM – C:\Users\USERNAME\BIM 360\YOURFOLDERS

TO – C:\Users\USERNAME\ACCDocs\YOURFOLDERS

 

If you were doing some interesting tricks with BIM 360 Docs, and sharing and federating Revit models as non-initiated files on BIM 360, you may find that links were broken and “Not Found” in Manage Links after that latest Desktop Connector installation.

 

But don’t worry! You can just set a symbolic link to point from the old BIM 360 Docs location, to the new location. The Command Prompt script looks like this:

if exist "C:\Users\%USERNAME%\BIM 360" rename "C:\Users\%USERNAME%\BIM 360" BIM360.old
mklink /d "C:\Users\%USERNAME%\BIM 360" C:\Users\%USERNAME%\ACCDocs
Run these commands to fix links Not Found

The moment after this script was run, I was able to hit Reload from Manage Links in Revit and the new location was detected and links were loaded successfully. Note that they still appear in Revit as if they are in the old location, but really it is reading the latest data from Autodesk Docs, and that new location is being updated by Autodesk Desktop Connector.

Related Note:

I had already setup a symbolic link to move my BIM 360 Revit Cache folder to a secondary hard drive.

At this stage it appears those links are still working, as the Revit CollaborationCache is a different technology to the simple file sharing mechanism of Autodesk Docs.