# Join geometry node RVT 2024 **URL:** \ **Category:** Revit\ **Tags:** python, dynamo\ **Created:** [December 16, 2023, 3:11pm UTC](https://forum.dynamobim.com/t/join-geometry-node-rvt-2024/96456 "2023-12-16T15:11:48Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Andrej](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/andrej/32/172909_2.png) [@Andrej](https://forum.dynamobim.com/u/Andrej)\ **Post date:** [December 16, 2023, 3:11pm UTC](https://forum.dynamobim.com/t/join-geometry-node-rvt-2024/96456/1 "2023-12-16T15:11:48Z")
Hi. I made this graph. It joins two sets of walls together (joins ceramics, plaster, stucco, or any other wall finish with the partition wall). It works in Revit 2022 in a decent speed. In Revit 2024, I got a message that I have an outdated node. It pointed me to “Join Geometry” node. I removed it. I looked for a new node. There is a native node, and another node from Clockwork. I tried both of them. It didn’t work, because the elements are not intersecting. The old node from Revit 2022 disregarded the fact that the elements are not intersecting, which is exactly what I wanted. The wall finish is next to the partition wall. It is not intersecting with it. So, does anyone know a way to join two elements together, regardless of whether or whether not they are intersecting? Is there some other node out there? ![4. Join the Wall Finishes to Other Walls_2023-12-16_03-52-02](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/9/4/94137683140e5769bdc5ddcb70c02957d4faa2d1.png) regards, Andrej ---
**Author:** ![Mike.Buttery](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@Mike.Buttery](https://forum.dynamobim.com/u/Mike.Buttery)\ **Post date:** [December 18, 2023, 4:05am UTC](https://forum.dynamobim.com/t/join-geometry-node-rvt-2024/96456/2 "2023-12-18T04:05:37Z")
Which version of Clockwork are you using - current is 2.6.0 Perhaps also try minimal case to see if it works - I have selected walls with a 700mm gap and it works ![image](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/9/8/98d398bce1051cc6da0fb07d8f45254362c8cbf4.png) ---
**Author:** ![Andrej](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/andrej/32/172909_2.png) [@Andrej](https://forum.dynamobim.com/u/Andrej)\ **Post date:** [December 18, 2023, 8:30am UTC](https://forum.dynamobim.com/t/join-geometry-node-rvt-2024/96456/3 "2023-12-18T08:30:18Z")
I just found out that by default, Clockwork is not updated to CPython3, so that was the issue. > [@What language are we using?](https://forum.dynamobim.com/t/what-language-are-we-using/96465/20): > > Actually go into Dynamo, place the node to inspect, right click \> edit and you should be able to access the python nodes within. Interesting thing happened. When I use JoinGeometry node from Clockwork, and run the script, nothing is being joined. But when I edit the Clockwork node, copy the Python that is inside, close the node, paste the code into a OOTB Python node, and run the script, it works. Everything is joined joy ---
**Author:** ![Mike.Buttery](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@Mike.Buttery](https://forum.dynamobim.com/u/Mike.Buttery)\ **Post date:** [December 18, 2023, 9:22am UTC](https://forum.dynamobim.com/t/join-geometry-node-rvt-2024/96456/4 "2023-12-18T09:22:50Z")
Yes, get the IronPython2 package for Dynamo A few comments on the graph You could get the FamilyName using a node rather than via parameter ![image](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/0/a/0a8dd34b8cfb749822fb2a1ed5248542b1727824.png) You could also just scale up the geometry around its centroid and use a _Geometry.DoesIntersect_ node instead of a cylinder ![image](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/a/d/adb5d5510579e6c2c602a3926fcfc065826e78a3.png) ---
**Author:** ![Andrej](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/andrej/32/172909_2.png) [@Andrej](https://forum.dynamobim.com/u/Andrej)\ **Post date:** [December 18, 2023, 10:12am UTC](https://forum.dynamobim.com/t/join-geometry-node-rvt-2024/96456/5 "2023-12-18T10:12:23Z")
> You could get the FamilyName using a node rather than via parameter Thanks! This is good, it will shorten the graph. I just noticed that I would have to use List.Contains node, because I would be comparing strings: ![Untitled](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/5/b/5b8f5a29f2f12f89f786f9abb4fbd12e1f2ce96d.jpeg) > You could also just scale up the geometry around its centroid and use a _Geometry.DoesIntersect_ node instead of a cylinder I could use Geometry.DoesIntersect (if its faster than BimoprhNode), but I need to build the cylinder anyway. Your graph could return multiple walls per each join. Take a look at the picture bellow: ![1](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/8/b/8b92fa5f1f9fca1647b3158624c60ecc48fe4d3e.jpeg) ---
**Author:** ![Mike.Buttery](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@Mike.Buttery](https://forum.dynamobim.com/u/Mike.Buttery)\ **Post date:** [December 19, 2023, 12:15am UTC](https://forum.dynamobim.com/t/join-geometry-node-rvt-2024/96456/6 "2023-12-19T00:15:49Z")
Yes, agree - I can see your logic makes a lot of sense. The Bimorph nodes are going to be more efficient than dynamo Finding basic wall geometry intersections is a fairly inaccurate exercise and I guess that it could improve by adding filter conditions like are they parallel, different materials etc.