Vojtěch Bubník

@FormerLurker Please read #6336 #5073. Shortly, Marlin reads relative E, adds it to its accumulator, then calculates the difference against the previous accumulator and passes the difference to the planner...

@bitingsock > > In absolute E mode, PrusaSlicer currently emits G92 E0 on each retraction. > Is there a reason for this? It makes extrusion-based gcode post-processing needlessly difficult. The...

Also in Bambula https://twitter.com/stlDenise3D/status/1623878580814901249 https://twitter.com/bubnikv/status/1623969126967394306

> My guess is that the PrusaSlicer keeps the file open for writing instead of closing (or at least flushing/sync-ing) it when done with the write. Frankly it seems to...

It happens on Windows only and it is extremely, really extremely rare. We went to such lengths as to save the file twice, adding checksums etc, but there seems to...

Klipper uploading is supported: Just select OctoPrint target. Klipper firmware is supported: Just select Marlin legacy firmware and follow Klipper manual.

Most likely we will implement Klipper support to PrusaSlicer 2.6

Supports are generated per object, and collisions of objects are not tested by Slic3r. This is a known issue.

That is a natural request. BTW PrusaSlicer implementation currently behaves the same way as in Cura, including this particular modifier behavior.

We understand the request perfectly. It is just about the effort and priorities. If you read the responses after each PrusaSlicer announcement, "Still no tree support?" is at the top....