Revit Wants The Whole Team On The Exact Same Revit Version February 10, 2017January 1, 2018 Luke Johnson This has been a ‘best practice’ rule for a while now, but it still applies, even in 2017. You should not mix Revit 2017.1 and 2017.2 on a single Central File. This was flagged by pepar in the BIM Experts Slack Group. This Bakery node or the Revit Properties extension may assist you in checking Revit build. Share on FacebookTweetFollow us 0 0 votes Article Rating Related Posts:Imported CAD file does not respect view depth and…Revit Zero is not the same as Project Base PointUsing aliases to simultaneously access the same…Multiple Revit Instances when working on the Same…How to Workaround A360 SSO issues by Running another…A View Template cannot have the same name as a View Post navigation Previous Previous post: How To Use A Temporary Point Cloud Transformation To Maintain Accuracy in RevitNext Next post: Free Tool to Compare Revit Models And Visualize The Differences Subscribe Notify of new follow-up comments new replies to my comments Connect with: Label {} [+] Name* Email* Website Δ Connect with: Label {} [+] Name* Email* Website Δ 0 Comments Oldest Newest Most Voted Inline Feedbacks View all comments
