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
Friend is working on a very thin-walled part more or less one nozzle's-width in wall thickness. While troubleshooting print quality issues that were arising, we found that the seam position, while consistent with the setting "Contiguous" that was set in the one section of the part in which there was more than one perimeter, was not so, on the thin-walled area. Furthermore, this isn't visible in the slicer with "seams" checked under Show: .
Project file & How to reproduce
Slice a part made with a large section of just thin wall perimeter, using Contiguous seam position. Under View: hit "Seams" and observe that none of the little white things denoting the seam position appear on the section with thin walls. Print the part and observe that the thin wall section does not obey the seam position setting.
What happened?
Friend is working on a very thin-walled part more or less one nozzle's-width in wall thickness. While troubleshooting print quality issues that were arising, we found that the seam position, while consistent with the setting "Contiguous" that was set in the one section of the part in which there was more than one perimeter, was not so, on the thin-walled area. Furthermore, this isn't visible in the slicer with "seams" checked under Show: .
Project file & How to reproduce
Slice a part made with a large section of just thin wall perimeter, using Contiguous seam position. Under View: hit "Seams" and observe that none of the little white things denoting the seam position appear on the section with thin walls. Print the part and observe that the thin wall section does not obey the seam position setting.
BUGS.3mf.zip
Version
2.4.58.5 and 2.5.59.12 (geometry of part makes 2.5.60.0 crash)
Operating system
Windows 10 + Linux Mint 22.0
Printer model
Artillery Genius Pro
The text was updated successfully, but these errors were encountered: