Shared folder for Slic3r filament profiles
At my FabLab we have several computer and I'm looking for a solution to safe additionals filament profile on our network.
Is there a possibility to outsource the profiles to a network folder? Also I'm interessted to know how I can change the modified settings in the new filament settings into "green" ones.
Thank you
Patrick
Re: Shared folder for Slic3r filament profiles
Using a network folder will work as long as the network (and OS) is stable. If you've done a lot of work with network drives, however, you'll know that is not a bet worth taking.
It's more complicated as it takes more effort, but setting up something to sync a local directory with the shared version would be better. That way if the network glitches you don't have to worry about how your slicer will react. The best approach would be to sync to one directory and then when you are sure it was successful, sync to the slicer directory. That would prevent partial files (due to a network issue mid sync) from messing you up.
Probably the best solution if you have it available and your team is up to the task would be to use a source control system like GIT. That will make the syncing well for you and you also get a history of who changed/added/deleted what.
Re: Shared folder for Slic3r filament profiles
This sounds like a good use for a sync tool like SyncThing. Set the folder to shared among the various computers, then have the config files synchronized. Alternately, pick one computer as the master and set it to push configs down to the others on sync. It's transparent to the applications, and loss of the network doesn't cause any problems.
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: Shared folder for Slic3r filament profiles
Thank you for your answers.
I understand that using the network could be get problems. However we have all our files on our NAS or in a cloud.
To sync the profiles you have to know where they are. I found the PrusaResearch.ini, but couldn't find the file with the user presets. Also I don't know how I tell slilc3r that the path to the presets has changed.
Re: Shared folder for Slic3r filament profiles
the slicer.ini is being written by all instances pointing to that profile directory. The latest Slic3r PE 1.41.3 and 1.42.0-alpha7 both access the slic3r.ini atomically in a way that it first writes a temp file and then it renames the file in a simple step, but still you have multiple instances of Slic3r fighting for the same slic3r.ini.
Re: Shared folder for Slic3r filament profiles
Sorry, but this is to complicated for me.
I need a simple solution to sync 5 computer with our filament-user-presets. Also I have to provide this filament-presets in a simple way for our members.
Re: Shared folder for Slic3r filament profiles
I use a NAS to store my profiles - the parameter --datadir "<NAS drive>:\Config\Slic3rPE" will tell Slic3rPE.exe where to find the config files.
Not sure if this will work when more than one pc access the files at the same time.
Have a look at my models on Printables.com 😉
Re: Shared folder for Slic3r filament profiles
I use a NAS to store my profiles - the parameter --datadir "<NAS drive>:\Config\Slic3rPE" will tell Slic3rPE.exe where to find the config files.
Not sure if this will work when more than one pc access the files at the same time.
Thank you. That is what I was looking for.
Are there some more fancy stuff like --datadir to open Slic3r. Otherwise why Slic3r don't have a simple config file where I can change the settings?
RE: Shared folder for Slic3r filament profiles
I'm a bit late in this thread, but your Inputs helped me very much and I wanted to ask if somebody tried to put the files on Onedrive or another cloud service.
I think I'll give it a try to sync my settings and if I remember, I'll update my findings here.
Just came to my mind, this would be a great opportunity for Prusa to deliver a community based filament database. @prusa: if you read this, maybe this would we a feature request worth trying.