-
-
Notifications
You must be signed in to change notification settings - Fork 890
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wall gaps from unretract on inner wall when there is no inner wall #1704
Comments
After reading the emitted gcode and experimenting with patching the source, I'm pretty sure I was wrong about the cause of this problem. It's not that the unretract at the beginning of the wall happens in the wrong place (somehow, it doesn't) but that the final retract before moving to the start of the next layer is happening at the wrong place. |
One thing I'm confused about is why one of these places is pulling the wall line count and width settings from |
any update on this? I am seeing this also 😢 |
Here's the (mildly sloppy from rebase after a conflicting patch prettied up formatting) draft patch I'm using that fixed it:
|
The fix for #1458 (commit db248b2) seems to have caused gaps in the outer wall when printing with a single wall, due to unretracting on top of an inner wall that does not exist. The below image shows the effect (right) in a hollow cylinder printed with no infill and only one wall, versus the same created with actual hollow geometry (so that there is no "interior" to move the nozzle into before unretracting).
It was not actually this commit that created the bug; it just exposed it by activating the functionality. The bug is just the logic to travel inside the model before starting the outer wall, which should only be done if the wall line count is greater than one. However the logic added in that commit probably needs to be reviewed too, as it might be wrong without this travel move being present (it might move the unretract before a different/much longer travel move, which would be even more harmful).
The text was updated successfully, but these errors were encountered: