Archilab - Multiple Release Versions and graphs used across multiple versions of Revit

@Konrad_K_Sobon

I have a quick question regarding the multiple versions of Archilab you currently offer and how they may (or may not?) function within a graph that is used between different versions of Revit.

Basically I have graphs that are used for all of our current Revit versions in house. If I utilized nodes from your package that is for Revit 20, will it still work in Revit 21 and 22 assuming I have the correct packages installed for each version?

The main reason I ask is that I was just testing out a graph in 2021 and when I try to open it it fails to completely open and nodes end up not displaying (all I see are connectors). I opened it in 2020 and it appears perfectly fine. Archilab is the only package I have that has multiple versions that I need to install so it was my first guess but I could totally be wrong on this and it could be something else completely.

Thank you for your hard work on Archilab!

So this must have just been a weird glitch. I restarted my computer and the issue is gone. I should have tried this before posting. /facepalm

I guess I am still curious if there are any issues in utilizing nodes from multiple versions of your package or not though.

There shouldn’t be any for most of the nodes. The reason I have multi version releases is to handle changes in the API for Revit between multiple versions. Take for example the unit nodes. If you use them in Revit 2018, 2019, 2020 and 2021 you will be fine, but you will need to upgrade your graph to use them in 2022. You will need a different Dynamo graph for that version because APIs in Revit changed and I had to change the nodes in my package for 2022. Your older graphs would be missing nodes if you opened them in Revit 2022, and had archi-lab.net installed for that version (ending in “22”). There are just a few nodes in my package that have that issue though, so for the most part you will be fine using them all across all different versions. There are a few where you will have to carry different versions. Another example is Material API changes between 2018 and then 2019 forwards. Some nodes will break. Just FYI.

1 Like