Something seems to be broken with my Rhino6 setup. In Rhino5 if I take a sphere and a box made with “Solid Tools” and do a Boolean difference I get this:
No surprise. However, if I do the exact same thing in Rhino6, the boolean difference does not allow me to select the sphere as the “subtract from” polysurface.
Thoughts (other than use R5 only of course)??
Hi Steve - weird… can you please post a V6 file that shows this?
Is the sphere a block by any chance? Can’t do Boolean ops with blocks… --Mitch
Ok it’s weirder than it first looks … or I don’t know what I’m doing. It started with a Vimeo tutorial for Grasshopper (which I’ve just got working). I went through the tutorial and everything was fine. I then baked in the final geometry so I could do a Boolean difference just to see the result. That difference failed. So then in Rhino I tried to directly add a separate sphere, box, and cylinder to see if it was something I had done wrong in GH. Now in Rhino, that difference fails. The dark blue is the baked geometry and the cyan is the post-GH attempt to do a difference.
I could select the box and subtract a cylinder but the sphere isn’t selectable. Maybe it’s something I’ve done while GH is running as the grey sphere is what is use in the GH.
Rosette.gh (17.7 KB)
Rosette.3dm (2.8 MB)
Hm… it all works here:
This is what you expect, right?
I’m not sure what to suggest - what does the command history look like after it fails? (F2 key)
Geez I hope I get to be anonymous! Here’s what happened. I get tired of seeing extra lines in shaded view so I turned off some of the display options (isocurves and tangent seams). When I went to do the difference, clicking on the sphere resulted in no highlights. If I had just hit enter and then picked the box, it would work.
Hi Steve - if you also set the display mode to use ‘Shade highlighting’ that particular problem will go away. But I would like a different way to highlight anyway, myself…
FWIW, the option to display isocurves on selected objects is no longer in RH6 but was in RH5.
There’s a bug report about that that you can follow here: