This wild goose chase, helped highlight an issue I created recently. So I do appreciate it.
I recently pushed a fix for sheets UI that people were asking for, and added a new node. Sadly, I messed something up and the entire solution migrated to .NET10. This broke all sorts of junk which is not great.
Specifically, it broke the View Extension which loads the correct DLLs. So no view extension working = no Rhythm loading.
So I reset the repo to the last working version and will investigate further.
I just tested in Revit 2024.2 and Dynamo 2.19.3 to see if it is working and it is!
So (while inconvenient), please try removing the Rhythm folder, and installing from the package manager one more time.
Also, this is the only Link selection node I have in the package anymore, if this will work for you, cool. But the UI nodes are gone because they did not work very good.
It’s not really intended to be a slag on you. It’s more frustration with reality because I spent a solid 5 hours on the issue today and something like 3 hours yesterday. All told, chasing this out has been around 12 hours of billable time. My commitment to this has been because Rhythm has been an awesome Package since I first started with Dynamo several years ago. I develop solutions for the rest of our VDC team so I need solutions to have a degree of stability and repeatability. Having put forth this effort I have to consider in retrospect I could have just reworked the graphs in less time. I am still very interested in solving the issue and continuing to use Rhythm and very appreciative of its’ existence and your contributions.
Building and maintaining a Dynamo package is a lot of (unpaid) hours as well, so I do appreciate the patience. Give installing it another try, as it should be good to go now.
I definitely do recommend combing over graphs periodically as new OOTB nodes are added all the time, and using those over a package (when possible) is a good strategy.
Yeah, that’s the Node I was using. Getting a selection of Elements from a linked model to copy into thew host model is the basic operation of this particular graph.
I’m glad you were able to sort this out. I understand there’s a sort of series of steps users should be taking to ensure it’s not a problem on their end. In review, was there any way I could have gotten this issue to resolution with less friction along the way?
The first step is isolating the cause. Having a method to quickly clear ALL customizations is the easy way to do that.
I like renaming my Dynamo appdata folder to clear the Dynamo customizations. A new folder with a clean ‘first boot’ usually triggers from there (with a few exceptions). It’s also handy to build new environments to test in but that’s a separate thing.
For Revit add-ins, the built in add-in manager (or 3rd party one for older builds/consistency helps). There are also ways to manually rename stuff to prevent loading but I’m hesitant to recommend those as the GUI helps most users quite a bit.
Once the package is isolated, you need to confirm the issue is happening with a clean install of the right version. Getting the ‘right version’ for many packages is hard - you have to read the package description, version info, or worst case trial and error; but with Rhythm it’s easy as the newest is always right. From there if it still fails to load grab the Dynamo log, package info, the installed package version info, and Revit journal. Post all those here so the community can double check what you’re up to; we can usually direct you to the package author (if needed) from there.
Other than what Jacob said. I supposed one way is to follow the Github.
While looking at that, it might have been noticeable that I made a change in recent days in the commit history. So at some point it could have been like,
”Hmm, I do see a recent commit that revised the deploy files”,
