and another dirty way as probably could work as well 
so now we actuelly have many option
¨try here but with that method some will fall becaurse some beam columns isnt really connected, if you wanna have it to work in all cases you should play araound with the location line instead i think…
forumHome.dyn (152.4 KB)
Hi,
the Z is in capital letters, it is the component of the vector carried by the Z axis
ans.Z
tagada.Z
Sincerely
christian.stan
can you show your whole graph ? expanded and you are sure you select as here i have only tried on one level
try cross in lacing in intersect
forumHome.dyn (158.3 KB)
sorry, surface.innerperimiterscurves, this ootb node should only be present from 2023, I don’t know if we can rebuild it for a lower version,
in this case,
follow Mr. sovitek’s lead
Sincerely
christian.stan
yeah we can probably find one similar in a custom package
the idea of the algorithm of this node must be I take the 1st line, I check the intersection with a line of the rest of the lines, if 2 lines I take the 1st of this one, I delete it from the stock, and I continue, then if exhausted I move into a second storage container until exhaustion, it will take me at least twenty days to write such an algo without being sure of arriving at a convincing result, it is better to search in a package
it’s very frustrating not knowing how to code sometimes
Sincerely
christian.stan
yeah in this case here all depends on how its modelled in revit, if it is modelled so beams columns really connect C/C then i guess all will go more smooth
Not ALL can creat slab~~
what is happen ~~
as i try to say in early post here, it will fail if your beams columns dont really connect,thats why i first tried with location line so we could create closed loops… try to clean that up in the revit model…and can probably work for all
