Fun discovery of the day: PrusaSlicer (at least for the Mini) actually _enforces_ the machine limits by emitting appropriate G-code when slicing. Among other things, this means that if you want, say, higher accelerations, you can just request them.
This is probably because the Mini can't save anything to EEPROM, which means any change to presets requires a firmware upgrade.
Unfortunately, I stopped caring about the acceleration limits and everything in #PrusaSlicer since I started to run #Klipper because it actually tells you that the limits are only for time predictions and aren't Ctually emitted to #Gcode.
But when you use #OrcaSlicer and you insert custom accelerations and dynamic-overhang-speeds and limits, the printer actually honors it.
So, not only are my time predictions with OrcaSlicer more accurate, but I am actually printing at the rate that I want to and chose in the slicer.
But then finally, I have to say. OrcaSlicer does not honor flow-rate limits as well as PrusaSlicer does. If I tell PrusaSlicer to never exceed 12mm^3/s, it would slow itself down.
OrcaSlicer justs YOLOs itself past that limit, and my exteuders start to skip!
The other thing is. With #PrusaSlicer in the printer's custom #Gcode where you set the start, end,layer-change, etc. Gcode. You can access variables such as temperature and layers, etc.
You, however, can't access variables like acceleration limits and use those values to emit them to your Macros when you run #Klipper.
So I need to look at a print, think a bit. Set limits in Klipper, transfer said limits to #PrusaSlicer, generate gcode, and then print.
#OrcaSlicer actually will honor your request to print slower or faster, but there is something wrong with its flow rate.
If you slice an object and switch to the flow-rate view. The color codes clearly show that it exceeds your set max. However , in speed-view, you can see that the speed is correct. And in #Mainsail during printing and can actively see how it changes the acceleration limits as it prints overhangs, perimiters, and briges.
As you can see, I am between 2 slicers here
@Stark9837 @3dprinting You actually can: https://help.prusa3d.com/article/list-of-placeholders_205643#placeholders-for-configuration-options
This can definitely be used for printer options, which is where the acceleration limits are set.
@Stark9837 @3dprinting Heck, PrusaSlicer's stock starting G-code for the Mini even does this:
M204 T[machine_max_acceleration_travel] ; restore travel acceleration
Koz Ross
Stark