Have you moved to Revit 2018.3 or 2019?

[GallowayUS_com_RonAllen2]

Please reply with a comment-

Have you moved to 2018.3 or revit 2019?

Are you using the A360/C4R Document management Interface (Second Gen)?

What version(s) are you running on active projects now?

What versions are you planning on upgrading to and when?

[aRcHiTeCt.JM]

Yes. Now I have been working on REVIT 2019.01 with excelent results.

Rendering has improved with this version, at least my opinion, it's been faster.

happy with this release.

[barthbradley]

We are working legacy projects in 2016, 2017 and 2018. Our newest contract states 2018 deliverables. We typically take about a year to go production with new releases, but we do have 2019 installed and are working with it. Bottom line: depends on when everybody comes on board.  

[Viveka_CD]

Hi @GallowayUS_com_RonAllen2

Thanks for posting on the Revit Architecture forum.

Is there a specific reason as to why you are asking? Is your team interested in upgrading?

Regards,

[GallowayUS_com_RonAllen2]

We have 2018.3 and 2019 available in deployments, but the inertia of old school CAD mentalities and lack of a "Current software policy" are keeping us from keeping current.

I don't understand with the benefits and features and the amount of data and integration that is coming down the road why folks don't test upgrade and if successful - upgrade!

[barthbradley]

I still trying to figure out why my neighbor, who just bought himself a brand new 2019 Lexus, is still mowing his lawn with a rusty old manual push mower.  Such is life, I guess.     

[a_meteni]

Haven’t took the move to the industry collection yet, We still in BDS with Revit 2016 & just recently 2018.2 and I’m not sure about upgrading to 2019 in the near future.
Sadly,We’re not using BIM360/c4R in our projects due to strict company policies.

[GallowayUS_com_RonAllen2]

Trying to get a feel for adoption out there. I am a leading edge type pushing to keep software current after test upgrades go well for every new major and dot version.

Autodesk should have an Autodesk Dashboard that showed licenses checked out and in use around the world. (Great IOT project for Flexera liceses everywhere!)  

[SteveKStafford · Accepted solution]

I have and will continue to upgrade as quickly as possible. That written the following factors into the decision to upgrade every project:

• Our consultant's or client's version requirements
• Project delivery deadlines
• Migration Impact - such as BIM 360/Revit Server
• Time to evaluate and become aware of identified bugs or issues that put projects at risk
• IT implications - hardware/OS/networking
• 3rd Party Tool dependency and their support/readiness for the new release
• Features that our projects will/could benefit from
• Performance improvements in latest release

What other firms do that I don't work with are of little concern to me (just like all the firms that don't use Revit) unless they know something about the new release that I don't that affects the above. If they don't say so in a way I can see it (like in a post here or I know someone that works there) then it can't factor in. This kind of knowledge is why people attend conferences, to mingle with their peers, people they might never work with directly or have that kind of conversation.

[barthbradley]

---

@SteveKStafford wrote:

This kind of knowledge is why people attend conferences, to mingle with their peers, people they might never work with directly or have that kind of conversation.

---

Sometimes it's just for the freebies too. 

[GallowayUS_com_RonAllen2]

Is there a particular reason why I would ask about who is upgrading their #Revit software and what #Versions they are using?- As fuel to "#KeepSoftwareCurrent" : )

When Carl Bass was CEO - there was a feeling that we could accomplish everything and that we were all working together. I was all for the subscription model- and if everyone keeps current we could all work together,
but,
now I fear under the new CEO- Autodesk has returned to focusing on the shareholders and the 'incremental release' strategy Apple employs... Back to previous days that drove architects and engineers to wait a few years before upgrading to maximize investment and ROI... The bleeding out innovations and advancements slowly rather than all at once will genuinely drive Revit users insane, and drive newcomers to other platforms. Under Bass- we came so far- even so far as to get Bentley developing again 😉

I understand limited resources and complexity in coding and shifting to the cloud. I also understand that if any discipline that gains features, operability, or process enhancements can only *gain* those enhancements in a non-backwards compatible platform, when *all* the other disciplines migrate to the next version. It is still a hard sell - working *against* us as so many of our users are stuck in the 'buy a version and wait 3 years' mentality or 'Last years version works fine' reasoning even though we are burning money on subscription across our large multidisciplinary firm.

I hope this is not the case; I am hoping it is the integration of acquisitions like Assemble and cross integration with other tools like Bluebeam originating the slowdowns.

But what I have been reading concerns me. We need to move away from the corporate closed off mentality and pick up a more #MillennialMentalityOfWorkingTogether on the problems and advancements of our tools, and then leverage those tools to the hilt to solve the worlds problems. If we as individuals, or as professionals in Architecture, Design and engineering cannot solve global problems- we're in trouble.

In the meantime- we take it one issue at a time and I will do my best to keep everything moving forward.