PrusaSlicer has encountered an error (filename format template)  

RE: PrusaSlicer has encountered an error (filename format template)

Just to clarify as well, I know I can modify the output filename format and save it as a modified preset, but I am not allowed to modify the system presets and they have this problem caused by an invalid output filename format.

Would uninstalling and reinstalling the software completely be a way of resolving the issue?

RE: PrusaSlicer has encountered an error (filename format template)

Before you do that check you have the latest profiles update.  The profiles are updated separately to the Prusa Slicer software.  When they make changes to the main software the profiles usually get modified if needed too.  When you start PS there's often a pop up saying a Configuration Update is available, which if you click on it will download the latest profiles (where things like that filename output string are stored).  
You can however force it to check using Configuration>Check for Configuration Update.  

RE: PrusaSlicer has encountered an error (filename format template)

There was a configuration update available, but that did not resolve it.

2.6.1 has also released, but installing that did not clear it.

Does everyone else have the default output filename format as {input_filename_base}_{nozzle_diameter[initial_tool]}n_{layer_height}mm_{printing_filament_types}_{printer_model}_{print_time}.gcode

It seems absurd that this massive output string that includes variables is the default filename format for all of the printer presets.

RE: PrusaSlicer has encountered an error (filename format template)

The default profiles such as 0.2 quality etc  for a Mk3 or a Mk4 have that and when I slice a sample cylinder or box it doesn't produce an error on my system (Windows 10).  Tried it in 2.6.0 & 2.6.1.

Can you post a zipped up project file saved from your computer that has the issue.  File>Save project As and then zip up the 3mf and attach.  With a project file all the settings you are using should be contained.  So if the problem is with one of the profiles someone should be able to duplicate it loading in your project.

I've tried several default printer profiles(Mk3, Mk4, different nozzle sizes and the associated default print profiles that go with them and none of them give and error slicing/saving gcode.

If a project from you doesn't give the error on a different system then that leads to looking at other things like system/environment variables or checking if someone else on a Mac has the same issue etc.

RE: PrusaSlicer has encountered an error (filename format template)

One thing I have noticed is that if I load in a more complex stl and slice then the Slice button changes to the Export button before its actually finished slicing for some reason.  If I click export before its finished slicing then it does generate that exact same error.

Just to get it out the way, you aren't clicking the export before its finished slicing are you ?

If you are waiting until its finished then that means the next area to check is the temporary file that PS writes while slicing.  If it cant do that properly then that will be a problem.  It may just be better to nuke everything (after taking a backup of your configs using the File>Export>Export Config Bundle functionality), including all the config folders (which aren't removed when you uninstall btw) and then do a clean install.  Not sure how Mac handles folder write permissions.

RE: PrusaSlicer has encountered an error (filename format template)

Posted by: @neophyl

The default profiles such as 0.2 quality etc  for a Mk3 or a Mk4 have that and when I slice a sample cylinder or box it doesn't produce an error on my system (Windows 10).  Tried it in 2.6.0 & 2.6.1.

Can you post a zipped up project file saved from your computer that has the issue.  File>Save project As and then zip up the 3mf and attach.  With a project file all the settings you are using should be contained.  So if the problem is with one of the profiles someone should be able to duplicate it loading in your project.

I've tried several default printer profiles(Mk3, Mk4, different nozzle sizes and the associated default print profiles that go with them and none of them give and error slicing/saving gcode.

If a project from you doesn't give the error on a different system then that leads to looking at other things like system/environment variables or checking if someone else on a Mac has the same issue etc.

I've been playing with this some more and it seems that what might be triggering this problem is importing more than one STL into a project... if I only import a single STL for printing I can't reproduce the problem, but if I import a couple of STLs I can reproduce it at times.

I suspect that there is something going on with a param getting clobbered when multiple objects are loaded onto the plater. 

Quite annoying.

I will generate another project that trips the error, zip it up and attach it here when I get a chance to do this.

RE: PrusaSlicer has encountered an error (filename format template)

You may need to use 'Add Media'  Or

Drag and drop the zipfile to the bottom of the text entry window. 

It appears that Attach file, is giving issues. 

regards Joan

RE: PrusaSlicer has encountered an error (filename format template)

Thanks Joan for the info. I have been doing it the same way since before I got the MK4 so perhaps something has changed.

RE: PrusaSlicer has encountered an error (filename format template)

I have passed this issue on to Prusa.

regards Joan

RE:

Problem 3mf zip file attached.

I imported an STL from this creator, set layer height to 10mm and exported the g-code with no errors.

Then imported another STL from the same creator, set layer height to 15mm and get error upon g-code export.

Tried completely quitting PrusaSlicer, starting a new project, importing the STL and exporting and same error.

The output options in print settings are default when this occurs.

RE: PrusaSlicer has encountered an error (filename format template)

As mentioned earlier the Attach file button is broken on the forums currently so your attachment isn't working.  Apparently you have to use drag and drop or the Add Media button at the moment.

RE: PrusaSlicer has encountered an error (filename format template)

I can see the .zip file at the end of my message post, so it does appear to have uploaded. I logged out and refreshed the page and still see it there. You aren't seeing it or aren't able to download it?

RE: PrusaSlicer has encountered an error (filename format template)

The link returns the error:

AccessDeniedAccess denied.Anonymous caller does not have storage.objects.get access to the Google Cloud Storage object. Permission 'storage.objects.get' denied on resource (or it may not exist).

RE: PrusaSlicer has encountered an error (filename format template)

cute_cat_ghost.3mf

RE: PrusaSlicer has encountered an error (filename format template)

Tried the file and I get no errors IF I let it finish slicing before clicking Export Gcode.  

RE: PrusaSlicer has encountered an error (filename format template)

Okay, interesting.

It has definitely finished slicing when I am trying to export it so not sure where the discrepancy is.

RE: PrusaSlicer has encountered an error (filename format template)

fwiw I'm running 2.6.1 on linux (ubuntu 22.04) and it works fine there (waited for slice to complete before exporting).

What happens if you delete the output file template and then type the exact same thing in?

RE: PrusaSlicer has encountered an error (filename format template)

I completely quit Slicer, re-started it, re-imported the STL ,sliced it, and this time it exported without the error.

I know I've restarted before when I've run into this and still run into the problem after slicing though, so I'm not sure what is going on. I have an M2 based Mac and the slice times are ridiculously fast, so perhaps something else is occurring.

One thing that Prusa might be able to do is introduce a dialogue when someone tries to export the g-code that simply tells the user that slicing has not finished.