You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've got duplicate last frames set, but I'd really prefer that last frame to be after the print head moves up and away from the print and I've got those moves in the PRINT_END macro.
Since I'm using the TIMELAPSE_TAKE_FRAME macro in Before Layer Change I thought the slicer is controlling the frames, so what I tried to do is add an additional TIMELAPSE_TAKE_FRAME after the call to print_end in the End G-code section of the slicer - my thought was that this keeps all of the timelapse control in the code generated by the slicer. I thought this would allow the print_end to move the print head and then it would take that additional frame after the move that would get stretched out by the render, but it didn't work. It appears that the render gets triggered by the print end state and not the end of the gcode.
So I'd be interested in some clean way to do this which may or may not involve a code change.
The text was updated successfully, but these errors were encountered:
I've got duplicate last frames set, but I'd really prefer that last frame to be after the print head moves up and away from the print and I've got those moves in the PRINT_END macro.
Since I'm using the TIMELAPSE_TAKE_FRAME macro in Before Layer Change I thought the slicer is controlling the frames, so what I tried to do is add an additional TIMELAPSE_TAKE_FRAME after the call to print_end in the End G-code section of the slicer - my thought was that this keeps all of the timelapse control in the code generated by the slicer. I thought this would allow the print_end to move the print head and then it would take that additional frame after the move that would get stretched out by the render, but it didn't work. It appears that the render gets triggered by the print end state and not the end of the gcode.
So I'd be interested in some clean way to do this which may or may not involve a code change.
The text was updated successfully, but these errors were encountered: