2009 vs. 2010

[greg.gebert978266]

Does anyone know where I can find a document that explains what was changed between 2009 and 2010? I hope it wasn't just the interface?

[clog boy]

Does anyone know where I can find a document that explains what was changed between 2009 and 2010? I hope it wasn't just the interface?

This page features known issues and feature summaries. Courtesy Revit.com (Autodesk's shortcut to their revit page)

[dpasa]

Mainly it was the interface and the new curtain wall panels.... Some small nice features but nothing much... and of course, nothing from the users wishlist.

[greg.gebert978266]

Mainly it was the interface and the new curtain wall panels.... Some small nice features but nothing much... and of course, nothing from the users wishlist.

PERFECT! Thanks.

[ntnik]

i was reading a few posts over the last few days.....have seen a few where 2010 seems to strike users as problematic ( is it big deal or should we just jump on in?).....we're a little slow here advancing to the more recent release.....concerning that issue (our slowness) i may be on the verge of creating a mistake, so i ask.....i havet a big project we executed in 2008....i have kept it there and seem to need to continuously update it as a result of changes, requests for supplemental details, etc. Do i need to go ahead and at least updat it to 2009?......or, am i ok keeping it in 2008?

[Andrew Dobson]

There is no technical problem keeping it on 2008. There may be licensing issues if you are not on subscription that you may have to clarify with your reseller.

[greg.gebert978266]

i was reading a few posts over the last few days.....have seen a few where 2010 seems to strike users as problematic ( is it big deal or should we just jump on in?).....we're a little slow here advancing to the more recent release.....concerning that issue (our slowness) i may be on the verge of creating a mistake, so i ask.....i havet a big project we executed in 2008....i have kept it there and seem to need to continuously update it as a result of changes, requests for supplemental details, etc. Do i need to go ahead and at least updat it to 2009?......or, am i ok keeping it in 2008?

My theory is that it is best to start and finish a project in one version. I know this can be difficult since projects can go on forever. I just feel this is the safest way of doing business.

[clog boy]

My theory is that it is best to start and finish a project in one version. I know this can be difficult since projects can go on forever. I just feel this is the safest way of doing business.

Absolutely, unless a new version has new features that would be of great value to the project. And then still with great caution.

[dpasa]

Since many people talk about upgrade or not, I must say that you must go to 2010, because Ribbon UI is here to stay so you should start using it....also, Adesk is changing the cost of updating the products for those that don't want subscriptions... it is getting expensive...
Revit 2010 is not bad.... it is just far from what we wanted and expected... that's why most people, me included, complain... there are some issues with the Ribbon but generally it is a good start of Revit's future... Maybe in RAC2011 we see the new form tools improved and in family editor too...or maybe we get a really great and updated mental ray inside Revit... and all the import/export options of Rhino... and the new graphite tools of Max for freeform modeling or maybe Acad's new tools and mesh object....
OK!OK! I woke up!... no more water!

[Phil Read]

Since many people talk about upgrade or not, I must say that you must go to 2010, because Ribbon UI is here to stay so you should start using it.

While the ribbon is "here to stay", it is not "here to stay put." You should expect the ribbon to change significantly for the next few releases as it will evolve due to user feedback. So learning it now may actually provide diminished returns resulting from having to relearn many times over what you could have learned once. Additionally, the allowance of significant user customization of the ribbon will prove most disruptive from a support standpoint. We will likely lock down the ribbon - but allow customization of keyboard shortcuts.

For this reason, we will remain in 2009 for the foreseeable future (and have advised our consultants and contractors to do the same - which they have agreed to do). Once the UI juggling settles down we will then consider moving to a later release.

If there were a "Classic" option we could have moved forward with this release - as well as beta tested the ribbon and provided more extensive feedback. Unfortunately this was not the case.

-Phil