Sometimes in Glue addin for Revit will fail with the message One or more gluing errors occurred“.

You may be able to workaround this problem by following these steps:

  1. After receiving the error, immediately browse to your Temp directory. To do this, open Windows Explorer and type %TEMP% in the address bar.
  2. Sort by Date Modified
  3. Look for a DWF or NWC that matches the View Name that failed to Glue in Revit
  4. Grab that file, and remove the suffix (usually a few digits) so that the DWF Filename = View Name = Glue Model name
  5. Using the Glue desktop app, upload that model manually
Renamed model ready for upload

This process opens up an interesting possibility… usually when exporting a DWF using plain Revit, it will always use Project Internal coordinates. However, the Glue addin can actually export DWFs with Shared Coordinates (if you choose that in the Glue export More Options dialog).

Using the above steps 1-5, you can ‘find’ this DWF with Shared Coordinates and use it wherever you please… such as in Navisworks.

Here is a few quick tips that I had sitting in draft post:

  • To delete lots of views quickly, select and then press Delete key. Do not try to right-click.
  • To combine multiple Clash Groups in the Clash Detective, select the groups, Ungroup (sub-clashes will be selected by default), then Re-group..
  • To delete multiple empty clash groups, drag a clash into one of them. Then, Select All the Groups and you can Explode Group
  • If you Append an NWD, the views with saved Hide/Required and Material Overrides will import “correctly” with these settings (but a Viewpoints XML cannot import these element hide and colour settings)
  •  Use Properties+ … it is simply the fastest way to test and build Search Sets

propertiesplus.png

This might pop up in your Application Manager soon…

update2_2016-8596749

Update 2 for Autodesk Revit 2016 Release 2
Update 2 for Autodesk Revit 2016 Release 2 Readme

R2 download link
http://dds.autodesk.com/2016/RVT/Autodesk_Revit_2016_R2-x64_UPD2.exe

New build numbers for Revit 2016 R2:
16.0.1108.0
20160126_1600

Enhancements list is live at:
http://revit.downloads.autodesk.com/download/2016RVT_R2_UPD2/Docs/RelNotes/AutodeskRevit2016-R2-UPD2ReleaseNotes.html

non R2 download link:
pending…

IFC for Revit 2015 (v15.7):
http://apps.exchange.autodesk.com/RVT/en/Detail/Index?id=appstore.exchange.autodesk.com%3aifc2015_windows32and64%3aen

IFC for Revit 2016 (v16.4):
http://apps.exchange.autodesk.com/RVT/en/Detail/Index?id=appstore.exchange.autodesk.com%3aifc2016_windows32and64%3aen

Details:
New Export Functionality:
Append “(Type)” to all internal Revit type property sets, to avoid having multiple property sets with the same name assigned to the same IFC entity.
Changed how the classification code is parsed so that classifications can have brackets and colons in them.
“Extra Low” level of detail now applies to all faceted BRep geometry, allowing many more files to export without hitting the size limit.
If a userdefined property set contains the same property name more than once, take the last nonempty value (don’t duplicate the property name).
Rebar elements can generate up to 1024 consistent GUIDs for individual IfcReinforcementBars, up from 256.
(IFC4) Zones can now have a long name, set by the “ZoneLongName” shared parameter for nonMEP zones, and the “IfcLongName” parameter for MEP zones.

Export Bug Fixes:
Don’t create orphaned IfcStyledItems.
Don’t export invisible geometry in beams.
Export DirectShapes of Walls category.
Export elements with empty custom classification field values.
Floors exported as IfcSlabs correctly report if they are load bearing or not, using either the “LoadBearing” shared parameter or the Structural builtin parameter, in that order.
Improve performance in certain cases where we can’t create a valid tessellation for a face.
The “Use active view to generate geometry” option now works correctly.
(IFC4) Correct the orientation of some IfcAdvancedBRep faces.

New Import Functionality:
Import IfcProxy as Generic Models.

Import Bug Fixes:
Fix how the IFC GUID is set for certain elements.
Fix the orientation of some imported objects where part of the local placement needs to be calculated.
(IFC4) Read in some missing relations caused by “IsDefinedBy” split into 3 inverse attributes.

via email

ifc-7830420

The Case Apps were (are) great, but they are pretty hard to get now:

suspended.png

One thing you might try is downloading this zip and running the Application Reference file. Turns out something is still alive out there…

caseapps.png

at http://www.case-dev.com/revit/installer$/FreeAddInManager/CaseRevitAddInManager.application

Tick the Terms & Conditions box and then tick the boxes for the apps you want to install.

Note: we also had to disable Microsoft Security Essentials (Windows Defender Real-time Protection) to get this application reference to work.

Here is the big list of apps in the Apps Manager:

This recent post on Dynamo Nodes shows how a simple Navisworks Search Set can be built by Dynamo running inside of Revit:
Create Navisworks Search Set XML for Element Ids | Dynamo Nodes

In the first release, this node just uses Element Ids to build a long ‘orsearch set, but this basic idea could easily be extended and adapted to more closely connect Revit to Navisworks search workflows through Dynamo.

Here is a Screencast:

As you are probably aware, when moving from Dynamo 0.9 to 0.9.1 you lose backward compatibility… in other words, you can’t open 0.9.1 files in 0.9 or earlier.

backwardcompat.png

Before taking that step up to 0.9.1 and beyond, you may wish to apply a filename suffix to all of your DYN files, so you are reminded of this issue when you open a DYN. I have a single folder with subfolders containing most of my DYN files, and I added the suffix (082) to all of them at once with this method:

Install Advanced Renamer.

Add the Directory that holds all your dyn files:

add%2Bfolder.png

Then add a suffix to the filename:

Now, you basically have an inplace backup of files. When you open one of these dyns in 0.9.1 or newer, just remember that you should Save As in Dynamo, and then newly saved file will not be open-able in 0.9 or earlier.

At some point in the future you can then remove or upgrade all of these ‘older’ Dynamo files.