Revit changes extensively with each version, adding elements and parameters that not only add functionality, but form connections with existing Revit elements that have been upgraded from previous versions. While it might be possible in some cases to downgrade a new element into a previous version of Revit, at best it would arrive in the previous version as dead geometry. All of its behavior would be dependent on the more recent version of Revit. All behavioral relationships established to other elements in the model would also be broken, resulting in unpredictable cascading behavior which would likely the compromise the integrity of the model. A round-trip through a previous version of Revit would, at best, return a model that was substantially different from the model generated in the later version.

Tips: Before upgrading any project to a new version of Revit, be sure to:

Save a backup copy in the previous version.
Verify the entire project team is upgrading at the same time, including outside consultants.
Communicate with the team about upgrading and upgrade timing.

You can run concurrent versions of Revit on the same machine. ie Revit 2011 and 2012 can run on the same machine.

Comments

Comments6

pattygaleMon Apr 25, 2011 5:31 amThis information was contributed by davissc.
-- Patty Gale, Autodesk Revit User Experience Team
simon.whitbreadSun May 8, 2011 5:36 pmOk, so you would like to work with previous versions of Revit, which is kind of not going to work, or is it?...

Scenario: Architect is using Revit Architecture 2011, Sevices engineers Revit MEP 2012.

Its quite obvious that the Services engineers want to use the lastest tools available in Revit MEP 2012, but they could be held back by the Architect. This is true in the traditional workflow, but consider this:

The MEP engineer receives the 2011 Revit architecture file and upgrades it to 2012, saves the file and then uses it as a link. The architect then asks for a copy of the MEP model for coordination and / rendering purposes, but they cannot read the 2012 file format.
The current options are:
Export MEP model to - DWG (not ideal, you can only do clash detection with the entire MEP model), FBX - great if you are using 3DS MAX. If you have Navisworks installed, you can export to NWC, but that only works with any full version of Navisworks, not Freedom.
There is another option though, and one that isn't given a great deal of attention. This is IFC export. IFC has been used for collaboration with other files formats and software vendors, so why not within the confines of Revit itsself?
A few limitations will become aparent fairly quickly: Many elements will turn from nice system, or loadable families into in-place familes. A lot of the 'intelligent' data is lost in the process, and in the case of new categories in the newer Revit file format, these can either disappear completely, or if you control the IFC mapping, the new objects can be mapped to say the 'Generic Category'.
This isn't a perfect process, but one that does mean you do not need to be using the same Revit version as your collaboration partners.
KDolleyMon May 9, 2011 6:12 amThanks for the collaborative tip simon.whitbread.
-- Kevin Dolley, Autodesk Revit User Experience Team
createjbFri Jan 27, 2012 7:02 pmWhat a pathetic bunch of bu-raw.
AdonisRatifyOneWed May 9, 2012 8:11 amAll right people... time to include the ability to "save as" a previous version. I mean Autodesk designed this program... THINK IT THROUGH A BIT!!
KDolleyWed May 9, 2012 8:36 amThanks for the comment!
Suggestions such as this are best made with our feedback form (http://autode.sk/dfY9IE). That way it will be formally recorded and tracked. Thanks again for letting us know.
~Kevin Dolley, The Revit User Experience Team

Revit

Community Scoring

Tag Tags9

Page statistics

Revit Backwards Compatibility

Table of contents

Comments6