Some slicer improvement suggestions
 
Notifications
Clear all

Some slicer improvement suggestions  

  RSS
mnemic
(@mnemic)
New Member
Some slicer improvement suggestions

Greetings dear [imagine I wrote your name here].

Here are some odd behaviors that I'm having in Prusa Slicer, or just some suggestions that would make my life easier at least. I'm on version 2.33 on a Windows 7 machine.

Configurable Gcode Export Name Syntax

  • It would be great to be able to change the "default naming" for exporting GCode.
  • Add support for any variable that makes sense to expose
  • Also add "custom variables" that show up in the right-side panel if you add them.
    • This could be useful for whatever value I want to change for all my prints

Toggle for auto-slice in the Print Settings pane

  • So you can quickly disable it if you're doing multiple changes to a heavy model.

Auto-slicing delay or pause

  • Maybe it makes sense to delay the auto-slicing by a second or two (with an option).
  • And also have an option to prevent or pause it if another tool is being used.

Auto-slicing interrupts move tool

  • There's a bug that happens when you move a mesh as the program is auto-slicing.
    • As it's done slicing, your ongoing move is undone.
    • This is frustrating when trying to correct an auto-arrange mesh layout.
  • It may interrupt other tools too, but this frequently happens to me when moving pieces around the plate for layout purposes when I have auto-slicing enabled.
  • If the auto-slicing was quicker to access, it wouldn't be as big of a problem.

The Arrange feature often creates unoptimized patterns.

The auto-slicing issue above comes from this issue where:

  • If I have 20 copies, I may get 4 in the first row, 5 in the second, 6 in the third, 5 on the fourth row.
  • Instead I would expect a 4 by 5 or 5 by 4 grid, since I'm duplicating objects.

Slicing Presets name recursion bug

  • When you "Save As" for a project, the Print Settings (the preset drop-down at the top of the right-side panel), gets the name of the old file.
  • If you then "Save As" again, it becomes: "Old file name (old file name)", which becomes unreadable.

The whole toolbox to the left is unclickable unless you select your mesh first.

  • It's more common that you first pick the tool, and then the object you want to manipulate.
  • Like IRL, you pick up the hammer, then choose the nail to smack.

3mf file format opening does not open it as a "project"

  • If you have assigned the .3mf-format to the PrusaSlicer software, and you double-click on a file, it will open the .3mf, but it won't have said 3mf open as a "project".
  • This means the first time you go to File > Save, it will do a "Save As", even if you already have a project file opened.
  • The name of the 3mf is not listed in the window name, it just says: "PrusaSlicer".
  • If I do a "File > Open Project" and load a .3mf-file, it opens properly, and the window title is set to the name of the 3mf-file.
Posted : 30/08/2021 6:07 pm
fuchsr
(@fuchsr)
Noble Member

All reasonable ideas. Alas, this is not the place to get them in front of the eyes of the actual developers. Try https://github.com/prusa3d/PrusaSlicer

Posted : 31/08/2021 1:29 am
mnemic liked
Neophyl
(@neophyl)
Famed Member

Also I think at least 80% of those already exist as github issues and one of them already exist within the software.  There are 1700 open issues after all.  So if you do post there please search first so you aren't creating duplicates.  Its also best to have one issue per item as that way each can be tracked independently. 

For example you can already configure your output filename.  The format is defined in your print profile.  Print Settings>Output Options.  You do need to be in expert mode to see it though.

Posted : 31/08/2021 8:54 am
mnemic liked
mnemic
(@mnemic)
New Member
Topic starter answered:
Cheers!

Thanks for the tips fuchsr and Neophyl!

I'll search for and create a few items in the github issue tracker!

Posted : 04/09/2021 2:45 pm
Share: