I would like to enhance the time estimate for custom start gcode. My printer is somewhat slow to heat up and I'd like to have the time estimate reflect the actual time for the printer to run from a cold start. A solution could be some information added to the printer profile about heating time or homing time. A simpler solution would be to have a special statement added to the custom gcode that the slicer considers to take time but does nothing on the printer (possibly a special string in a commented out line). I'd be happier to know what the "full time" that a print takes from pressing the start button to completion. This could also be useful to include in the color change gcode as well to account for any special behavior that happens during the M600 statement.
I would like to enhance the time estimate for custom start gcode. My printer is somewhat slow to heat up and I'd like to have the time estimate reflect the actual time for the printer to run from a cold start. A solution could be some information added to the printer profile about heating time or homing time. A simpler solution would be to have a special statement added to the custom gcode that the slicer considers to take time but does nothing on the printer (possibly a special string in a commented out line). I'd be happier to know what the "full time" that a print takes from pressing the start button to completion. This could also be useful to include in the color change gcode as well to account for any special behavior that happens during the M600 statement.