Hey all,
i’ve been putting this off for way to long and am getting stuck at the moment.
Last year/begining of this year I made a dynamo script (which is pretty huge, with custom nodes and stuff) that i made in Revit 2022. Now that the script has advanced a bit more some would like to use it.
The “problem” is that the project they want to try it on is in Revit 2023. I believe I have found the source of my script not working. But I have no clue how to fix this…
I know there has been changes in a possitive way with the newer versions, but i am clueless on how to fix this. i’ve seen multiple topics with similar problems with different Nodes, but have yet to come to a solution.
I believe the Node StirrupPolycurveandlinefromTopBottomandLongsidefaces from PracticalBIM ain’t working. Because the Node is giving an error in my script i tried Disecting it. At this point I can see the script is returning empty lists at the geometry intersect Node.
Eventualy these intersections are used to create polycurves which are used to create various Rebars. I’ve no experience with Python, and I didn’t come a long way with ChatGPT… so I’m hoping someone here can push me in the right direction.
Below a screenshot of the full script and a list of the custom packages installed for this script. (I had to resize the screenshot of the script because it was too big, i hope it is still readable enough)
Hi @manonio - does the Stirrup… node return null? If so, given it’s a custom node, chances are likely that you can go into the Custom Node and edit the inputs or output ports. There will be a warning inside (Most likely).
Can you open that up (When it’s connected, and you ran it) and see if there are warnings inside?
Hi @solamour , Sorry for the late respons. was on a holiday for a couple days. I did indeed look into the custom Nodes. Maybe I didn’t describe that enough…
I’ve copied the custom Node within the script to see where the hickup was. There I found that the ‘Geometry.intersect’ Node is not working. it’s returning an empty list and no warning is shown. Because this list is empty the Nodes after are returning NULL. I have a feeling the Node used to work with surfaces, but doesn’t in the newer versions.
I’m going to keep trying, but if anyone knows a Node that I can use instead to either intersect the surfaces or to create the rebar that would be great.
If I end up with a solution i’ll post it here.
We didn’t change the node, and it should definitely work with surfaces 
Are you able to share your content? If not comfortable publicly, you can do so in a Direct Message.
@solamour i’ve send you the different files that come with the script and the script aswell. Can you let me know if you have received it all correctly?
I hope you can help me a little in the right direction to making my script work again. Going to look into it a little further today hoping to find something
Edit: i’m going to look into the Revit project file now… I’ve upgraded my test file from 2022 to 2023, updates Revit and stuff and there it works fine now… I guess I needed a good night rest before thinking of testing this first.
So no I guess it will be a “look for the differences” but then in Revit i guess 
I’ve found the problem within the project… Were i tested the script the geometry was not connected/joined to anything. For some reason the script does not seem to work well with geometry that has been joined with it.
My guess is because the script tries to read out the surfaces of the object, but they are not connected because the joined geometry is also taken in account as a side…
1 Like
