BUG Can't change G-code Flavor since 5.3.0

[doubletrouble023 1]

Previously I've been jumping back and forth between Marlin and RepRap flavor. ( I'm running Klipper )

Mostly I just use Marlin, but whenever I need to postprocess a gcode, (continue a failed print for example ) I switch to RepRap because it uses relative extrusions.

 

It is set to RepRap now and when I try to change it, it just goes back again.

Can't slice a file with another flavor anymore, tried saving, restarting etc. Only chance might be to create a new machine perhaps. But I'd like to find a better solution for this if possible

 

Ideas?

Edited March 30, 2023 by doubletrouble023

[RadianM 0]

Same issue and creating a new machine doesn't fix it for me. Stuck with Marlin so Reprap extruder isn't at all happy.

[doubletrouble023 1]

Alright, then I'm not alone at least! Then it is a new "feature" of 5.3.0

 

I hope devs are looking into this, I've tried going through all files that felt relevant in AppData folders to see if I could change the flavor for the machines there but I didn't find such a solution.

 

[RadianM 0]

12 hours ago, doubletrouble023 said:

Alright, then I'm not alone at least! Then it is a new "feature" of 5.3.0

 

I hope devs are looking into this, I've tried going through all files that felt relevant in AppData folders to see if I could change the flavor for the machines there but I didn't find such a solution.

 

 

This kind of issue has cropped up in previous versions so it seems to have regressed. I don't know what differences the flavors make but I can't get extrusion to behave. I think I found out how to set cura to issue relative moves for the extruder in  the "special modes" settings but the E motor is skipping furiously when attempting to print with Marlin flavor.

 

Back to PrusaSlicer for me now. 🙄

[Piov666 0]

Same issue here too ^^

It's so frustrating :D

[doubletrouble023 1]

6 hours ago, Piov666 said:

Same issue here too ^^

It's so frustrating :D

Very much so!

I haven't found anything that could help unfortunately  :/

[rburema 26]

Hi! Dev here (Community manager is on holiday atm).

 

Can confirm that this happens on our side as well. I've put it on the list of things to discuss with the team w.r.t. future fixes.

It seems that the mechanism that saves the data is blocked somehow, the loading still works, that means that there is a workaround.
 

If you change this frequently, then the following isn't much of a solution, but here it goes: You can still change it outside of Cura by manually adjusting the config file. Turn Cura off first to avoid potential confusion. It should be in %appdata%/cura/5.3/definition_changes (so probably something like C:\Users\U.Sername\AppData\Roaming\cura\5.3\definition_changes\awsomeprinter.inst.cfg or similar). In that file, make a new line that reads machine_gcode_flavor = Griffin (substitute the exact string in the dropdown menu you need to be selected). Save the file and it should work. If this causes trouble, don't reset, but close Cura and remove the line (and/or try again w.r.t. spelling errors and the like).

[rburema 26]

The rest of my team indicated that they think this is a fix we did for the upcoming 5.3.1 -- When testing from latest source I indeed can't reproduce this anymore. That version should (have) be(en) out ... already actually, but we've run into some translation related troubles. We still expect April though.

[cjh83 0]

I tried 5.3.1 and the same thing happens. The print resumes at the incorrect height. 

 

 

[Slashee_the_Cow 266]

11 hours ago, cjh83 said:

I tried 5.3.1 and the same thing happens. The print resumes at the incorrect height. 

Have you tried 5.4 or the 5.5 beta?

[GregValiant 1,251]

The Machine Settings dialog box had some issues starting with 5.0 and the move from QT5 controls to QT6.  I know that the "Bed Shape" would always revert when the dialog was closed and I believe the Gcode Flavor also wouldn't keep a new setting.  The workaround was to adjust the printer definition file to reflect what you wanted.

5.4.0 doesn't suffer from the problem and it doesn't seem to have reverted in 5.5.