I’m running into a strange issue with MillMage and I’m wondering if anyone else has experienced this.
I set up a project in MillMage where I imported an Adobe Illustrator (.ai) file containing the vector paths. I then created all the operations I needed (pockets and profiles) and set up the tools correctly. Everything previews exactly how I expect — the toolpaths look correct and the simulation behaves properly.
I then save the project file to a network drive.
The next day when I open the project again, the toolpaths are completely different. Some of the operations appear to be doing the opposite of what they should be doing. For example, pocket operations end up cutting areas that shouldn’t be pocketed, almost like the inside/outside logic flipped or something similar.
Nothing else about the project changed, same vectors, same operations, same settings.
What’s odd is that if I recreate the operations from scratch, everything works correctly again. But once I save and reopen the file later, the operations get messed up again.
A few details about my setup:
MillMage Core 0.8.00
Running on Mac
Tested on both an M2 Max Mac Studio and an M2 MacBook
Same behavior on both machines
Project file is saved on a network drive
This obviously isn’t very sustainable if toolpaths change every time I reopen the project.
Has anyone else seen this behavior? I’m wondering if this could be related to:
Welp, did some more testing and now it’s happening to local files. I’ve only imported Illustrator files (.ai) and have not tried any other imports or creating shapes in MillMage. I’ll be testing that next.
There were files that had the issues that were saved on the NAS, copied them to my local hard drive and deleted all the paths and started over with re-importing and getting it back to where it was/should be. Saved them, again locally, and re-opened them and they had the issue.
Going to test with a brand new fresh project and save locally only to see what happens.
Yep, happening to straight up local files as well. Created a fresh brand new project, imported my SVG file, created all my operations and got it looking like it should. Saved locally to my desktop, closed, then re-opened immediately and the issue is happening. Tried a new vector file as well with this test. Only worked on this project, didn’t open any others in between.
What it should look like. This was after I set everything up.
I think I may have found the issue, and should have mentioned this in the original post as well.
I was using “Auto Use Layer” for nearly all my operations, or the ones that made sense to. I re-did all the operations, but selected the paths I wanted for them instead.
So after doing that, it seems to be working as expected. So something with Auto Use Layer is messing things up.
I’m not sure why, but it looks like the group of brown rectangles is included in every operation. Digging in to see what’s going on.
Edit: Found and fixed. This will be in a patch update relatively soon. Basically, if you didn’t have any shapes manually assigned in an operation, it would end up automatically assigning the first shape in your file to it. In your case, that first shape was the group object containing the brown rectangles.
Can you check out this file as well, having the same issues with it when I have Auto Use Layer on for an operation. I have an operation assigned manually to a shape/path and the others using Auto Use Layer. And all the shapes/paths have some sort of operation to them, either auto or manually assigned.
If you have at least one shape manually assigned to every op, you can safely use Auto-Use Layer for the rest. The bug is that operations without any manually assigned shapes would self-assign the first shape in the file when loading.
