Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Slicing dialog not disabled for locally running slicers while printing #1631
What were you doing?
When a print operation is running, meaning commands are being send to the printer slicing will not give any result. When trying to slice a file while printing operation is running you do net get any feedback and there is no visual response.
When trying the trigger a slice operation while the an other print operation is running you get the same result, Nothing happens. But you get a 409 error back.
What did you expect to happen?
I expected it to continue doing its printing operation and that it started slicing simultaneously.
What happened instead?
As described earlier nothing happend.
Branch & Commit or Version of OctoPrint
Version: 1.2.18 (master branch)
Printer model & used firmware incl. version
Printer: Ultimaker Original plus
Browser and Version of Browser, Operating System running Browser
The issue is not effected by the browser or operating system it is run on.
Link to octoprint.log
Link to contents of terminal tab or serial.log
The Terminal output was the same as when I am just printer and not trying the slice simultaneously.
The JS console did not give an exceptional output.
Screenshot(s) showing the problem:
There is literally nothing to see. That is part of the problem.
I have read the FAQ.
That it doesn't slice while printing is intentional. Slicing (on a Pi) eats a lot of system resources. System resources that are needed to pump data to the printer to actually print. So OctoPrint disables slicing while a print is ongoing (if the slicer plugin in question signals that it slices on the same system, which the bundled CuraEngine plugin does) in order to prevent prints from failing due to resource issues.
Now, OctoPrint should actually disable the slicing controls in its UI for such locally run slicers while printing for that very reason (as should any slicing related plugins for that matter), but apparently that broke sometime ago. I'll take a look.
@noahlvb Sorry, I somehow missed your follow up question until I opened this ticket to tackle it just now... There is no way to enable slicing on local slicers concurrently without modifying the code of the slicer plugin in question.
The problem with the UI inconsistency here has been fixed on the current