I followed @GavinCrump Gavin’s tutorial on youtube and found this thread. I recreated the script, however in the last step the floors don’t get created, the node only gives back null, even though the curves are closed.
I tried it in RVT25 (DYN 3.0.3) and RVT24 (DYN 2.19) had the same issue in both cases.
What am I missing? If it was only in 3.0.3 I could explain it with the .NET8 changes, but I’m lost.
Any help would be highly appreciated!
Guessing you’re using an unsupported version of Crumple. Try the out of the box node and a Element.SetParameterValue node instead.
Ah - didn’t see that you had such going on. Make sure you’re in the latest version of Crumple and it should work in 2024. Not sure about 2025 yet though.
It’s another test project I have 
Unfortunately, it doesn’t work in revit 24 either. I get the same null values. I tried with the Crumple versions 2024.4.3 and 2024.4.2
Post the test project and graph and I’ll try and have a look before I sign off for the weekend.
Evening @EV_92 ,
Try adding “FloorType.ByName” node here. Think its expecting list of types as opposed to list of strings maybe…
Actually check Gavins youtube video out again think you may have fed the wrong node in.
Can confirm this works for rvt 24 have not tried 25.
Cheers KS
if you provide the sample revit file with expected result i can try as well.
Most common reasons are using an older Crumple that uses IronPython for that node (latest doesn’t), and not having the IronPython package (version 2.5) installed. A lot of hoops to jump through, I know.
More than likely the list at the end is the wrong structure, it looks 1 level too deep to me. Should be a list of lists, where each object in the sublists is a list of curves. If you run the room.finishboundary node on a set of rooms it will be that exact structure.
This comes up quite often. Have tried to comment the inputs as well as I can, but Python nodes will often have pretty strict input structures to support iterations.
So,
I’ve re-installed the dependencies, re-done the script from zero. Some of the spaghetti was definitely connected wrong (like, c’mon…i thought I was thorough). Now it works like a charm. Thank you @GavinCrump for the amazing script!
In the end, the Floors.Create node still lists ‘null’ to the floors list, but the elements get created. I checked it in the original RVT22 version as well, it does the same (I guess it reads and prints something else than the created object).
Thank you all for the replies and help!
