When splopped objects are booled, the target surface goes crazy.
The shading is damaged.
Changing render mesh settings doesn’t help.
In some cases the boolean union doesn’t work at all.
I can’t see the reasons.
Here’s what I do:
And the model:
SplopTest.3dm (170.6 KB)
I also tested in V7, same results.
What is wrong?
I can confirm,
for example on right surface comes this. (RHv7.3)
Boolean with individual objects,
sporadically a Dot Object is added and Boolean aborts,
without Dot Object, Boolean completes and removes piece of surface.
Dot Object says “surface intersection error.”
Sploped object also has a shadow flaw at the tip, like double surface.
I can’t see the reason for the failure.
The left surface is ugly, I know, but the right one is quite normal.
Also the object to splop seems ok to me.
Is is the model or a bug?
Perhaps @pascal can tell us and file it as a bug (if it is)?
Hi Charles - Splopping can result in self intersections
I do not know how feasible it is to make this better. I’ll add this to the list for the developer. The self intersection is tiny - microscopic, even. The length of that small segment is 7.1131685648842637e-09
@Charles - I have no idea if this is a reliable work-around but I tried making the surfaces of the input object more complex - all degree 3 in both directions and the curved surfaces with a good number of additional knots (_InsertKnot > Automatic) . My quick test shows the splopped objects are messy at the corners but do not self-intersect. It may be I just got lucky but possibly worth some further testing.
SplopTest_Complexified.3dm (58.7 KB)
-Pascal
Hi Pascal
From the first days on I always preach to keep geometry as clean and simple as possible…
Now complexifying can be a solution 
And it is not.
I tested here, and the result is not reliable (but a bit better than before).
We have 3 bugs now:
Hi Charles - there is one underlying problem with multiple symptoms - the creation of self-intersecting geometry. As I say, I will but this on the pile but I am not super confident that a fix will be forthcoming, in the short term at least - the refitting in Splop and other UDT tools is a complex and, ultimately, inexact process, from what I understand.
-Pascal
As is in file works in Rhino v4
I tested in V4 now as well.
It works far better, but not in all cases.
Sometimes the strange micro loop is seen in V4 as well.
And the following symptoms.
That’s bad news.
Rhino creates bad objects, and it’s a known fact - but no realistic chance it will be fixed.
In the example it is possible to fix the issue manually, not so much effort.
In the real model the splopped objects are more than a single object, so many more errors.
And I have no idea for a workaround.
