Uncaught exception: (1): '=' character not found in line
Got up this morning and found I can no longer launch PS2. Get the above error each time. Restarted PC, no help. Redownloaded latest PS2 files (not the alpha version), no help. Removed everything in local\Appdata\temp, no help. Windows 10 64-bit
I suspect this is a corrupted config file being called when PS2 launches, but I don't know where they are hidden.
Any ideas?
T'IA
RE: Uncaught exception: (1): '=' character not found in line
Never mind - found the config info in C:\Users\Frank\AppData\Roaming\PrusaSlicer. I moved the entire PrusaSlicer folder to a different location, and then was able to launch PS2. Then by comparing the newly regenerated PrusaSlicer folder and the old one I was able to determine that the .ini file had gotten corrupted and this was causing the startup error.
All is well, crisis averted 😉
RE: Uncaught exception: (1): '=' character not found in line
There's an open issue about this on github. However everyone who suffers it seems to just delete the folder and generate a new one leading to the devs not having info needed to figure out why its happening. If you still have the corrupted folder it might be handy to zip it up and attach it to the issue on there to give them something to work with.
RE: Uncaught exception: (1): '=' character not found in line
I do have the corrupted file, and I'll send it along to the dev folks
RE: Uncaught exception: (1): '=' character not found in line
We don't know why it is happening, but we have a hypothesis. It happens on Windows only. The PrusaSlicer.ini is first stored into a temp file, and then it is renamed to the target name atomically. It is known that file renaming is a finicky feature on Windows. We applied some magic to the PrusaSlicer 2.1.0-beta2, which hopefully fixes this issue.