Hello, i am just starting up dynamo after being a long time user, node that I have grown to trust dont seem to be working at all. I just downloaded a brand new set of packages for everytthing in revit 2024 but some of them just dont seem to work at all. Particularly Springs nodes current selection or Data Shapes UI nodes. Is there something I am missing? I mean this one should just pick up my current selection. simple enough but it doesnt. I tried toggling on/off tried auto/manual tried running it mulitple times but it still says ânullâ even though I have things selected in revit. What am I missing? did i somehow install these packages wrong? Please point me in the right direction.
Likely missing an IronPython 2 dependency. This might be good as IronPython2 is now been 5.5 years since itâs last update which makes it completely and horribly insecure. Moving to a supported Python3 package is recommended.
You may also have installed a Dynamo 3.0 package in a Dynamo 2.0 environment. This could eve for the primary package or for a dependency such as IronPython2.
The package may also not have been updated for one of the many API updates which happen in any given year.
Which of those is as play isnât knowable with what you have shared. Try editing the custom nodes and see if any useful warnings show up. You can also check the Dynamo log file and Revit journals to see if any mismatches or conflicts are noted there.
Getting the right environment configured is hard, doubly so when it has been awhile since you last did so.
Worth checking the dates when packages have updated before you install as well. Some packages havent been updated for a long time, and revit has changed from net framework to core so this will have impacted some zero touch packages and python engine changes have impacted py ones.
I generally assume any package that hasnt been updated for at least 6 months or so might happen to work, but isnt guaranteed to and depending on it will become a risk over time.
Some packages have aged very poorly due to not keeping up such as steamnodes and bakery. Minimize package use to what you need, and if youre using a mega package for 1 or 2 basic nodes consider using python in lieu of them.
Hi Jacob,
I looked into dynamo versions and went to update to the latest version but what I found out makes it sound like you cant just download and install a new version of dynamo when you want to anymore. Its locked to the version of revit you are in. Is that accurate? I am in Revit 2024 so the version of Dynamo I am using is 2.19 (see below) I wouldve liked to have 2.5+ because I heard they got rid of the memory leak but I would also prefer not to fight with a bunch of install âworkaroundsâ I would just like to use one version and it to work. Please let me know how to research my ironpython2 dependency if I need to or not. I am not sure how to do that. Ill try cracking open the custom nodes and looking under the hood though. Thats a good idea. I havent tired that yet. But please let me know if i need to and how to move to python3 dependency. Much appreciated.
Correct - the only way to update Dynamo for Revit is to update Revit. Youâre in what is likely the last ever build for Revit 2024 (barring a security issue). It is also the 20th version of Dynamo 2, which is newer than the 6th version (2.5).
The information about version requirements for the IronPython2 package can be found in the package description - check it there.
Troubleshooting specific nodes requires specific troubleshooting steps - there isnât a âeasyâ button for resolving the issues without figuring out what the issues are first.
First make sure the package version you installed is correct for your Dynamo and Revit build - this is done by checking the details in the package manager. If you have the wrong version, uninstall it, relaunch Revit, and install the right one.
Next you need to identify node failures.
For zero touch nodes this will usually require reading the warning and coming to terms that you either have the wrong version or that the package is not supported anymore.
So in the case of a .DYF node (custom nodes you can open up by double clicking), double click them and see if any warnings show up. If there arenât any, copy the contents to the clipboard, swap back to your other workspace, and paste the copied nodes in. Wire inputs in and figure out what is going on. It may be that one of the nodes changed, or that some incorporated Python needs an update, or that one of the nodes it needs is from the wrong package version.
All of this is to say the community can help with specifics, but youâre going to have to do the legwork to expose the specifics you get stuck with.
@jacob.small understood and all of that makes sense. except for the part about making sure the package version is correct for my dynamo and revit build. That information is not available in the descriptions and their âversionsâ do not correlate with revit or dynamo version at all. See below. So how will I ever know if I have the right version or not?
This seems like an example where the package author posted a one node package and didnât provide any information for the version. Typically these should be avoided as they are almost never maintained.
In this case you can likely use PolyCurve.ByGrouped Curves as a replacement, which is an out of the box node now.
Each similar case will require a similar review.
For an example of packages with description information, check out DynamoForFormaBeta, TuneUp, and DynamoIronPython3.
@jacob.small I got the data-shapes able to run once I had the right version of python assigned to it. But the buttons on it are super big. They used to be much smaller, now they run the full length of the window overlapping the button discription. Is this something that got messed up when I was fixing the python version or does it âsupposedâ to look like this now?
Looks broken to me, but I havenât used the package for quite awhile. Make sure you have the right version of Datashapes, make sure it isnât edited and direct from the package, and modify inputs to see if you can ID a setting.
