Bogdan Kecman

btw is there a way to add to on_error some code to display g-code line number and content of that line to console?

> > @SoftFever change to relative extrusion mode. I prefer relative extrusion mode myself but I'm just testing klipper for the first time (RRF/Smoothieboard mostly till now) so didn't want...

major changes from "default" (that worked for a while with .4mm nozzle) - .8mm nozzle - .95mm retraction - .80-96mm line width - .5mm layer height

tried now 1.9.0-beta same problem :(  ~~~ 52678: G1 X157.084 Y163.502 E1.03131 52680: G1 X157.143 Y164.24 E10.04082 ~~~ so 9mm of filament into 1mm movement :( probbly more places...

Move exceeds maximum extrusion (166.142mm^2 vs 44.000mm^2) 1.9.0-beta project [bug-1.9.0-beta.3mf.zip](https://github.com/SoftFever/OrcaSlicer/files/13816487/bug-1.9.0-beta.3mf.zip)

will do thanks... I found another issue, again huge E movement but now outside of WIPE  it is not as huge but retraction is 0.95mm and I see here...

> I've reproduced it. Will look into fixing it. In the mean time you can enable relative extrusion and add G92 E0.0 in the "after layer change" gcode section of...

@igiannakas :D I am not even using a fan :D :D :D no clue why is that set at all will try in a minute thanks ... you want me...

1.8.1 on win11 - when I set fan speed-up time and fan kick-start time to 0 produced G-code that worked flawlesly testing 1.9.0-beta arm64 now

1.9.0-beta finished ok after speed-up time and fan kick-start time are set to 0 So this is a good workaround for the problem :D