Grippler

Is there a slicer that let's you configure sections of the model to print at a different layer height?

I often have some larger models I'm printing, and 0.3mm layers are just fine for this to speed things up, but some of the overhangs print very poorly with thick layers and require thinner layers to print well.

I recently made the switch from the marlin-based stock firmware on my anycubic kobra 2, to klipper. I didn't have issues with bed levelling or first layer on the stock firmware, but I'm having significant issues running klipper. The bed is uneven, the probed mesh shows a deviation of 0.197mm, it was the same when running stock FW+octoprint.

But it seemed to be correcting just fine for this on the stock FW. I got a consistent decent first layer across the entire bed.

With klipper, it's absolutely impossible to get it to correct for this unevenness. Half the bed will get perfect first layer, but then the second half is either way too squished or hardly connecting to the bed. And it's causing further issues as it's also hitting the print when moving, despite having Z-hop of 0.3mm for travel moves.

What the hell is going on? How do I fix this?

I have this incredibly loud noise coming from my Y-axis. It doesn't affect print quality, but it is horrible to listen to and really loud. It is present when the Y-axis moves at ~100mm/s and gets worse/louder as speed increases.

How can I mitigate this? There doesn't seem to be any mechanical issues when I move the bed by hand, it is smooth and easy to move.

I'm trying to do some temperature calibration, using the M104 command to change hot-end temperature on the fly between layers/sections of the tower.

It consistently waits a few seconds for the temperature to stabilize whenever I trigger an M104 command.

I have inserted my gcode in the "before layer change" section, it looks like this

{if layer_z >= 1.05} M104 S220 {endif}
{if layer_z >= 11.05} M104 S225 {endif}
(etc.)

With different layer_z values for the different temperature sections up to 260°C

I can't find anything in the marlin documentation that would cause this, only M109 should trigger the waiting AFAIK?

I have checked the generated gcode, and it only uses M104 commands.