Autodesk® Revit® Architecture 2015 Updates – Corrects the behavior that caused view templates to apply incorrectly for some views, if a temporary view template was also applied to the view.* – Improves stability when editing a families.* – Improves loading and editing families which contain extensible storage.* – Allows type parameters in upgraded families to swap from one type to another.* – Improves stability when upgrading a project which contains corrupt families.* – Improves notification reliability when closing a workset in which a rvt file link has been placed.* – Improves stability while opening the Material Dialog.
Autodesk® Revit® MEP 2015 Updates – Improves highlighting of circuits in the plan view from a panel schedule or System Browser.*
Autodesk® Revit® API 2015 Updates – Improves querying of point cloud on RCS files using the Revit pointcloud API.* Direct links copied here:
Please refer to the Readme links for installation and update enchancement information.
How did this bug happen? I’m not entirely sure, but I think the number of updates and the confusion around which UR5 update is for which Revit version may have resulted in Revit 2015 getting sad. But, its happy again now… and its a good lesson to remember the ApplicationPlugins folder when diagnosing Revit problems.
Something from the journal: ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=000007FEFCDE940D
UR5 enhancements: Improvements made in Update Release 5 build (20141119_0715):
Autodesk® Revit® Architecture 2015 Updates Improves resolving of the Revit Server saved paths.* Corrects the behavior of placing families in a project when the family type selector is expanded. Improves stability when loading families that contain data created by add-ins. Improves stability when ungroup a group. Improved stability when filter a schedule. Improved stability when opening projects with bad dimensions. Improves stability when making edits in the Sun Settings dialog. Improves stability when deleting parts while modifying division. Improves stability when canceling new label creation in family environment. Improves stability when editing materials in families in a workshared environment. Improves stability when clicking the Macro Manager tool in the Family Editor. Improves stability when multiple users load families and undo their actions in a workshared file. Improves stability when two users loaded families of the same name. Corrects an issue with ceiling-hosted lights that caused the lights to be deleted when the ceiling was moved or copied.* Corrected an issue related to placement of face-based families on certain part elements.*
Autodesk® Revit® MEP 2015 Updates Improves stability when editing a conduit temporary dimension in an elevation view.
Autodesk® Revit® Structure 2015 Updates Improves stability when exporting multi-rebar annotation into DWG format.* Corrects an issue with incorrect warning and error messages for groups in design options with a group containing structural framing elements or columns.* Fixed an issue with the generation of the analytical surface for a vertical floor and slab.
Autodesk® Revit® API 2015 Updates Allows the ability to offset the end of a wire when it is connected to other elements.
Why does this happen? Because the Bulk File Upgrader doesn’t work if it is trying to upgrade a Local and it can’t find a Central (I believe this is a Revit API thing)… and you may get this error: filename.rvt could not be upgraded: The file-based central model could not be reached, because e.g. the network is down or the file server is down.
The core problem here is that someone has probably given you a Local copy, when they should have given you a Central or Detached copy to link into your project.
If we want to upgrade lots of these “local-type” linked files, how can we get around this batch upgrade limitation? We will need to to use eTransmit – twice. Let’s say we are upgrading from Revit 2013 to Revit 2015:
Make a blank 2013 RVT project
Link in all the 2013 version files you want to upgrade
Save the host file in 2013 and close it
Transmit the host using Revit 2013, including Links and tick the ‘Open and Save models in the active version of Revit’ option (this places the newly saved linked models into a transitory state, where you can choose to save as central or work with this model temporarily)
Open Revit 2015
Addins – Transmit a Model
Choose the output eTransmitted 2013 host file from step 4
Make sure to tick the “Linked Revit models” and “Cleanup” boxes
Click Transmit Model and wait for all of the files to be upgraded (yay)
Remember to discard the host file before transmitting or copying the files
Note: using the “Add Files” option in eTransmit and adding RVTs manually will not upgrade them.
On latest R2 version of Revit 2015, with Navisworks 2015 SP3 and Navisworks Exporters R3, there remains a Navisworks export bug that affects some projects after upgrade from previous versions of Revit.
Set Level of Detail of view to something other than Fine
Set Level of Detail of categories in V/G to the setting you desire (can be Fine)
Try exporting again
or Try turning off categories one at a time to find out which Category the problem geometry resides in.
or using “uncut” in the Family Editor to uncut the voids from everything, and then using ‘cut’ to cut them again. after reloading back through into the project, this also allowed the export to continue.
or some other way…
The log file reports: Autodesk.Revit.Exceptions.ExternalApplicationException: Object reference not set to an instance of an object. at Autodesk.Revit.DB.CustomExporter.Export(View3D view) at NavisWorks12.LcIRevitBase.Export3DView(View3D view_3d, StateDictionary state_dict) at NavisWorks12.LcIRevitBase.ExportDocument(String& return_message, ElementSet elements, LcIRevitParameters* params)
It hasn’t shown up on Exchange yet, but it is already available for download on the Sourceforge page. There is an update to IFC 2015 (the one that is really robust, fast and accurate for Import and Export), and also some updates to 2014 IFC addins.
Some of my testing: 30% file size reduction in RVT when using Link IFC on 85mb steel model from Tekla v16.1 v15.1.0 = 297mb v15.2.0 = 210mb
66% file size increase in IFC when using export IFC to all proxies: v15.1.0 = 288mb v15.2.0 = 478mb
Some key Export improvements from the readme (I’ve underlined points of interest): – The functionality for creating and using user-defined property sets has been greatly enhanced. This includes: – Added a “DefaultUserDefinedParameterSets.txt” file to allow a user to create user-defined property sets for any setup, including the in-session setup. – Added the “IFC2x3 Extended FM Handover View.txt” user-defined property sets file to the installation. This also fixes a typo in the original version. – Allow the user to specify any file as a user-defined property set file, instead of being forced to use the default name and location. – Increased the types of fields that can be used from the original 4. The full list is detailed in the DefaultUserDefinedParameterSets.txt file. – The Setup dialog for the export alternate UI has been split into 3 tabbed pages to make it easier to find and understand the export options. – Significantly improve performance when trying to export a highly-tessellated geometry. New Import Functionality:
– Add an “IfcMaterial” field that contains the material name(s) associated with the element. – Add an “IfcSpatialContainer” field that contains the name of the project, building, building story or space that contains the element. – Create multiple layers for simple cases of elements where IfcMateralLayerSetUsage is defined. – Import IfcGrids. There are some fundamental differences between IFC and Revit Grids, most notably that IFC grids are per-view, and Revit Grids are per-model. As such, there may be cases where some grid lines show up in more views than initially designated in the IFC file. – Improve healing and logging of imported solid data that is slightly dirty. This should result in fewer missing objects.
Import Bug Fixes: – Fix “missing” faces when elements were cut by openings and the IfcOpeningElement sub-category had its visibility turned off. – Handle unbound circles used for profile definitions in certain cases.
Interestingly, this hotfix comes in the form of a macro to clean up your files. The issue as stated on the Autodesk Knowledge Network is: In Revit 2015 the performance of some file is very slow. This means that opening material browser may take an extremely long time or Revit will hang. Typically you cannot execute the “Purge unused elements” command as well, because Revit will freeze. … Every time you edit a family and load it back in > overwrite > the number of materials will grow substantially. For example after 5 or so subsequent reloads in our sample file it jumps from 15551 to 186623 materials. … We have seen this most commonly when editing titleblock familes in the German and Japanese version of Revit.