PruseSlicer 2.2.0-RC2 has corrupted my config
I have been using Slic3r for a fair time and worked my way through releases with zero issue and through each upgrade found my config remains. As such, my "current" release is 2.1.1.
Tonight I figured I would try the 2.2.0-RC2 build, just to see if there were any new features.. This isn't the first time i have tried a Beta or RC so I wasn't too worried... And it was fine, or so I thought.
When I ran 2.1.1 again I was told that my config was corrupted and now when I launch either 2.1.1 or 2.2.0-RC2 all of my settings are gone..
Is there any kind of "backup" held anywhere.. Is there any way to get my config back?
Interestingly I just notice that I have an instance of 2.1.1 still running and all my config is there.. Is there any way to save or export what I have whilst I can?
RE: PruseSlicer 2.2.0-RC2 has corrupted my config
I fixed it.. By drilling down into the file system I found a "snapshot" folder with lots of "backups".
I realised then that there was a "configuration snapshots" option on the GUI where I could 'activate' old configs.. But when I did this I got an unknown exception error and Slicer crashed.
So in the end I copied the files from the last snapshot folder.
When I ran 2.1.1 again I was told that the config was incompatible as it was for 2.2.0 and Slicer quit and lost the config.. So i had to go back to an earlier snapshot until I found one that worked.
It seems that 2.2.0 modifies the config and after this you can't run 2.1.1 again.. Odd as I use to have Official releases and Betas running at the same time.
Either way its fixed now and I think I will wait until the final 2.2.0 release before I upgrade again.
RE: PruseSlicer 2.2.0-RC2 has corrupted my config
Before updating any version always go to file and save a configuration bundle. That way you can load a new clean copy of slicer in on any machine and any version (alpha/beta/release) and later import all your configs (print, filament and printers).