This doesn't happen too frequently but it does take us to our licenses limit at least a couple of times a month. As we move to newer versions of Revit, if we don't have users using the same version of AutoCAD, then whenever they have Revit and AutoCAD open simultaneously, they are consuming two network licenses instead of one.

At that point at least if we're pushing other firms to upgrade I'll know why.įor us, the main driver for upgrading AutoCAD is licensing since we are on a shared network license with Revit. I expect by next years relseases I'll have lot of my bigger problems out of the way so that we can really focus on what the new versions provide and leverage those changes. I've only been here 5 months, prior to that rolling out new versions was an expensive 'project' with our consultants. I figure I won't start pushing it out just yet so that we're not the 'problem' firm. I'm ready to go once we start needing it. Likewise, if you're collaborating with a different office and they're using 2013, you'll need 2013. So save a project in a new version and you're stuck there. The biggest difference is you can't easily move backward between versions. I already have my licenses and a basic deployment built waiting for me to decide to spend the time on the roll out. I think the 'wait for the first service pack' is probably a little out of date with the past few years, but you don't run into pressing reasons to upgrade. A lot of the changes are related to the cloud features and there's a new file format, of course. From what I've seen not much has changed since 2012, and not a whole lot changed since 2011. We are using AutoCAD 2011 and I'm planning to upgrade to 2013 'when I get around to it'.

Autodesk revit 2011 service pack