Inelegant PrusaSlicer presets?
I finally got around to adding Octoprint and a pi to my Prusa printer. I had some pretty odd behavior initially but finally found out that the printer setting in the slicer needed the "verbose" setting turned on. No problem. I made the change and then tried to save it to the preset but couldn't. I have read some comments that say the system settings cannot be changed? Were earlier versions of the slicer like that as well? I kinda remember being able to change the presets AND save them.
In any case, unless there is some means by which I can edit the presets (and I should be able to save something like verbose across multiple print profiles) the inelegance of it all just didn't seem consistent with everything else I've experienced with my printer. Since Octoprint is such a popular platform, it seems like the default from the factory should be that verbose is on, not off.
Anyway, if anyone knows of a way to edit and save these system files, I would appreciate you sharing your knowledge.
RE: Inelegant PrusaSlicer presets?
You cannot overwrite the system profiles. You can, however, just give them a new name when you hit the save button. Prusa automatically updates the system profiles, so to avoid stepping on user changes and no doubt ease their support challenges, system profiles are read-only.
You can change whatever you want in your custom profiles. Here's a related thread that might be useful. Not everything is perfectly smooth in the GUI -- there have been a lot of changes under the hood lately -- but the mechanics underneath are solid. Hopefully the UI will get some attention soon.
RE: Inelegant PrusaSlicer presets?
FWIW I use Octoprint and PrusaSlicer exclusively and I've never set verbose mode. If always assumed, perhaps wrongly, that that mode was available for debugging.
RE: Inelegant PrusaSlicer presets?
@towlerg
Do you use Octolapse? Maybe I'm mixing up my facts a little and it was the plug in causing the issue? Switching to verbose fixed it. First time I tried printing something with Octoprint, the Mk2 would fail on the 4th bed leveling. Additionally, the bed and nozzle temps weren't being set. I don't recall if I installed Octolapse before running my first print, but I think so. Changing to verbose was the fix.
RE: Inelegant PrusaSlicer presets?
@sherri
Sorry don't know anything about Mk2. Generally the trend is towards reducing the size of GCode. Maybe theres something odd about the way Mk2 buffers data? Ultimately what ever works.
Can I suggest you post on OctoPrint and Prusa MK2 forums.
Two examples of reducing size of GCode -
Arcwelder converts the multiple moves used to generate a curve. Meatpack implements a reduces the number of bits per char.