Is there a way to close the open vectors created when performing boolean operations on vector artwork? For example, I have a somewhat busy or complicated design, I create a shape to fit it into and perform a boolean subtract to remove the extraneous portion. The resulting art has many open vectors that are now causing the art to have inconsistent fills.
Thank you - if this is confusing, I can supply some visual aids.
The Boolean functions all produce closed output shapes (or are supposed to), so if what you’re getting as output is not closed, please attach the project file with the sources here, or email it to support@lightburnsoftware.com if it’s not a design you want to share. (If you email, please include a link to this thread so we know what it’s for).
Thank you. Oz and I have been working with your file and have not been able to reproduce what you are observing. What else can you think of or share about your workflow? Which version of LightBurn, running on what OS?
While testing, we both commented on the time to calculate the boolean operation, and noted the complexity of this image. Yet both our exercises returned the expected results. We tested on both Windows and Mac.
I think I know what’s going on. The map is being subtracted from the circle. So the image appears inverted because the areas of the map are subtracted from the solid circle.
I suspect the desired operation is Boolean Intersection. Or reversing the order of the subtraction.
That’s interesting. I’m running the latest version of LightBurn - 1.2.01 on a Mac Mini running 11.6.8, Big Sur (3Ghz-6 core, 64G). Many times I create vectors from images, using photoshop, illustrator, and dragpotrace.
Berainlb - Yes, it appears that I should be using intersection. That did give me the desired results.
Thank you everyone!
I’ve improved the progress bar timing for the boolean ops for the next release, but there’s not much I can do with this case otherwise - there are hundreds of thousands of lines in that file, so it’s just a lot of work for the computer.
completely understandable. I generally work with files with that many lines, so I’m used to making my computers labor for them. I do apologize for not realizing intersection was what I was needing.