GCODE export directory into current dir ???
Hello,
I really love PrusaSlicer (on Gentoo Linux) and all the cool stuff it packs. But one thing drives me mad, and I really would like it to be "you forgot such and such config parameter".
My workflow is to export the GCODE into the same directory the STL or 3MF come from.
If I select the "remember output directory" option, it will (as expected) remember where I stored the previous GCODE and use this directory by default, until changed. So I very often end up having my GCODE into some other project's directory tree.
If I do not select this parameter, PrusaSlicer always uses the same directory by default (I do not understand how this directory was chosen, but that's another matter).
I have not found any way to require PS to use the same directory the STL/3MF come from as default for GCODE exports. Which is weird IMHO, since this behaviour is exactly what is done when saving a new project, which by default goes into the same directory as the STL.
Any idea ? Or shoud I open an enhancement request ?
Thanks.
RE: GCODE export directory into current dir ???
I'm running on Win10 at the moment and for me it saves gcode files into the same directory as the Prusa Slicer Project file. So I open a new project, load in some stls etc from wherever, then I save Project As into a directory of my choice. After that whenever I generate gcode files it saves the gcode into the same folder as the project.
Same when loading in a previous project, if I regenerate gcode from that project the gcode is saved to that directory.
Why are you filing GCODE?
It's a temporary file, used to transfer a slice to the printer(s) after which it is a waste of space...
For most prototyping it will be used once and then discarded. If a project is approaching completion you may be tweaking the slices so it makes sense to preserve a .3mf project file from which the GCODE can be recreated or altered at need but otherwise it's the CAD files that matter.
I slice everything into the same transit directory on a Raspberry Pi within two paces of my printers, all GCODEs more than three days old are deleted from both the USB/SD media and the transit directory semi-automatically about once a week.
Yes, there are two or three GCODES that are used unpredictably but often enough to worth holding ready - they are in another directory on the same Pi. Neither directory is ever backed up as everything is either temporary or trivial to recreate.
Your proposal is likely to clutter the directory tree with large, mostly unnecessary files that can be recreated at need should you so desire. I don't see that as an enhancement.
Cheerio,