Boolean Issues continued

I have asked at least once before questions about the Boolean tools. The last one in April 2024. My issues from that event in April, doesn’t seem to work to resolve this isssue. I’ve attached 4 files.
I’m trying to get the small image shown in image 1 onto the branches as sown in the example in the 2nd image. I did it once but I’m not remembering how to do it again. I’ve confirmed the tree and the image are closed objects, see last 2 images. I’ve also put them all on the same layer as sown in the last 2 images. I can’t seem to get them to work. I know the software is working like it should, and that user error is the cause. I am looking for suggestions on how to resolve.

Seems like I always have issues with Boolean tools. I’m hoping one day I’ll figure it out without asking for help.

It’s been 2 years, can you send those files again so we can play together?

I’ll see if I can find those files, but this is a new and different issue. I’ll work to find them just in case. The files attached is for a different problem as I understand it.

Here are the files from April 2024, and the link to the previous issues.

Boolean not working.lbrn2 (8.5 KB)

Could be you’re selecting them in the wrong order.


Sometimes it’s wise to use the boolean assistant. This is version 1.7

^B is the keyboard shortcut.

If you use Tools → Boolean Assistant it will preview you the results of a specific selection real time.

Did you use the assistant? Also try selecting in the proper order.

Good luck.

:grinning_cat:

Assuming that the shapes are properly formed try this:

  1. Move the dog tag over the background tree in the position you expect it.
  2. Select the tree
  3. Add dog tag to existing selection by holding shift then click
  4. Tools→Boolean Subtract

Upload the lbrn2 file that you’re currently dealing with. The pictures aren’t the file.

1 Like

In this file there is a logical explanation why it is not suitable (as it is) for boolean operations.
Your bottom row of teeth is not “close enough” to the rest of your drawing, therefore…

That and the shapes not being closed, are the 2 main problems that most often prevent correct boolean operations.



Possibly an optional tolerance of up to 0.05 mm could for example prevent this one problem…
It should be made as a suggestion to LB.

1 Like

Try changing to line not fill, don’t know why but sometimes it just doesn’t like fill colours doing boldens

could be pixels and not being able to find line definition that it wont work

I thought I tried, but it wasn’t giving me the option, either from the menu drop-down under Tools, or by doing ^B

I’ll read the rest of the comments and see what I can learn. As I said, I’m confident this is user error as I am increadibly pleased with the powerful program Lightburn is.

Initial Tree Design_treeonly.lbrn2 (216.4 KB)

Right, thanks for that reminder. Here’s the file.

Your tree is an open shape. I went to Edit Menu> Select Open Shapes Set to Fill and it selected the main tree. I clicked Node Edito and found the problem. I pulled it apart for the screenshot. Connect the shape at this location and Boolean Tools will work.

1 Like

To keep Fill Shapes integrity the better faster and easier solution is to use the Cut Shapes Tool (Alt + Shift +C).
image

Edit: your shape also has some other issues. Tomorrow I´ll explain better with a pro tip.

Check Here:

I so appreciate this forum. I can always find the answers I need here. Thanks so much Tim.

I wonder how I missed this. I set the layer to fill and it filled just fine. Doesn’t that usually tell you that there is a closed or open object?

Something more here I’m having to take by faith I guess…

Your tree shape isn’t a “pure” continuous shape.

Typically, yes, but in this case the nodes were right on top of each other. Apparently that is close enough for rendering. It didn’t pop up an error when previewing either. Select open shapes found it though.

This tells me there is a bug in Lightburn FILL or is above FILL tolerances.
Because is identified as a open shape but can be rendered as “closed” FILL.

However and to clarify users searching solution to similar situations

Can you explain step-by-step how you obtain this in a straightforward way ?

1 Like