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
It looks like there is some information missing from your bug report that will be needed in order to solve the problem. Please take a look at the Contribution Guidelines which will provide you with a template to fill out here so that your bug report is ready to be investigated (I promise I'll go away then too!).
If you did not intend to report a bug, please take special note of the title format to use as described in the Contribution Guidelines.
I'm marking this one now as needing some more information. Please understand that if you do not provide that information within the next two weeks (until 2016-02-15 22:50) I'll close this ticket so it doesn't clutter the bug tracker. This is nothing personal, so please just be considerate and help the maintainers solve this problem quickly by following the guidelines linked above. Remember, the less time the devs have to spend running after information on tickets, the more time they have to actually solve problems and add awesome new features. Thank you!
Best regards,
~ Your friendly GitIssueBot
PS: I'm just an automated script, not a human being, so don't expect any replies from me :) Your ticket is read by humans too, I'm just not one of them.
What were you doing?
Slicing model with built-in Cura plugin.
In the Cura profile (.ini file) profile there is a line
"retraction_combing = All"
What did you expect to happen?
Slicer should slice with combing on.
What happened instead?
Combing is off.
Branch & Commit or Version of OctoPrint
Version: 1.2.8 (master branch)
Problematic code: https://github.com/foosel/OctoPrint/blob/536bb31965db17b969e7c1c53e241ddac4ae1814/src/octoprint/plugins/cura/profile.py#L868
How it actually should be handled: https://github.com/daid/Cura/blob/16cc0fa302f1ceccde229fdab6359bdbdc08b70c/Cura/util/sliceEngine.py#L533
The text was updated successfully, but these errors were encountered: