Surface.SubtractFrom - Another Bug

[mellouze]

Hi all
It has been a long time since I posted here, and I come to you with I believe to be anoter Surface.SubtractFrom bug. See the previous one here :

Surface.SubtractFrom bug?

Hi people Files : Desktopsurfs_opn.sat (11.0 KB) Desktopsurfs_walls.sat (21.7 KB) subtract.dyn (18.0 KB) I have encountered a bug (?) this afternoon (at least I’m guessing it is one). Here it is : I have a list of surfaces representing walls, and list of surfaces representing openings (doors and windows). I want to cut the openings off the walls. My idea was to : use Surface.Thicken (inputs = surfaces that represent the openings), use Solid.ByUnion to get a unique solid, fi…

In the exemple I encountered this morning, the Surface.SubtractFrom output is the same as the surface given in input, even though the input solids do intersect it. Here are the relevant screenshots and files :

The graph (as simple as it can be):

The input (and alas output) surface :

The input solids :

The SAT files :
Surf.sat (2.3 KB)
Opn.sat (63.7 KB)

Best,
Mustapha

[sovitek]

Hello…seems it works as it should… or ?

[mellouze]

Strange… Maybe this has been corrected in an updated version ?
I have Dynamo 2.1.0 (version on which I developped most of my scripts), but I didn’t updated Dynamo ever since.

[sovitek]

Not sure, but in your image above you actuelly have turned the last node preview off…

[mellouze]

I’ve juste turned it off to take the capture

[solamour]

This is also working for me in Dynamo Core 2.12

We did make some updates to the node as there was a bug with it that you may be running into. Is the node working for you with other cases or not?

A workaround, which uses one more node (Note, it will be computationally a little heavier with this workflow, and only work on surfaces that are in the same plane)

[mellouze]

Thanks for the input
This is the only instance where I encountered this problem, I had the same script running thourgh hundreds of other surfaces, and this is the only one that cause a problem.

I’ll try to update Dynamo in the future (and my scripts), and see if this does solve the problem.