Custom Profiles lost on P. Slicer Update  

RE: Custom Profiles lost on P. Slicer Update

So found the old ini's - imported them, and they don't work - the filament profile overwrites the printer profile and the print profile ... and it looks like all my profiles need to be recreated to try out the alpha build.

RE: Custom Profiles lost on P. Slicer Update

From the release announcement on GitHub:

To let you enjoy the alpha without worries, the alpha builds save their profiles into PrusaSlicer-alpha directory, so you may use the alpha side by side with the current release without ruining your production configuration.

So where ever on your computer the settings/configuration folder for PrusaSlicer is stored, there should be one adjacent called "PrusaSlicer-alpha".

I would advise against copying the alpha files on top of the official distro. What I've done in the past is create a folder for the current alpha/beta on my desktop (or somewhere else in user-space on your harddrive(s)) and copied the contents of the zip there. That way you still have access to the previous "stable" release should you run in to a bug that blocks your workflow. (This is an alpha release, possibly critical bugs are expected and more of them in a beta release.)

For you, I would suggest reinstalling 2.0.0, and then empty the zip archive of the alpha somewhere else convenient. Fire up 2.0.0 and save out the config bundle. (If you don't have any SLA profiles saved, expect 2.0.0 to crash, but then open the .ini file in a text editor and delete the partial last section.) Then import the config bundle .ini file into the alpha. Hopefully you should now have all your custom profiles in both.

Note, the profiles are saved in different places, so if you change/add your custom profiles in one you will have to export and import config bundles. I haven't installed 2.1.0-alpha1 yet, so I'm only assuming that the config bundles will be forward and backwards compatible (obviously new features would be lost when transferring the config bundle from 2.1.0-alpha1 to 2.0.0) based on this method working during the Slic3r 1.42 betas and alphas.

RE: Custom Profiles lost on P. Slicer Update

My method of testing is to use the code in as close to real life settings as possible, and that includes install locations.   It finds more oddities that way.  Having folders change in the code is just one more place defects can come in when moving from alpha to beta to rc to release.  Anywhere fingers touch the process.

I just dump the code into the normal install folder ... and seems I am suffering punishment for doing so.  

In the process though, seems I discovered a defect in importing configs.  Load a filament config and it appears it is considered global and affect printer and print settings, and locks you out of using any builtin configs until you reload the app ... and then you have multiple copies of whatever you imported and they appear in all three profile selectors -- e.g., an imported PLA profile showing in my Printer profile selection seems broken, no?

RE: Custom Profiles lost on P. Slicer Update

FWIW: Installation on MacOS 10.14.6 Mojave also resulted in lost configurations (or simply did not import them). This was using the direct download from GitHub and not using the full installer. I was able to easily import configuration bundles without issue and all appears to be working.