Distribute PrusaSlicer Machine config *with* bed model and texture
I've got a machine configuration that I've built out which includes a bed model and texture. I know that I can use the "Export Config Bundle" option to export all the settings. But that's just a plain .ini file and does not include the bed model or texture. In fact it contains only a absolute path link to where I had it saved locally.
Is there any way (even if I have to set it up manually) package a **complete** machine configuration including the bed model and texture so that it could be distributed to customers of a new printer design I'm testing?
Only thing I can think of now is to create some sort of installer that saves those files into the PrusaSlicer directories but, honestly, that would be a real pain.
It's made a bit more challenging trying to be compatible with Windows, Mac and Linux installs. I've had limited luck using relative paths, but would also be interested in a clean way of packaging customizations.
Wow - I'm honestly surprised no one has done this 🙁
Wow - I'm honestly surprised no one has done this 🙁
Its a new feature and not well documented. Some sort of installer script is probably the easiest solution at this point, but finding a good cross platform.option is a challenge.
I have been using the relative paths that Bob mentioned on all the various versions I have on my USB stick.
The following is for windows but might be applicable to other OS. Maybe.
So in each folder (v2.2.0, version 2.3.0 etc) I have a "start.bat" file. All it contains is ".\prusa-slicer.exe --datadir .\profiles" This tells the software to start and use the configuration info stored in the profiles directory. The profiles directory is a copy of whats normally stored at the normal configuration folder location. So when I use start.bat it launces and uses the data on the USB stick. That way its portable from machine to machine, ie home and work.
Also whenever they release a new version I can extract it to a different folder and copy the profiles folder and start.bat to the new version folder. When I launch that from its start.bat then all my profiles and settings get picked up without having to go through the wizard or do a config import. I do still perform regular config bundle exports for backup though.
I have just checked and if you store your svg and bed.stl assets in the profile folder too and point the printer config to that location then when you copy profiles and start.bat over it knows where to look for them so it works.
Not quite a package process but it just means copying one folder and a batch file for each new version and for running on multiple machines the folder is portable so could be copied to the hdd or a removable media like I use.
[...] So in each folder (v2.2.0, version 2.3.0 etc) I have a "start.bat" file. All it contains is ".\prusa-slicer.exe --datadir .\profiles" This tells the software to start and use the configuration info stored in the profiles directory.
This is the eternal bliss of cross-platform programming: Dealing with OS-specific paths. It's easy enough to work around with a small python script, but python isn't available on Windows out of the box (or is it with Win10?). A shell script works nicely for macOS or Linux, but not Windows. You have to consider drive letter specification on Windows, but not macOS or Linux. A Windows batch file is simple but won't work on macOS or Linux.
A full installer might work, but either costs money or is overkill. I tried to deal with this back in the 1990s, and am dismayed to see it's still a pervasive problem. I'm happy to write up howto articles, but would really like to be able to put together a simple installer for one-click installation. It would be nice if Prusa ultimately incorporates something into PrusaSlicer itself to simplify this process... but then again, it would only benefit 3rd party printer manufacturers to do so.
Yeah.... all those *could* work... but was trying to find something that would work for more novice users and not require having them muck with their PrusaSlicer profile data directories.
Heck - mine is all sorts of weird since I actually have separate profile directories for each machine type I have, using the --datadir, option. Because I absolutely **hate** how PS manages different machines and the associated print/filament profiles. It was just easier to keep them all separate.
But, thanks for the input @neophyl - that basically answers my question 🙂 Hopefully this becomes a feature in the future - maybe I'll try to add it myself 😉
[...] Heck - mine is all sorts of weird since I actually have separate profile directories for each machine type I have, using the --datadir, option. Because I absolutely **hate** how PS manages different machines and the associated print/filament profiles. It was just easier to keep them all separate.
I've got the dependencies all figured out and am able to keep my 2 printers nicely separated running one instance of Prusaslicer. I would like to a separate PrusaSlicer instance for each printer at the same time. Does --datadir let you open 2 instances at the same time and keep them sanely separated? (I should just test it, but hoping someone else tried it already.)