Strategy for R2025 - are you changing your upgrade plans based on the R2024 schema-error experience?

Strategy for R2025 - are you changing your upgrade plans based on the R2024 schema-error experience?

HVAC-Novice
Advisor Advisor
549 Views
5 Replies
Message 1 of 6

Strategy for R2025 - are you changing your upgrade plans based on the R2024 schema-error experience?

HVAC-Novice
Advisor
Advisor

This is mainly for people or companies that usually upgrade to the new version relatively soon. I usually do that as well.  As you know, in R2024 there was a schema-error that (hopefully) will be fixed now with 2024.2 (released on 11/8/2023). I still want to have the "new features and old bugs fixed". So, I don't want to use very old versions for ages. 

 

If I had known about the schema issues, I would have waited for SP2. but this isn't information available to us beforehand.  Would have, should have, could have.... 

 

My initial thought was to wait till 2nd SP (R2025.2). But R2021, 2022, and 2023 never had an SP2. So that isn't a good strategy. 

 

My second idea is to wait till "SP1 + at least one patch" and scan this forum to see if there are issues. If no one reports issues, then upgrade to R2025 + all SP and patches.

 

Third idea is to just wait till around November, scan the forum, and then just assume all is fine and upgrade to R2025 very latest version. 

 

What are your (updated) strategies for R2025 deployment?

Revit Version: R2026.4
Hardware: i9 14900K, 64GB, Nvidia RTX 2000 Ada 16GB
Add-ins: ElumTools; Ripple-HVAC; ElectroBIM; Qbitec
0 Likes
550 Views
5 Replies
Replies (5)
Message 2 of 6

ToanDN
Consultant
Consultant

I upgraded every two versions minimum, and only after a major service pack released.  I don't want to be a test mule.

Message 3 of 6

HVAC-Novice
Advisor
Advisor

So you do 2022.1, then 2024.1 and skip 2023 entirely, for example? 

 

Do you still apply all patches after you have jumped to the new version? Or if it is stable for you, you just use as-is till the next actual upgrade? 

 

I just realized the past versions still provided updates for about 2 years. So, there won't be a final version for a long time.  I'm probably too impatient to wait 2 years.  

Revit Version: R2026.4
Hardware: i9 14900K, 64GB, Nvidia RTX 2000 Ada 16GB
Add-ins: ElumTools; Ripple-HVAC; ElectroBIM; Qbitec
0 Likes
Message 4 of 6

ToanDN
Consultant
Consultant

@HVAC-Novice wrote:

So you do 2022.1, then 2024.1 and skip 2023 entirely, for example? 

2013.1 - 2016.1 - 2019.1 - 2022.1 - 2024.1 (it was supposed to be 2025.1 but 2022 was bad with importing Rhino model so I had to upgrade sooner than planned).

 

Do you still apply all patches after you have jumped to the new version? Or if it is stable for you, you just use as-is till the next actual upgrade? 

Yes, apply all patches.

 

I just realized the past versions still provided updates for about 2 years. So, there won't be a final version for a long time.  I'm probably too impatient to wait 2 years.  

Most if not all users are like that.  That's why we have plenty of posts complaining about new versions screwing up their projects.

 


 

Message 5 of 6

HVAC-Novice
Advisor
Advisor

Oh, so basically 3 years for you. 

 

I have the suspicion Revit may not actually fix all bugs, ever. But "fixes" them in a new release.  So a bug from R2021 may not ever have be fixed, but being taken care of in R2022 and so on. Kind of like they never solved that Rhino issue for you in R2022. 

 

Maybe I start by still staying with annual upgrades, but wait till end of the year assuming I don't hear of issues. That hopefully resolves all  major bugs, but also gives me whatever new features or other improvements the Service Packs provided. If I "hear" of issues, I may wait longer even.  This strategy should be a great (stability) improvement over my old "update asap" strategy.

 

I do like the small subtle (sometimes not documented) improvements we get every year. 

Revit Version: R2026.4
Hardware: i9 14900K, 64GB, Nvidia RTX 2000 Ada 16GB
Add-ins: ElumTools; Ripple-HVAC; ElectroBIM; Qbitec
0 Likes
Message 6 of 6

barthbradley
Consultant
Consultant

Depends on what you mean by "upgrade". We don't "upgrade" a project midstream and we don't use latest version for new projects until, typically, 12-18 months after the initial release.