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
Wrong extrusion width when slicing #10259
Comments
I think its just a preview scale issue. Your prime lines are 'fat', hence the scale going to 0-2mm extrusion width. At that scale on the legend everything thats printed with normal extrusion widths looks almost the same colour and its impossible to differentiate the difference between 0.4 and 0.45. The actual printed gcode should be fine. I'm sure this has been reported before. Ah found one of them #8479 |
and also #8777 |
@neophyl in any case, it is a problem for users, no matter how you justify it from your point of view as an advanced or expert user. When users go to the extrusion width preview they see wrong information. |
Issue should be fixed by adding new button in legend and fix will be part of next release. |
…en Custom extrusion paths are set to invisible
Description of the bug, Project file & How to reproduce
1- Add any shape;
2- click Slice now;
3- switch the preview mode to Width and look at the result (image 1); everything will be printed with the lowest extrusion width of the graph
which is equal (or approximately equal) to the Top solid fill (image 2)
4- In the Start G-code, comment out the extruder movement during the purge line (image 3)
5- slice again, now each part of the print has the correct extrusion width (image 4)
6- You can perform the same test with another printer, for example an Artillery Sidewinder X1 (images 5, 6, 7 and 8)
Shape-Box-2.3mf.zip
Shape-Box.3mf.zip
Checklist of files included above
Version of PrusaSlicer
2.6.0-alpha6+MacOS-x64 / 2.5.1+MacOS-x64 / 2.5.1+win64 / -2.6.0-alpha6+win64
Operating system
macOS 10.15.7 / Windows 10
Printer model
Any (Prusa, Artillery, Ender, etc.)
The text was updated successfully, but these errors were encountered: