"Advanced User Control" setting or something along those lines. #1249

New Issue

MrUnknownDE · 2026-04-05T17:06:00+02:00

MrUnknownDE commented

2026-04-05 17:06:00 +02:00

Originally created by @jefftopp1984 on 12/28/2025

Is there an existing issue for this feature request?

I have searched the existing issues

I am an extremely advanced Klipper user. My printers are very "state aware" and I have a fully guided readiness/initialization process that actually will prevent a print from starting unless the initialization process has been completed. It's not just whether the printer is homed and heated correctly. It actually uses checkpoints through the multi-stage initialization process that asks the user if they would like to level the bed first, it heats, prompts the user to remove any oozed filament from the nozzle, then homes, prompts the user to place a sheet of paper on the bed under the nozzle, lowers the head to 0.1, prompts the user to use the paper as a feeler gauge to see if the Z gap is correct, allows adjustment at that stage if it's not, then either parks ready to print or it begins the BED_MESH_CALIBRATE process. After the bed leveling, it automatically saved, restarts, reheats, rehomes, and then prompts the user again to check the Z gap as a confirmation after the new bed mesh is loaded. And it'll allow the adjustment here again if it is not. Throughout those macros, it sets several variables that tells the printer whether this initialization process has been completed. If it has not, the _START_PRINT macro, which is the ONLY thing in the start print gcode section, will actually REJECT starting the print, display an error message with choices on what the user would like to do, and immediately cancels the print. If it detects any of those initialization steps have not been completed, it will tell the user what has not been completed and ask if they would like to do that now or just cancel. So, all that being said, I also have macros that are in control of the nozzle heater, bed heater, fan, and everything else. It seems that some of the built-in readiness and thermal coding of the slicer is getting in the way and I've had to use post-processing scripts to remove those commands as they are redundant, interfere with my process, and are doing more harm than good. I'm sure I'm not the only user that has an advanced setup like this, so it would be very nice if there was a quick setting to disable all of that in the slicer so it only provides geometry, speed, and line type comments in the file for the post-processing scripts to read. I have this process because my business partner and his wife have absolutely zero printing experience and I wanted them to be able to use the printers without any issues. It works very well for them, but I've run into some hurdles along the way from the slicer injecting commands that are unwanted. For instance, if you set the bed temperature to be the same regardless of the layer, it will still insert a command after the first layer to keep the bed temperature the same, right after I've paused, parked, and sent the M190 command through my macros and allowed the bed temperature to drop before proceeding. Then it kicks the bed temp back up right then and there, right after I just gave it time to drop! Very annoying. So, if there could be a mode where the slicer would only run the geometry data, speeds, and line types, that would be awesome because then there would be no chance of the system overriding any of my highly customized processes.

Which printers will be beneficial to this feature?

Klipper

Describe the solution you'd like

I already said it above, but a "geometry only" or "advanced user control" setting that turns off all thermal and readiness commands in the slicer.

Describe alternatives you've considered

Running post-processing python scripts to remove these unwanted commands.

Additional context

No response

*Originally created by @jefftopp1984 on 12/28/2025* ### Is there an existing issue for this feature request? - [x] I have searched the existing issues ### Is your feature request related to a problem? I am an extremely advanced Klipper user. My printers are very "state aware" and I have a fully guided readiness/initialization process that actually will prevent a print from starting unless the initialization process has been completed. It's not just whether the printer is homed and heated correctly. It actually uses checkpoints through the multi-stage initialization process that asks the user if they would like to level the bed first, it heats, prompts the user to remove any oozed filament from the nozzle, then homes, prompts the user to place a sheet of paper on the bed under the nozzle, lowers the head to 0.1, prompts the user to use the paper as a feeler gauge to see if the Z gap is correct, allows adjustment at that stage if it's not, then either parks ready to print or it begins the BED_MESH_CALIBRATE process. After the bed leveling, it automatically saved, restarts, reheats, rehomes, and then prompts the user again to check the Z gap as a confirmation after the new bed mesh is loaded. And it'll allow the adjustment here again if it is not. Throughout those macros, it sets several variables that tells the printer whether this initialization process has been completed. If it has not, the _START_PRINT macro, which is the ONLY thing in the start print gcode section, will actually REJECT starting the print, display an error message with choices on what the user would like to do, and immediately cancels the print. If it detects any of those initialization steps have not been completed, it will tell the user what has not been completed and ask if they would like to do that now or just cancel. So, all that being said, I also have macros that are in control of the nozzle heater, bed heater, fan, and everything else. It seems that some of the built-in readiness and thermal coding of the slicer is getting in the way and I've had to use post-processing scripts to remove those commands as they are redundant, interfere with my process, and are doing more harm than good. I'm sure I'm not the only user that has an advanced setup like this, so it would be very nice if there was a quick setting to disable all of that in the slicer so it only provides geometry, speed, and line type comments in the file for the post-processing scripts to read. I have this process because my business partner and his wife have absolutely zero printing experience and I wanted them to be able to use the printers without any issues. It works very well for them, but I've run into some hurdles along the way from the slicer injecting commands that are unwanted. For instance, if you set the bed temperature to be the same regardless of the layer, it will still insert a command after the first layer to keep the bed temperature the same, right after I've paused, parked, and sent the M190 command through my macros and allowed the bed temperature to drop before proceeding. Then it kicks the bed temp back up right then and there, right after I just gave it time to drop! Very annoying. So, if there could be a mode where the slicer would only run the geometry data, speeds, and line types, that would be awesome because then there would be no chance of the system overriding any of my highly customized processes. ### Which printers will be beneficial to this feature? Klipper ### Describe the solution you'd like I already said it above, but a "geometry only" or "advanced user control" setting that turns off all thermal and readiness commands in the slicer. ### Describe alternatives you've considered Running post-processing python scripts to remove these unwanted commands. ### Additional context _No response_

Sign in to join this conversation.

No Label enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/OrcaSlicer#1249