Anyone know why and how to prevent all of these extra files being created whenever I save a toolpath using post processor for Vectric?
I noticed this as well and was wondering….?
Those are an annoying little side effect of some functions in the macros when you run a file, not from when you create them with the post processor. I forget the exact name of the code, but when you run the Gcode file it will likely run some code (like the M6 macro), and these get generated on the fly and then run as part of the macro code. You can delete them and they will come right back in the directory when you ran your Gcode from. The only way I know of to get rid of them is to either modify the macro code to do these functions in line instead of current way they are generated, or you could write a cleanup macro that is called at the end of your Gcode that deletes these files. Maybe @Eric has a better solution since the last time I asked him about it.
I find them annoying because they clutter up my temporary Gcode directory and always end up at the top because I sort my directory by timestamp. I wish Centroid would just clean these up automatically after the Gcode is run.
Everything Jim said is correct. I am working on a fix. No promises though 
1 Like
Nice!
fingers crossed 
. I am in the same camp as jim. I keep a temp gcode depot as well, and with the fusion bug only exporting if there is a number at the beginning. I would love some quality of life improvements!
How would one set that the files go to a certain folder?
They are created wherever you load your g code from
The issue and solution is in this thread on the Centroid forum. 09101 09102 ect... Keeps Auto populating my nc files folder (Work Around Resolution) - Page 2 - Centroid Community CNC Support Forum
This is not a solution unfortunately. This is the default behavior by CNC12 and not something that we, or an end user can control.
If you want to see an m6 file that solves the issue, I can send you one. It leans towards a custom M6 and not an off the shelf or auto generated one though.
The underlying issue here is that if you use subroutines those files are created. On that particular script you can work around it, but there are other macros (like many of ours) that require subroutines because the macros themselves are at a level of complexity that won’t allow for that simple workaround unfortunately.