Roman Tyr

I was also curious about it and I got this answer: The firmware internally maintains an absolute counter even if it is addressed relatively in the g-code. This G92 E0...

I am not sure I can answer that question properly, maybe @bubnikv can.

No response.

You can try to change g-code resolution on advanced tab (higher value = lower g-code resolution). Overall it seems more like FW issue, since standard g-code works fine on Marlin/Klipper/RRF...

https://github.com/prusa3d/PrusaSlicer/releases/tag/version_2.7.1

It looks this happens when running MK3 gcode on MK3.5 printer, likely unwanted FW behavior, forcing 170C for MBL even when it is not included in the start gcode.

Could you please look at this @pmjdebruijn ?

already answered here https://github.com/prusa3d/PrusaSlicer/issues/12335#issuecomment-1969505974

It made sense on MK3S, but not so much on MK3.5, since even 0.20 SPEED already prints so fast, that it is close to the volumetric speed limits of the...

It will print fine, but slower. The speed is limited automatically by volumetric speed limit.