Making user customizations to the ini sticky
Decided to modify the "output_filename_format" in the ini file so I could avoid a lot of typing each time I export gcode. However, I cannot seem to make it work.
I have edited every entry in:
...\Prusa3D\PrusaSlicer\resources\profiles\PrusaResearch.ini
but it still tries to save using the original (very long) filename. I also tried exporting a config bundle, editing it, and importing. Same result. If I export a new config bundle after importing my edited version, the new config bundle does reflect my changes. However PrusaSlicer seems to be ignoring all "output_filename_format" entries. Suggestions?
On version 2.1.0
RE: Making user customizations to the ini sticky
Just save copies of the defaults with the setting overrides you desire. Make your change, hit the save icon and give it a new name. I put a date stamp on my configuration changes.
and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan
RE: Making user customizations to the ini sticky
That works - just tedious to do for all profiles and then I end up with a bunch I will never use. Was hoping for a way to modify things outside the tool so I could use search-replace to apply to all profiles. I suppose if the user presets appeared above the system presets so I didn't have to scroll to them that would help. As I type this I realize it sounds really nit-picky. Really, I'm not that bothered by it - was just wondering why my attempts to modify the system presets failed and if anyone worked out how to do it.
RE: Making user customizations to the ini sticky
[...] Was hoping for a way to modify things outside the tool so I could use search-replace to apply to all profiles.
You can create your own config bundles. I make use of the inherits = feature to minimize duplication of effort. Any profile will inherit any settings specified under the profile listed by name in an inherits = line. You can use this to create sub-profiles that only marginally differ from the parent. I've got a (rough) example here. If you import this as a config bundle, you'll end up with a bunch of profiles. Unfortunately, if you then export your settings as a config bundle, each profile is complete, meaning you'll need to maintain your "master" bundle with the inherited sub-profiles separately. It's a little annoying, but it saves me a lot of work, especially with printer profiles where I want common gcode across all my profiles.
I suppose if the user presets appeared above the system presets so I didn't have to scroll to them that would help. As I type this I realize it sounds really nit-picky. Really, I'm not that bothered by it - was just wondering why my attempts to modify the system presets failed and if anyone worked out how to do it.
You could probably hide them through clever use of the dependencies. I use this to hide unusable layer heights in print profiles based on the nozzle size I've selected in the printer profile.
and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan
RE: Making user customizations to the ini sticky
@bobstro
Cool. Lots of good stuff here - thanks!