Revit 2024 - Rhythm.Revit.dll not loading

Packages
1

After installing and uninstalling numerous times and confirming Rhythm otherwise works in other Revit Versions, I’m at a loss for how to further troubleshoot why the Revit Nodes for rhythm refuse to populate in my RVT24/Dyn2.19 deployment. I do not have administrative access so disabling add-ins is going to be a session with IT thus I’d need some pretty strict marching orders so I don’t break their patience.

I feel certain it was working previously but possibly I was only in RVT23 and I’m just discovering the issue with RVT24. the only Recent Addins are Collaborate, FormItConverter, and TotalCarbonAnalysis; the latter two of which I could safely disable if they are really expected to be the issue.

2

Can you confirm which build of Revit 2024 (which will subsequently tell us which D4R version), and verify that Rhythm is in the right Packages folder for that one?

Im in Revit 2024 right now (2024.3, with D4R 2.19.4), and Rhythm is there and working correctly.

3

Revit Version 2024.3.4 with D4R 2.19.3 and the files install to the 2.19 folder. Installation goes fine and all the files appear to be there but when the Revit nodes are not listed in the tree in D4R.

4

Attaching Dynamo Log

dynamoLog.txt (265.4 KB)

5

Have you tried closing revit fully as well, then going to the package folder and fully deleting Rhythm before trying to re-install?

C:\Users\ADD USERNAME HERE\AppData\Roaming\Dynamo\Dynamo Revit\2.19\packages

Also reinstall the latest version from the package manager and not the same version installed in revit 2023(eg dont copy and paste from earlier version of revit)!

1 Like
6

Yes, I have fully closed Revit. deleted the package from the appropriate directory, opened Revit, installed from package manager, fully closed Revit and finally reopened Revit to use Rhythm.I do now get a Revit tree entry with a very limited number of nodes, only one of which I actually need (Select Elements from Link) which appears to work in that a selection is made but then it pukes out a dereferencing non-pointer error and all the output values are Null so it’s functionally useless.

7

After removing all packagaes and loading Dynamo clean I still get 3 errors, all the same, involving System.Collections.Immutable being loaded as an incompatible version by Procore.Plugins.Revit and Autodesk.Extensions.

Dynamo has detected a conflict with a dependency and may be unstable. If any issues are detected, please uninstall addins or packages and contact the provider.:
While loading assembly DynamoUtilities, Version=2.19.3.6394, Culture=neutral, PublicKeyToken=null, Dynamo detected that the dependency System.Collections.Immutable, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a was already loaded with an incompatible version. It is likely that another Revit Addin has loaded this assembly, please try uninstalling other Addins, and starting Dynamo again. Dynamo may be unstable in this state.
It is likely one of the following assemblies loaded the incompatible version:
Procore.Plugins.Revit, Autodesk.Extensions

Is this an error of true concern?

8

Yes, I would be concerned by it.

Have you disabled ALL of your Revit Addin-ins?

9

No, I’m going to have to engage IT for that. To date I’ve been trying to make sure it wasn’t anything else. I think it’s time and these errors suggest those 2 add-ins. The main issue I’m having at this point is that those 2 add-ins are mission critical. Additionally, they’re widely used across the industry so it seems reasonable for Rhythm to jive with said add-ins? More importantly, if these add-ins were the actual issue a whole lot more people would be complaining.

10

Which addin’s are they?

11

The Procore Plugin and Autodesk Extensions

12

Both might need an update.

Try this:

  1. Close Revit, start a new Revit session, get to the Home Screen, and force quit.
  2. Open the journal from that session (latest file) and search for ‘API_E’.
  3. Make note of any add-ins (not standard Autodesk components) which conflict with anything other than Revit API 24.X instead of 24.0. Those should be addressed.
13

Select in Link nodes were removed from Rhythm because of issues with compatibility. So those nodes will no longer show up in the library.

They are obsoleted here:

In Dynamo there are now nodes to collect elements from links. Use those instead.

14

I fully and completely uninstalled Revit 2024 as well as all Packages. I reinstalled Revit 2024. I was able to open Revit and Launch Dynamo with zero errors. From this blank canvas, I installed only Rhythm and the same 11 errors and limited node tree presented. I spent several more hours removing global plugins and the built-in add-ins to the point that there were only 5 essential add-ins for Revit/Dynamo to even launch. Even in this minimal state of existence there were always the same 11 errors and limited node tree.

Everything works great in Revit 2023 which makes me doubt it’s some other offending software. At this point, I am forced to begin rewriting my graphs to disuse Rhythm as that’s far more efficient than this wild goose chase.

15

As for the desired nodes being removed; I get the exact same issues installing the prior version of Rhythm that the graphs were originally written in.

16

If you were to build a tool on Windows XP, and then try to run it in Windows 11, it likely would t work. Similarly just because it worked in Revit N doesn’t mean it will work in Revit N+1.

ALL parts of he environment have to be built and configured for he new base (in this case that means Revit 2024, but it could also mean Revit 2024.1, 2024.2, 2024.3, 2025.0, 2025.1, etc.).

Go back to the blank state, recreate the issue, and then post your Dynamo preferences file, log from the recreation session, and Revit journal from the recreation session.

My guess as to why you aren’t getting full nodes in Rhythm is that something in your organization’s infosec policies is preventing download. Only way to confirm is getting the info above, reviewing the data, and then doing additional troubleshooting based on what we learn.

17

I think we agree. I meant to say that if it’s working in 2023 then there’s likely not something like my VS.Net install mucking the libraries on the overall system. While the Infosec policies may well be the culprit, it does seem like they would interfere in 2023 as well.

I can go back in the Logs folder and give you the clean slate install Dynamo launch log pre and post rhythm; they are attached.

dynamoLog_clean install pre-rhythm.txt (8.4 KB)

dynamoLog_clean install pwith only rhythm.txt (123.3 KB)

18

Rhythm is failing to load, as noted in the log. So either this is the wrong version of Rhythm, or there is something else which has loaded the wrong version of seemingly everything Rhythm uses.

So… How are you installing Rhythm? Note the package is not version portable so you need a clean install for each release. Best way to fix it is to uninstall from Dynamo, restart Revit, and install the latest version of the package from Dynamo’s package manager. There is an extension in Rhythm which will then go to the package’s GitHub and install the package version that is built for the Revit release you are using. Copying the package from another installation that is targeting a different Revit release can cause issues similar to what you are seeing here.

19

I am using package manager to install and deleting the Rhythm folder from Packages to uninstall. That’s infrequent, though as I’ve not seen much reason to remove Rhythm as it would be reasonable to assume all the right pieces are in the Packages folder and it’s something else causing the DLL to not load. Uninstalling from Dynamo also just removes the folder.

Is it possible the package manger process is reporting the wrong version or somehow causing Github to send over the wrong Package? Is there any way to audit the Package folder to ascertain which target is being provided for?

20

I might’ve messed something up with a recent build. Let me take a look. I re added the sheets node last week because a user asked for it and I probably messed up something.