done the usual - went to edit
close selected shapes , auto join shapes
select open shapes set to pocket ,only thing still highlighted , clicked that again nothing shows
even tried select shapes smaller than selected using one of the smallest pieces
still comes up as above in preview , saved restart still there
in preview it looks ok
am i missing the obvious
high land cow big_backup.mage (61.1 KB)
found problem after about half hour of searching found a minute little dot causing issue
Yes, there was a very small shape (less than 0.001mm) causing these two warnings:
Operation #1 (MDF sign Pocket 8mm) → Wood down cut 6mm
contains one or more open shapes that will be skipped
Operation #2 (RestPocket Rest Pocket) → Wood downcut 3mm
contains one or more open shapes
I’ve asked the dev team why the alert description mentioned “open” shape, I as that threw me off initially when I tried to “Select Open Shapes”, but perhaps because it is so tiny it also is effectively like an open shape also in some circumstances in the program?
But the shape can be found if you turn on start point visibility or use Edit>Select Shapes Smaller than Selected
It shouldn’t have caused any issues with this job if this particular warning was ignored.
i did try that and it didint show anything, when i have used it with LB it has shown really small pieces
didn’t think about using start point will try that next time
cheers
You have to create a small sacrifice shape 1mm or 2mm (or one that´s smaller than what you design). Select it and the above Tool then delete.
I have had the same kind of issue, little dots often cropping up in various places almost 1 pixel x 1 pixel.
I have a feeling this might be a bug, I find they usually crop up up after snipping (I call them artefacts) but don’t notice them util MM throws up a dialog.
NB. I have never had this with LB.
LightBurn and MillMage are using the same core engine, but MM has more checks against this kind of thing. LightBurn has a few more mature “filters” for things that are so small you’d never see them anyway, and will automatically remove things that won’t contribute to the output.
MillMage’s output builder is entirely new, and doesn’t have those same checks. Typically, CNC work uses less complex geometry and designs with larger features than you would for laser work, so I didn’t expect to need this kind of filtering.
Have you reported this before? If you can reproduce it consistently and tell us how, we should be able to fix it.
What’s happening here is that MM is doing a bit of cleanup on the shape to remove line segments that are too short. In this case, all the line segments were too short, so the resulting shape was “open” - meaning the start wasn’t connected to the end.
I’ve changed the code to keep at least two segments, to make sure you can have a closed loop, which gets rid of the “open shape” warning. You still have the problem of the teeny shape that the bit doesn’t fit in, but that’s actually true. 
Thank you Oz,
I have not reported it before but I will see if I can get more info to you if/when it crops up again, I like to think that it is consistent…but consistently inconsistent 
oh so you cant use a small part from inside the design , i just interrupted it as pick a piece and than search
cheers oz , would rather have bit to big warning than open shape , may not cut
Per the docs:
Currently selected shape remains in the resulting selection.
So, you don´t want to delete a shape that is part of your intended design.
You can also Select All then Arrange > Create a Rubber Band Outline, if it´s outside will show up.
Or you can click-drag-right (red selection) in small zones of your design…
Or select the shapes one by one and set them to another layer then hide the layer . After do a large click-selection…
MillMage/LightBurn have a few options that gives the same output.
Yes, you can, but it will find every shape that size or smaller and select them. We’ll probably add a dialog for this at some point, but coding UI takes longer than the feature itself sometimes, so using an existing shape made it faster to write.
Yes, ditto - it was a bug, and has been fixed.
