Archi-lab.net updated for Revit 2025-2027

Packages
,
1

Hey everyone,

archi-lab.net has been updated on the Package Manager. It now supports Revit 2025, 2026 and 2027. Revit 2017-2024 are no longer supported, so if you’re on an older version, stick with what you have installed.

A couple of fixes worth knowing about:

  • Node tooltips are back. Released builds hadn’t been shipping the documentation file, so nodes showed up with no descriptions.
  • The Excel export conflict is fixed. If you ever had to uninstall archi-lab to get the out-of-the-box Data.OpenXMLExportExcel node working, that’s sorted.

Uninstall your existing archi-lab before installing this one. The DLL names changed, so installing on top of an old copy means Dynamo loads both and you’ll see every node twice. Uninstall, install fresh, done.

Also gone: ParameterGroupUi, UnitTypeUI and DisplayUnitTypeUI. They already didn’t work in 2025+, so no current graph should care.

About the version numbers

All three Revit versions ship under the same archi-lab.net package name, so the version number is what tells them apart. It reads year.day of year.Revit target:

2026.216.270 → built on day 216 of 2026, for Revit 2027

The last segment is the Revit year times ten, so 250 is Revit 2025, 260 is 2026, 270 is 2027. The extra digit is there in case a mid-cycle Revit update ever needs its own build. Eg. Revit 2025.5 → 2026.216.255

The practical bit: you don’t have to work any of this out. Dynamo only offers you builds your version can actually run, and the newest one it offers is always the right one for your Revit. Just take the latest one you’re shown. Just hit the magic install button in Revit 2025-2027 and it resolves the correct one. More info here: Discover the New Dynamo Package Management Experience - Dynamo BIM

The source changes are in review over at Add Revit 2027 support, drop Revit 2024 and earlier, add CI/CD by johnpierson · Pull Request #127 · ksobon/archilab · GitHub if you want to see what actually changed. Anything you run into, drop it here or open an issue on the repo.

Big thanks to @Konrad_K_Sobon for the package and for the years of supporting the Dynamo community.

image
image1280×863 94.4 KB

image
image1816×994 42.6 KB

2

I also wanted to add a bit about the versioning.

Versions older than the 2026.xxx.xxx line use the previous versioning schema.

Newer versions use this:

image
image1360×452 20.7 KB

3

That’s a nice versioning system… might use it for pickles once i ship v1.

Nice work on updating an OS package as well. Pillar of the community.

4

Definitely had to work around some dynamo package manager versioning constraints to land on it!

If I were starting fresh I would maybe consider,

Major.Minor.TargetRevitVersion
1.0.260 etc.

But I do appreciate calver as a basis at it does simplify things a bit.

Edit:
I actually use calver for Rhythm as well as it allows a user to make several updates easily

5

:partying_face:

6

Ah yes i did consider that also before seeing this. I guess sequencing lower > upper and stacking nicely in a sorted list of versions is the goal. Food for thought, thanks!

7

You are the best @john_pierson!