Now, to go on the next step: how should I do if I would like to not make the curve offset to avoid the kind of loft between the boundary the added points and keep a constant width?
probaly you have some binding i have when i test…so try disconnect floor or point input…run…connect again run…maybe it could do it PolyToFloor.dyn (47.6 KB)
It’s more stable now, but it still doesn’t work correctly on the first execution on my side.
On the first run, the script creates the floor on the XY plane using the Z‑offset, but the floor is not placed at the correct elevation. It’s as if the geometry is being generated before the floor creation is fully ready, so the Shape Editor doesn’t get the right elevation values.
If I rerun the loop, nothing changes.
However, if I manually reconnect Point.ByCoordinates to IN[1], run it, and then reconnect List.Flatten to IN[1] and run again, it works properly.
It feels like the coordinate node computes faster than the floor creation step, so the Shape Editor is not using the updated geometry on the first try.
Hi @CMANEL i can take a look in next week im not at dyn, on vacation…but not really sure, try with some transaction or passthrough…another way mabe could create the floor in plane and set the slope.without play with subelement…maybe.. PS is it the ootb create floor there dont work on struc floors,btw you can set it to struc after…not sure if in other post you could find out why…or maybee @jacob.small have an idea,i give it a go later
I tried with only Transaction.End or Passthrough. It wasn’t a success
But after getting a bit deeper in the definition of both, in my case it was mandatory to use both at the same time. If I have well understood, it needed to commit the data to Revit with Transaction.End (between Floor and Python script) and only after the commit, to restart the process with the points to finally use it in the Python script.
perhaps…Floor.AddPoint ottb could be better, and maybe flatten the point list before feed in
Which version of Revit are you using?
