Hey everyone,
Quick question:
Can it cause any issues if different person that are working in the same model has different version of Revit? In our case we have revit 2018. On my workstation i have 2018.3.2 but others still have the original 2018 version.
For the moment nobody has issue, but does the fact that we don't have all the same version cause issue in general?
Thanks,
JP
Yeah, that may cause issues. If people start crashing a lot that is most likely the culprit. Most company standards to Revit installations is that everyone is on the same version. This is why many disable the Desktop App and disallow access to updates.
Why isn't everyone else updated?
Thank you for taking the time to answer.
I guess not everyone checks if there's a new update on the desktop app. That's why we don't have all the same version.
Thank you!
IT or your Revit Lead (When you don't have a BIM Manager) should be keeping track of all that.
Okay i'll make sure we keep track of it, thank you.
Is it a good idea to update as soon that a new patch comes up?
Should we wait a little?
You said it can cause issue, did you mean on the workstation not updated itself it can causes issue (like crash or slow process)?
We are mostly worried if it can create any problem in the central model?
So when I first started with my current position everyone pretty much worked on their own projects...no big deal. Then they started working on a workshared project and that is when people noticed Revit running slow, or crashing the program and losing work. After going around to all the workstations I found a few people running first release and some a few updates later. I updated everyone to the same version that night. I also told everyone to start with a fresh local file every time they open Revit and not open their local file everyday. Problem solved.
As for updates, I never install right away. For example I still haven't installed 2020 as I wait a few days to see if there are issues, and there were. Point updates are project driven. I'm currently holding all projects in 2019 to .1 as that is the set version for a BIM 360 project I am working on so .2 is on hold until the team I am working with updates.
Oh i see thank you for your answer.
Okay I understand for a new yearly revit update (2018, 2019, 2020, etc) but what about the Hotfix like 2018.1 and all? Are they safe to install right away?
Thanks a lot, and i'll make sure everyone is updated now.
As previously mentioned it’s best to be on the same version as errors with translating info can occur. Maybe ensure everyone reads the BEP prior to commencement.
hope this helps
Not being on the same build will almost always lead to some sort of model corruption. You can look at the journal file to see the history of the versions in which it was saved. Here's a snippet from one journal and you can see the 2017 versions jump all over the place. This was part of why the user was having issues with their model.
' 3:< Document save history --> :
' 3:< Revit 2014 2014 (2014.000) : 20130709_2115(x64)
' 3:< Revit 2014 2014 (2014.000) : 20140709_2115(x64)
' 3:< Revit Architecture 2014 2014 (2014.000) : 20130308_1515(x64)
' 3:< Revit 2014 2014 (2014.000) : 20131024_2115(x64)
' 3:< Revit 2015 2015 (2015.000) : 20140223_1515(x64)
' 3:< Revit 2015 2015 (2015.000) : 20150303_1515(x64)
' 3:< Revit 2015 2015 (2015.000) : 20151007_1515(x64)
' 3:< Revit 2015 2015 (2015.000) : 20140606_1530(x64)
' 3:< Revit 2015 2015 (2015.000) : 20150303_0715(x64)
' 3:< Revit 2015 2015 (2015.000) : 20151207_1515(x64)
' 3:< Revit 2015 2015 (2015.000) : 20160220_1515(x64)
' 3:< Revit 2015 2015 (2015.000) : 20150702_1515(x64)
' 3:< Revit 2015 2015 (2015.000) : 20160512_1515(x64)
' 3:< Revit 2015 2015 (2015.000) : 20140903_1530(x64)
' 3:< Revit 2017 2017 (2017.000) : 20170118_1100(x64) 2017.2
' 3:< Revit 2017 2017 (2017.000) : 20161205_1400(x64) 2017.0.3
' 3:< Revit 2017 2017 (2017.000) : 20160720_1515(x64) 2017.0.2
' 3:< Revit 2017 2017 (2017.000) : 20160225_1515(x64) Initial release of 2017
' 3:< Revit 2017 2017 (2017.000) : 20171027_0315(x64) 2017.2.3
' 3:< Revit 2017 2017 (2017.000) : 20170816_0615(x64) 2017.2.2
' 3:< Revit 2017 2017 (2017.000) : 20181011_1645(x64) 2017.2.4
' 3:< Document save history <--
HOW TO TIE THE BUILD NUMBER WITH THE REVIT UPDATE
https://knowledge.autodesk.com/support/revit-products/troubleshooting/caas/sfdcarticles/sfdcarticles...
Matt Wunch
Revit Subject Matter Expert/sUAS Pilot
Twitter | LinkedIn
AU2017 - Code Blue Dr Revit - How to Resuscitate Corrupt Revit Models
Was this answer helpful? If so, please click the ACCEPT AS SOLUTION or the KUDO button.
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.