APIdocs.co brings Revit, Rhino, Navisworks and Grasshopper APIs together

Apidocs.co is an ambitious online project by Gui Talarico, the author of the Revit API website called RevitAPIdocs. Instead of focusing on one particular application, apidocs combines several applications’ APIs into one online library with more than 120K unique documents:

apidocs.co

Apidocs has a clean and user-friendly interface, which is easy to use and navigate. Just select the desired application, then either search or dive into its API:

apidocs.co interface

This project is a huge timesaver and a one-stop shop for several design applications’ APIs. Moreover, it is open and free for everyone.

And if you are interested in supporting the project, head over to support page: apidocs.co/support

What’s new in Navisworks 2019.1

Navisworks 2019.1 update (available via the Autodesk Desktop App) comes with the following list of bug fixes and improvements:

Improvements

  • [LMV] Support .VUE file property.
  • Fixed incorrect IFC Class and Element description in IFC hierarchy.
  • AVEVA E3D import (RVM file format) – missing attributes in the object properties.
  • Allow Display ID to be shown in Timeliner overlay text.
  • Add a space between the date and time in TXT clash report exports.
  • Read shared parameters in corresponding to IFC data.

Bug fixes

  • Timeliner Auto Attach not working on certain Category/Property.
  • SceneConvertServer doesn’t shutdown.
  • Setting global options via API or XML file has no affect with out-of-process loaders.
  • ArchiCAD 21 cannot export nwc with error “Cannot write output file”.
  • Cannot check ArchiCAD 21 in “Configure Installation” dialog when installing NWExporter2019.
  • C++ error rendering a model.
  • Navisworks does not display anything if the assembly is saved in a substitute LOD.
  • Navisworks Manage 2018 crash with CER during Save.
  • CER when load IFC file after install IFC for Revit.
  • Navisworks License Timeout.
  • Multi – threaded clash, crashing with a point cloud data set.
  • A Chinese translation mistake in Archicad config file “nwexportarchicad.name”.
  • ArchiCAD21 Exporter options display unreadable code in localization OS.
  • Exported NWC and Glued model are not what is displayed in Revit.
  • English Language Pack – Spanish category objects in selection tree.
  • Revit to Navisworks Export is excluding certain instances of family.
  • Navis exporter progress dialog issues.
  • Global Options overrides are not passed onto SceneConvertServer.
  • Some files cannot be loaded with internal error.
  • Cannot load rvt because of an internal error.
  • Navisworks 2018 crashes with saving file.
  • Embedded texture is not displayed while opening NWD file.

Direct download links for 2019.1 update could be found at Luke Johnson’s blog.

If you are interested in Navisworks future, please vote for bringing back Navisworks Idea Station here: Autodesk community ideas.

 

Will Rhino 7 run inside Revit?

McNeel & Associates have recently published a webpage about the “Rhino Inside” technology, which sounds pretty amazing:

Rhino 7 WIP (Work in Progress) can now run inside other 64-bit Windows applications such as Revit, and potentially AutoCAD, Solidworks, Photoshop, Excel, etc.

Imagine that you could run Rhino’s geometry engine inside Revit environment. This could be a game-changer for those who work with conceptual design.

The bad news is that “Rhino Inside” is in the early phase of development, so that there is nothing to see or test for the moment. Even the Rhino Inside webpage is full of placeholders for the download and help links:

Try Rhino inside Revit (RiR)

  1. Download and install the Revit plugin.
  2. Try the Rhino, Grasshopper, and Python examples.
  3. Build your own RiR tools. How to get started…
  4. Check out the source code for RiR and the related examples.
  5. Try writing a Rhino Inside plugin for your favorite product. How to get started…

Personally, I don’t mind the wait: it’s almost certainly better to have the new feature work well when it launches, rather than launch with bugs.

What’s better than clash detection? Live clash detection!

We’ve been doing iterative clash detection in out projects for years. This is an old-fashioned and time-consuming process, which consists of repetitive manual or semi-automatic tasks:

  1. Convert each discipline model into the Navisworks / Solibri file formats.
  2. Update project federated model.
  3. Run multiple clash tests.
  4. Publish results.
  5. Introduce results to the design team.
  6. Next hour/day/week/month repeat steps 1..5

Wouldn’t it be great if we could spend our time in a more effective manner? There are actually a couple of software platforms that offer live (real-time) clash detection inside Revit environment.

BuildingSP ClashMEP

Read more about ClashMEP here

MagiCAD for Revit 2019

Read more about MagiCAD for Revit 2019 here

Both of these Revit add-ins use the same concept: they provide you with clash detection in real time, while you build your model. There is no need to iteratively run clash tests, and you can visually see the conflicts in views and schedules. You can see the full process in these videos above.

The future of clash detection is coming!

Autodesk published IFC Manual for Revit users

Revit IFC Manual is a 52-page document, which describes all of the available options for using IFC format within the Revit environment. This is definitely a handy document for everyone working with Open BIM.

This document is intended to serve as a guide for Revit users handling IFC data and providing a better understanding of the settings available in Revit, discussing the way they can influence the quality and the content of the IFC file.

The Revit IFC manual therefore sets out the basics of IFC and explains in detail how to export, link and open IFC files in Revit.

Revit IFC Manual

The Revit IFC Manual is available for download from the official Autodesk website (direct link). I also suggest you to check out a series of articles by Simon Moreau from BIM42 about Revit IFC exporter settings:

You may also need to update your Revit IFC exporter to the latest version: download from Sourceforge

Conductor Revit & Rhino add-in becomes free and open source, bringing Trello boards inside your models

Conductor is a Revit and Rhino add-in that integrates Trello task management with your models. This add-in has originally been released as paid application (I’ve already mentioned it in my post last year) by Nathan Miller from provingground, and now it’s available for free.

Conductor uses Trello API to move your tasks between Revit (Rhino) and Trello. The integration is clean and seamless:

 

Below you can find the the add-in requirements:

  • Revit 2017/2018*
  • Rhinoceros 5.0 64-Bit for Windows*
  • Windows OS (Developed and tested with Windows 10)
  • ClickOnce installer is best used with Internet Explorer
  • ClickOnce user installer assumes a standard Windows user setup
  • Internet connection
  • Trello account (you’ll also need to authorize the app with your own Trello token)
  • * Versions for Revit 2019, Rhinoceros 6, and Navisworks 2019 are forthcoming.

You can also read the full description here (including the download links), and release notes here. Source code has been posted to bitbucket.

Speckle.works now supports Dynamo

A couple of months ago I wrote about the tragic death of Flux.io – the service that allowed us to seamlessly exchange BIM data through the cloud.

One of the possible substitutes for Flux is the Speckle.works – an open source (MIT) data communication platform. Until recently it had only Grasshopper integration, and yesterday they published the very first alpha version of the Dynamo package.

For those of you missing the Flux, go ahead and download the package called “Speckle for Dynamo” from dynamopackages.com

Please note that this is still an alpha version, and there may be some issues. And in case you encounter any problems, don’t hesitate to report them @ GitHub or Speckle.Works.

Dynamo 2.0 is now available

A couple of months ago I’ve made a Sneak peek into Dynamo 2.0, showing you some of the upcoming changes to the “Next gen Dynamo”. And now that Dynamo 2.0 has finally arrived, you can do the following:

  1. Read the official release notes here: To Dynamo 2.0 and Beyond.
  2. Download Dynamo 2.0 release version from the official repository @ DynamoBuilds.comDynamo 2.0 release
  3. Back up your existing Dynamo library:
    %appdata%\Dynamo\Dynamo Revit\1.3
  4. Completely uninstall Dynamo 2.0 pre-release build if you have one.
  5. Install Dynamo 2.0 release version and play with the new features.

Please note that there are still some issues with this release

(see this page @GitHub for reference: dynamo known issues):

  • Node library search may not work properly (GitHub issue 8757 & GitHub issue 8769)
  • Dynamo 2.0 has a conflict with Revit 2018.2’s and 2018.3’s (GitHub issue 8768) implementation of P&ID Modeler (thanks jmmkm for the tip in the comments section below) resulting in the library/browser now showing. This issue is not present in 2018.1, or Revit 2019. If you want to use 2.0 with Revit 2018.2 or 2018.3, you will need to remove the the manifest file
    C:\Program Files\Autodesk\Revit 2018\AddIns\PnIDModeler\PnIDModeler.addin
  • For custom nodes, using dot-notation in node Names or Categories will result in additional nested sub-categories. The “.” will work as a delimiter to determine the additional hierarchy. This is new behavior in the library for Dynamo 2.0.
  • If the network drive pointed to by “Manage Node and Package paths” is > 1TB in size loading Dynamo may take a minute or more, irrespective of actual package size. We recommend drive size of 100GB or smaller.
  • Toggling the freeze state can cause a node to be executed twice after editing a Code Block Node.
  • Installers fail to prompt for missing VC++ components which causes Dynamo to silently crash at load time
  • Packages that deliver DynamoServices.dll may have corrupted multi-output port nodes; instead of multiple output ports, they will be collapsed into a single output port.
  • Some JSON graphs may open and erroneously appears to have unsaved changes as shown by the asterisks in the workspace tab.
  • If your workstation contains multiple major versions of Dynamo, e.g, Dynamo 1.x and Dynamo 2.x, Dynamo Player will start with whichever version you select for Dynamo for that session.
  • Custom node libraries that contain the same category and node names result in unexpected library organization.

If this list of known issues is not critical for you, feel free to be an early adopter.

Navisworks 2019: nothing to see here, move along

This year’s Navisworks 2019 has been around for about two weeks, being released rather quietly. And the reason for this is pretty obvious: there is nothing new inside, except for the version number, desktop shortcuts, and a splash screen.

Considering the huge amount of time and effort that Autodesk spends with BIM 360 products, it is no surprise that Navisworks becomes abandoned. New features are coming to the cloud, leaving desktop products obsolete, and this is inevitable.

All of these machine learning and artificial intelligence stuff just can’t fit into the single desktop application. And we’ll probably see the other products shifting to the cloud in the coming years.

Quick Access Toolbar missing in Navisworks on Windows 10 with UltraHD (4K)

If you are using Navisworks 2017 / 2018 on Windows 10 with UltraHD (4K) monitor, then you’ve probably seen this picture:

Navisworks QAT 4K not visible

Quick Access Toolbar (QAT) is invisible, while the buttons are still in place (hover over them with mouse cursor, and you’ll see the tooltips).

The problem is caused by WPF hardware acceleration, which is enabled in Navisworks by default. Here are the steps to switch off WPF hardware acceleration and bring Quick Access Toolbar back:

  • Open Navisworks options > expand Interface menu > select Display
  • Switch off the WPF acceleration:

Navisworks WPF off

  • Click OK to accept changes
  • Accept the warning message and restart Navisworks:

Navisworks WPF off warning

  • After Navisworks restarts, you’ll see the QAT:

Navisworks QAT 4K is visible

Where to find Navisworks 2018 / 2019 language packs

Autodesk has changed the way to distribute Navisworks language packs. Previously you could have found them via the Autodesk Knowledge Network portal in the Downloads & Upgrades > Service Packs & Fixes menu.

Starting from Navisworks 2018, there are no links to download language packs. Why? Because now language packs for Navisworks are already contained in the software package.

All you need to do is downloaded the software package (which is usually an sfx archive) and extract its contents:

..\Autodesk_Navisworks_Manage_2019_Multilingual_Win_64bit_dlm\x64\

Find the folder with the language code you need:

  • en-US (for English localization)
  • de-DE (for German localization)
  • es-ES (for Spanish localization)
  • fr-FR (for French localization)
  • it-IT (for Italian localization)
  • ja-JP (for Japanese localization)
  • ko-KR (for Korean localization)
  • pt-BR (for Brazilian Portuguese localization (documentation only))
  • ru-RU (for Russian localization)
  • zh-CN (for Chinese (PRC) localization)

Each of these folders contains both Navisworks language pack and Navisworks exporters plugin (NWEXPORT):

Navisworks LP package

Open the folder with the language pack you need and launch the *.msi installer:

Navisworks LP installer

 

After installing the language pack, modify the Navisworks desktop shortcut.

Right-click the Navisworks shortcut > Properties > Shortcut > add the language code in the Target field:

"C:\Program Files\Autodesk\Navisworks Manage 2019\Roamer.exe" -lang de-DE

Save the changes and launch Navisworks.

Toggle contour lines in Navisworks section

Sometimes it could be frustrating to navigate in Navisworks section views when you look at the cut elements without contour lines. The edges of elements can’t be easily distinguished, so that your view becomes messy:

Section Lines off

Since Navisworks 2018 we can change the way Navisworks renders cut elements in sections. This option is called Sectioning and lies inside the Interface menu in Navisworks options:

Interface sectioning options

Open Navisworks options > expand Interface menu > select Sectioning

From there you can enable / disable contour lines and switch their color. This is how the same model looks like after changing the options:

Section Lines on Even while Navisworks does not ‘read’ elements as solids, they could be easily distinguished with contour lines.

Renaming Revit materials with Dynamo

Imagine that you have to rename a lot of materials inside your Revit model. You could spend ridiculous amount of time, renaming all of the stuff manually. The other option would be to write a relatively simple Dynamo script that will handle this task for you.

And here it is – simple yet powerful Dynamo graph:

Dynamo_Rename_materials

This script takes all Revit materials that contain “Concrete”, then adds a custom prefix “Prefix_” to material names. Of course, you could change the logic as you wish.

Please note that you should use the custom node called “Element.SetName” from the Clockwork package (available @ dynamopackages.com) to rename elements! Out-of-the-box (OOTB) node “Element.SetParameterByName” will fail with ‘read-only’ error.

Download the Dynamo graph here: Dynamo_Rename_materials

Flux.io is shutting down on March 31, 2018

Now it’s official: Flux.io, the cloud platform which helps architects, engineers, designers and other AEC professionals seamlessly transfer building data is shutting down. These are the sad news for many of us, especially those who have built up their workflows upon the Flux platform.

The current Flux products (both platform and applications) will be shut down on March 31, 2018. Time to start looking into similar solutions like Speckle.works, an open source data communication platform.