Hello,
It appears that the node “Floor.AddPoint” works only if I switch back and forth between Auto and Longest lacing… It seems to be arbitrary, because it works if I make the switch, not because of either one of these lacing are set.
See video… Is there a way to refresh the model, or trigger this “refresh”?
Crazy thing is, this node has been regularly working till now, in tis same script…
Hard to give much insight when we can’t see what the graph is actually doing, but I’m guessing this is more of a transaction issue. It looks like you’re selecting an existing floor to modify, but are you creating any other geometry in the graph? Instead of changing lacing, what happens if you just disconnect one of the Floor.AddPoint inputs, run the graph, then reconnect and run again? If that process also updates the floor points then you’re dealing with multiple transactions.
Nick,
the floor is existing… the points are new, unless the script is re-run, then probably Dynamo
"remembers” them from previous run.
And yes, simply disconnecting, run, and then re-connecting the Floor.Add node will “trigger” the script to function again…
I am experimenting with the Transaction nodes, but this is very odd becasue the scirpt has been working for the last few weeks.
All that has changed is I am using a multi-loop floor element (those stripes), instead of a single loop floor…
Any advice on where to put the Transaction nodes?
I mean the scirpt is too large to share… 
Wait,
I think the problem is that I am using a floor that was reset (points never edited).
I think the Floor.Addpoint node only works for floor that were already edited…