Revit 2014 Update Release 2 has been posted to the Autodesk Revit product pages:
- Revit 2014 Update Release 2
- Revit Architecture 2014 Update Release 2
- Revit MEP 2014 Update Release 2
- Revit Structure 2014 Update Release 2
As usual, the update release uses service pack technology and does not require a full install.
Prior to installing the Update Release 1, please verify that you are running the First Customer Ship build of Autodesk Revit 2014, build 20130308_1515 or the Update Release 1 for Autodesk Revit 2014, build 20130709_2115.
After the update, the build number specified in the Help > About dialogue will be 20131024_2115.
For your convenience, here are direct links to the English 31 Kb readme file and the 223 Kb enhancements documentation.
A link to update is also built right into the Revit product itself.
No pure API enhancements are officially listed, but it does fix at least one little and one big issue that developers have reported in the past:
- The Revit API LoadFamily method can throw an exception saying "External component has thrown an exception" when loading a family created from the Revit 2014 first customer ship version of the Generic Model template. This can be avoided by using the Revit 2013 template instead, or the one included in this update release.
- When a custom Dockable pane is registered using the UIControlledApplication.RegisterDockablePane method, the Revit document now closes when the last document view window is closed. Thanks to Phillip Miller for pointing this out! One report of this problem was by Luca in his comment on the simpler dockable panel sample.
A significant product enhancement is discussed in depth by Ian Molloy, Senior Product Manager of Building Performance Analysis, who lists a number of important improvements to automatic energy analytical model creation using Revit building elements.
It also seems to fix the problem if an addin was registered using the Dockable framework, when closing the last view of the document, the document actually now closes. Previously it didn't. You had to close it through the close button accessed from the Big "R" in the top left corner.
Posted by: Phillip Miller | November 12, 2013 at 17:17
Dear Phillip,
Oh, brilliant, thank you very much indeed for picking that up.
It completely slipped my mind.
Certainly the most important enhancement that I am aware of for add-in developers.
I'll add this above in the main text as well.
Cheers, Jeremy.
Posted by: Jeremy Tammik | November 13, 2013 at 02:45
Hi Jeremy,
since UR2 the doc.Create.NewFloor method returns an error about unsatisfying geometry in the CurveArray i am using. But in UR1 the same method worked fine for the exact same geometry. So i was wondering about the curve order and used your SortCurvesContiguous() without success. still unsatisfying geometry. writing the curvearray directly as modellines works and looks correct. any idea on this?
regards
max
Posted by: max | February 25, 2014 at 13:13