I just thought of something after reading through this thread regarding packages.
Are there any nodes that you are missing that you used to use from packages that have “fallen off the wagon”? (While ignoring UI nodes for now)
If so, please add them to this thread and provide as many details as possible.
Eg.
Package:
Lunchbox
Node Name:
RemoveNulls
Details:
I used to use this all the time and my Dynamo life is way harder without it.
Depending on the responses, I can start to prioritize and add some of these to Rhythm, which is maintained and works for Revit 2020-2025.
Note: Commenting a node on this thread does not mean there is guaranteed development of said node. Rhythm is still a project that I maintain in my free time, which is harder to come by these days. So the idea here is to add quick nodes that people might be missing.
Nodes Added Already (this list will change over time)
You had an AWESOME node for selecting Sheets in Rhythm. Yours showed sheet name AND sheet number. Now that it’s OOTB it only shows Sheet Name, which is awful. I end up having to do a test run with a sheet.sheetnumber node right after, to validate that I have the right sheet. Minor, but rough. Hehehe
I used to use this once for put my Kinect wind veil facade geometry into Revit family.I’ve heard Dynamo team is working on the same function node as well.If they do you can ignore this one.
It don’t work in Revit 2025 but works well in Revit 2024，I have installed IronPython2.7 in both version of Revit.I think maybe the RevitAPI changes cause the issue.
So I build it in Revit2024 and then upgrade the revit file into Revit2025.
Here’s my original post.
And these are two gifs of which I did.
And for lunchbox node I use Panel.PanelQuad a l lot.This is the only reason I keep install the package everytime I install newer version of Revit like Revit 2025.But I have found my own way to split surface to construct quad points as well.However I still think it‘s useful for someone else.
Lunchbox is famous for it’s curtain wall panel function in Grasshopper as well.
At last thanks John I really considerate donate in the future for your kind work and sharing.But now I’m not in good economic situation.I’ll do when situation changes.
No donations required at all! I appreciate the reply.
FamilyInstanceByGeometry has an OOTB equivalent. Family type.ByGeometry. The downside is, you then have to place it with a family instance by point. Springs just works and is the one I used the most. I will take a look at that one.
The quad and panel nodes from lunchbox have OOTB variants and will be in Revit soon. So those I won’t address right now.
Curve.PointAtParameter might be a fit for now. I will note that while I haven’t seen it return different results than the start and end point nodes yet, but mathematically it’s possible these could deviate.
