Autodesk Revit Architecture

[#1]

Does anyone know what Autodesk plans to do about the backwards compatibility issue with Revit?  I have Revit 2012 but I have to use Revit 2011 because the software is incapable of saving back a release.  This is total craziness!  Why would anyone knowingly upgrade with this being the case?

[#2]

There are no plans to make Revit backwards compatible.  Why would you not upgrade to 2012?  If its consultants, why would they not upgrade?  It's total craziness to NOT be using the latest release.  2013 products are coming soon...then you will be 2 releases behind. 

[#3]

Hi Scott,

That’s a very easy question to answer.  If I create a family in Revit 2011, it’s possible to use that family in Revit 2011, 2012, and so on.  If I create that same family in Revit 2013, only those who have that release can use it.  In order to stay compatible with the widest audience I have to work in an order version of the software.  Speaking for myself, I don’t know anyone working in 2012, and even if I did I would still be compatible working in 2011.  Clearly Autodesk has no clue how users really use the software.

This is a big problem!  I would like to see Revit become the standard for architectural design, but there needs to be a way to save files down a version. 

[#4]

Revit has been around for nearly 12 years now, and in north America, is the architectural standard.  Most users are on 2012, and if you aren't, well you are nearly a year behind and its time to upgrade.  If you really need to make families that are available across multiple versions, then simply build them in an earlier version.  I used to do it all the time when I was in arcitectural practice.  Autodesk is well aware of how its customers use its products.  Through the Customer Involvement Program, we even know what commands you use most often.

What it comes down to is communication:  communicate with your project teams, including consultants, and decide collectively what versions will be used for the life of the project.  Or decide collectively when you will upgrade.  On subscription, you can use up to 3 versions of Revit.  On subscription, you have immediate access to upgrades.  There really is no good reason why anyone should continue to use an older version.  Sorry, this isn't intended to come across as harsh, but its reality.  My job puts me in front of customers every day so I have experience in this subject.

[#5]

Hi Scott,

It appears we are talking about 2 different things, maybe because I’m not being clear enough on the situation.  First off, if you read my original post, I do have the latest version of Revit.  Second, I’m talking about family creation not projects.  If I create a family in Revit 2012 it can only be used in a Revit 2012 project which is a limitation.  But if I create the same family in Revit 2011 it can be used in Revit 2011, or 2012.  I want the families I create to reach the broadest audience.  I don’t think you understand the situation I’m in.  If I’m creating families in the latest version I can’t save down a version, I have to re-create the family from scratch in an older version.  This costs me money.

[#6]

This is how Autodesk forces people to buy the latest release.  Total craziness......

[#7]

Forces you to buy?  Most likely you are on subscription so new releases are yours already.  But besides that....no pressure.  If you want to continue using older versions with less performance and less functionality, thats your choice.

[#8]

A side thought... If you are on subscription with Autodesk - you do get previous version use. Since you have 2012 you can use 2011, 2010 and 2009. So if you needed to start your familyson 2009 and then use them in any version after.

For project work - it is a best practice I discuss with cllients that what ever version you start a project in - you finish it that same version. This avoids any issues with team members/consultants not wanting or having the finances to upgrade the software.

just my $0.02

LD

[#9]

My guess is that the OP represents a manufacturer of some sort, and is not actually in the architectural profession, so telling him to coordinate with the project team prior to starting probably isn't going to get him very far.  However, if you look at most of the manufacturer's out there, they tend to release their families in only the latest release, or at most, the current release and one prior release.  Since a vast majority of Revit users upgrade with each new release, having to provide content in prior releases just shouldn't be that much of an issue.  

Personally, I'd rather have every manufacturer's family in the latest release; that way I don't have to sit through the "upgrading family" whenever I load it the first time.

My advice to the OP: build your families in the current release.  Upgrade your entire library of families with each new release, but keep a copy of the older versions for at least 2 releases, in the event that some functionality is lost from one release to another (e.g. family painting parameter disappearing between 2011 and 2012).

[#10]

Your guess is pretty close.  I work with foodservice equipment manufacturers and commercial kitchen designers.  No one I work with uses Revit 2012.  I have a subscription as well as the latest version of Revit.  I created this post mainly to see if Autodesk has any intension to allow a user to save a Revit family back a revision or two.  According to Autodesk Scott, the answer is simply no.

I very much want to work in the latest version of Revit, but I cannot simply because the software does not have the capability of saving to a previous version.  Because of that limitation I’m forced to do all my work in an older version.

In my opinion, bottom line, if Revit could save families back a release or two it would give kitchen designers a reason to upgrade.  I also think it might give kitchen designers using AutoCAD incentive to try Revit.  If I were Autodesk I would listen to my customers, look for every opportunity, and not be so dismissive.