After reinstalling revit 2023
this error popps every time I open Dynamo
and I tried to update the packages and for some packages it work. BUT rhythem and Orchid.
any suggestions?
all
For Rhythm:
- Uninstall the package, then close Revit.
- Restart Revit and launch Dynamo again.
- Open the package manger, download the latest version of Rhythm, and install that.
You should be good from there.
For Orchid you will have to reach out to the package author, as they don’t leverage Dynamo’s package manager so ‘how to’ steps aren’t known to me, nor discussed on the forum.
1 Like
Thank you.
already done.
I did it again and still it not working.
I ask it github about Orchid, he replay-
“If you’re having an issue with Python, please seek assistance on the DynamoBIM forum. I don’t use Python in my nodes—I only develop using .NET languages (C# and F#). From what I can see, you’re combining four different packages, and some of them are Python-based, which is where I would start troubleshooting.
That said, I don’t see any indication from your description that my nodes are causing the problem. Therefore, I’ll close this issue for now until you can provide an example that demonstrates a failure within my nodes.”
and Im stuck.
Once orchid and Rhythm are installed those nodes should run.
What is the issue you are facing once those are installed?
Honestly these days I would advise only using Orchid for Dynamo unless absolutely necessary. As you gauged from Erik’s reply, he can be rather difficult to get help from unless you already know the answer to your question. I built what I see as superior family management nodes if you’re using it for those, partially because I couldn’t get Orchid to work, and partially because I got tired of the friction Orchid caused for forum users.
Rhythm looks to be an old version, you might need to replace the nodes on canvas with newer ones from the latest Rhythm to get rid of that message if it thinks the Python code comes from Rhythm.
You may be better off reinstalling the packages and rebuilding the script too, to see at which point the issues occur specifically.
Looks like your still missing Orchid (
).
If you can share your .dyn i can check if i get warnings too.
@GavinNicholls
I was always under the impression it is best to install the package matching your Revit version.
Am i wrong here?
(looks like OP works in Revit 2023
and has Rhythm for 2024)
Rhythm is the exception, as @john_pierson has put some significant effort into building an extension for his package that when you install it there is a tool which runs in the background to fetch the latest version for your Revit release, and put that version of the DLL in place.
1 Like
I did not know that.
Not all heroes wear capes.
2 Likes
Each package manager managers their packages in different ways. Some like archilab manage multiple versions that the user has to pick from, John has a dynamic installer, Orchid just says go to my github here’s a package with a node to it etc.
In my case I test to ensure my nodes work between a certain range of versions, and then say if you run Crumple outside these I cannot guarantee it will work (currently 2023-2026). I’ll likely be having to line in the sand quite soon and only support 2027 going forward for new releases given the Python changes coming then.
2 Likes
Hi @GavinNicholls if your nodes now run in cpython 3 it should easy run on pythonnet 3 as well as i understand it…but i have probably total misunderstand as usual…
i have just test my cpython 3 to pythonnet 3 and seems it doesnt work direckly without some modify for some of them…i test in 26 but i understand the frustration if it give again very much work as it was from ironpython 2.7 to cpython 3 / ironpython 3/pythonnet 3…but lets see whats happend when 27 is out…
2 Likes
PS and lets hope we then stay in pythonnet 3 for long time now
1 Like
The reality of Python is that frequent updates are likely a part of life going forward. This is the price which we all pay as BIM tools move from desktop applications to web connected toolsets.
1 Like
Here is a little info on the why and the how for Rhythm’s installation method.
3 Likes