You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
+1, it seems like PrusaSlicer has been generating many feedrate changes for me as well, either due to Arachne perimeter generation, perimeter autospeed, or dynamic overhang speeds, and I've been needing to resort to printing from Klipper's virtual sdcard
I have problems like in Issue #124.
It seems to occur when the gcode has many flowrate changes.
I commented out this section:
In the result the prints were flawless.
Could you please add a possibility to disable reacting on feedrate changes?
The text was updated successfully, but these errors were encountered: