Cannot load config from gcode on Prusa Slicer 2.0
Hello everyone,
I've been using Prusa Slicer 2.0 since it came out, and I just found out that trying to load the config from some g-code files I have generated with it throws this error:
I use no other slicer by the way. Any clues as to why this happens?
Edit: the error message reads
"PrusaSlicer has encountered an error
Not a Slic3r generated g-code."
Best Answer by Neophyl:
AFAIK its a known bug at the moment. A bit of an embarrassing one really. Theres a header line in the gcode that says what slicer it was produced with and when, for example "; generated by PrusaSlicer 2.0.0+win64 on 2019-05-29 at 15:05:03" if its Prusa 2.0 it rejects it. You can manually use a text editor to modify the gcode to replace the header with one from an earlier version and then it will accept it if you really need the settings from that gcode as a work around until its fixed. for example "; generated by Slic3r Prusa Edition 1.41.2+win64 on 2018-12-25 at 16:58:14"
RE: Cannot load config from gcode on Prusa Slicer 2.0
AFAIK its a known bug at the moment. A bit of an embarrassing one really. Theres a header line in the gcode that says what slicer it was produced with and when, for example "; generated by PrusaSlicer 2.0.0+win64 on 2019-05-29 at 15:05:03" if its Prusa 2.0 it rejects it. You can manually use a text editor to modify the gcode to replace the header with one from an earlier version and then it will accept it if you really need the settings from that gcode as a work around until its fixed. for example "; generated by Slic3r Prusa Edition 1.41.2+win64 on 2018-12-25 at 16:58:14"
RE: Cannot load config from gcode on Prusa Slicer 2.0
Thank you very much for your reply, I will do that for now.
RE: Cannot load config from gcode on Prusa Slicer 2.0 STILL (not solved)
still waiting on a fix 🙄
noone has been "assigned" to the issue on github, since its still a mixmash of slic3r and PS in the code base . most references to version is actually still Slic3r, and not a new name that actually matches the new stuff, thats where the problem is. config export is acting right, import is still old code looking for the Slic3r version. it can care less about the version number
bang the GIT together guys. or revert the name import check
"Semver" is a good place to start
and we’ll be saying a big hello to all intelligent life forms everywhere … and to everyone else out there, the secret is to bang the rocks together, guys.
RE: Cannot load config from gcode on Prusa Slicer 2.0
Migamix,
Does this also apply to exported config.ini files? I get Prusa Slicer 2.0 to crash when exporting config bundles. When I try to import them I get a similar error. Replacing the " generated by PrusaSlicer" line gives yet another error.
Any thoughts?
RAH
I am the inveterate tinkerer. I can tink up most anything.
RE: Cannot load config from gcode on Prusa Slicer 2.0
That error is not related. Looking at it it’s expecting a = at some specific spot and it’s not there. You can open up the config file in a text editor and have a look but it can be hard to spot.
RE: Cannot load config from gcode on Prusa Slicer 2.0
Thank you. I will start another thread for this issue. I have emailed the issue to Prusa.
BTW, I have linux tools to search for the missing '=' sign. 😉
I am the inveterate tinkerer. I can tink up most anything.