discuss@lists.openscad.org

OpenSCAD general discussion Mailing-list

View all threads

Preview, processing v graphics

JB
Jon Bondy
Mon, Oct 20, 2025 6:18 PM

If this might lead someone to over-write the output from OpenSCAD with
the output from PrusaSlicer, then that would be annoying.  Of course, we
have no control over PrusaSlicer (other than I imagine it will at least
emit a warning message).  I imagine each of us will come up with our own
naming conventions

On 10/20/2025 1:59 PM, Jordan Brown via Discuss wrote:

With the advent of F7 invoking the selected exporter, I thought I'd
take a stab at using 3MF as my default 3D export format.

I immediately noticed a potential issue.  PrusaSlicer uses 3MF for its
project files.  Historically, I've exported as STL, brought that into
PrusaSlicer, then if the slicer settings were non-trivial I saved the
project using the same base name.  I can't do that now since the model
and the slicer project file end up with the same extension.

There's nothing wrong, and nothing really to be done about it, but
it's an unexpected hiccup in my workflow.

(Of course, what I really want is a way to embed the slicer settings
in the OpenSCAD program and directly export PrusaSlicer-compatible
project files.  But that's a pipe dream for now.)


OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org

--
This email has been checked for viruses by AVG antivirus software.
www.avg.com

If this might lead someone to over-write the output from OpenSCAD with the output from PrusaSlicer, then that would be annoying.  Of course, we have no control over PrusaSlicer (other than I imagine it will at least emit a warning message).  I imagine each of us will come up with our own naming conventions On 10/20/2025 1:59 PM, Jordan Brown via Discuss wrote: > With the advent of F7 invoking the selected exporter, I thought I'd > take a stab at using 3MF as my default 3D export format. > > I immediately noticed a potential issue.  PrusaSlicer uses 3MF for its > project files.  Historically, I've exported as STL, brought that into > PrusaSlicer, then if the slicer settings were non-trivial I saved the > project using the same base name.  I can't do that now since the model > and the slicer project file end up with the same extension. > > There's nothing *wrong*, and nothing really to be done about it, but > it's an unexpected hiccup in my workflow. > > (Of course, what I *really* want is a way to embed the slicer settings > in the OpenSCAD program and directly export PrusaSlicer-compatible > project files.  But that's a pipe dream for now.) > > > _______________________________________________ > OpenSCAD mailing list > To unsubscribe send an email to discuss-leave@lists.openscad.org -- This email has been checked for viruses by AVG antivirus software. www.avg.com