Updated to 2.0.01 (is shows as Lightburn Core). With this version, lines and curves do not intersect, and as a consequence, drawings can not be made accurately
Can you be a little more precise about what you are experiencing, some visual example would be nice too. I have not experienced anything unusual when constructing with lines or curves in the “new” LB. (MacOS)
Hi
Thanks for the response. I found the issue when working with a segment of a large radius circle. 1270mm radius, with a segment length of about 200. When I draw a straight line across it, it does not “intersect” the segment and so I can not use the “intersection” as a snapping point.
I have experimented with a full circle of smaller radius (200) and the line and circle intersect. Similarly with rectangles. If however I stretch the circle into an ellipse, the line and (now) ellipse no longer intersect and consequently, no snapping point.
The file is large as it has images within, and lots of drawing. It’s about 12.5MB. I thought this might have been an issue, but I can replicate the issue in a new file. The behavior is erratic also. Sometimes the intersection will be recognized in a new file, and other times not. Even more bizarre is when I have drawn a circle and a line over it, and it will show an intersection on one of the crossings points, but not the other.
I don’t have a Z axis laser, but it’s as if the shapes are being drawn on a different z plane.
Any suggestions greatly appreciated. Windows 11 environment
I’m trying to understand what you mean. Is that what’s in the picture?, circle 1250mm and a crossing line segment at the top, which (here) snaps nicely to the topmost of the 4 circle points.
Works with each of the 4 circuit points
(convert to path)
Hi
Generally correct. Things snap to the quadrant points of the circle. If you make the circle an ellipse (randomly reduce the x dimension say) and then draw a random line through the ellipse, not at one of the quadrant points, then there should be an intersection point where the line crosses the ellipse. When I do this, I don’t get the intersection snap.
The ellipse is converted to a path, and it doesn’t matter if I have selected the line, the ellipse, or both. Generally I don’t get the intersection as a snapping point, but sometimes it does. It used to work without issue before the update.
I can’t send a screenshot today as I’m away from my computer (responding on iPad), but can send through one if it will help tomorrow.
Again, many thanks, cheers
I probably don’t fully understand your problem. When I try what you say, the line segment snaps to the ellipse at the segment’s midpoint, regardless of the angle. (NB. The circle is not converted to a path)
I believe this might be the issue the original poster is experiencing. The trim tool does not always detect intersections. Note: The red segment has the snipping tool active, but the scissor icon is not shown when using Windows Snipping tool.
When drawing a line and snapping to nodes in Windows, first select the Alt key, and hover near the first node. It will appear that the cursor is like a magnet, and it attaches to the nearest node. Then do the same for the node you want to snap to. It would be nice if LB “flashed” a small square color over the node you snapped from/to. You get used to how it works, but a colored visual would be better.
Hi again
Thanks for the responses. I have now done a couple of screenshots which I hope makes the problem more clear. Please excuse that they are actually photographs of the screen, but the screenshots didn’t show the cursor.
Looking at this image (Fig 1), there is a “V” on layer 02 and two circles on layer 03. The smaller circle is diameter 150mm, the larger circle is 2540mm diameter. In this figure, I have hovered the cursor over the intersection of the right side of the “V” and the smaller circle, and the cursor shows as a diagonal cross “X” with a small circle, indicating that LB is recognising the two lines are intersecting. In the second figure below (Fig 2), the same image is shown but now the
cursor is hovering over the intersection of the larger circle and the right leg of the “V”. As can be seen, the cursor is a line with a “zig-zag” in the middle, indicating that LB is recognising that there is an object there to snap to, but it is not recognising the intersection. Up until a week or so ago, this was not an issue, but now with the release of LB version 2, it seems that there is.
I hope this is more clear.
Many thanks
The visual explanation helped a lot to understand the issue, thank you.
I can reproduce it this way, that I can get the intersection snap function/view of the intersection on 3 of the four intersections, but not on the last one.
It would be great if @LightBurn could look into the matter and/or come up with an explanation.
I’m glad that I managed to explain it in the end such that you have been able to replicate the issue. It’s quite important for me to get this fixed as I am building a model ship and very many of the parts involve this type of line intersection for trimming, extending, snapping etc. I am new to the forum. Does your “at” LightBurn push it up to them, or is there something more that can be done?
I’m pretty sure the developers @LightBurn are looking over our shoulders and are happy (in their own way 
), that “we” find these kinds of bugs so they can be fixed.
During their workday, they’ll probably make a comment on the matter.
1 Like
Hi
There seems to be no comment coming out of @LightBurn. It would be nice if there was some acknowledgment of an issue being worked on. I have downgraded to V1.7. Working a treat!
Cheers
Thank you each for reporting. Here is what I am seeing with the recently announced LightBurn v2.0.02 Release Candidate. If willing, please confirm your results. 
(click to zoom)
Note: investigation continues.
Hi Rick
I have just installed 2.0.02. Unfortunately, behavior has not changed for me. See attached. Again photos of the screen as it shows the cursor. First figure shows the cursor hovering over the intersection of two straight lines. The second is hovering over the straight and large diameter circle (2540 mm). As can be seen, first figure recognizes the intersection, the second does not.
Many thanks. Hope this helps. As noted above, it works exactly as expected in V1.7.
Cheers
1 Like
Report generated.
I believe I have this fixed for 2.0.03
2 Likes
That is excellent news. Cheers
1 Like