Hi!
It’ll be extremely helpfull if you could work out the concept of slice caching (using a local file to host last slicing results). It’s the same concept as when rendering… I can see the last render even after closing the software I’m working with. With Bambu Studio I’m forced to slice every single time which is, depending on many factors, a time consuming operation specially with this trend of printing fabric-alike meshes; and the only option to avoid slicing is to rely on printer’s local cache or Bamby Handy app where I can re-send the same job for printing. But when working with a computer that doesn’t happen.
Hi, you can save the generated g-code to a local file manually from the slicer. The arrow on the “Print” button (top right) expands to include that option (can save one plate or all). Later these files can be opened in the slicer w/out re-generating anything. I know it’s not automatic, but OTOH you have ultimate control over what gets “cached,” where, and when.
HTH,
-Max
Yeah, thanks a lot Max. I was thinking about the automated process. That’s why I used the word “caching”. If I forget to manually export g-code then it’ll be (and it actually is) frustrating, whereas when using a cache file I won’t forget for sure to copy it whenever sending it to whomever or to upload it to makerworld, etc. It’s easier not to forget about files portability rather than deal with the frustration of having to slice again.