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
This may be related to issue #8841 from 2022 (still open) although that issue is more about seams on curves. This is about a seam that should be on a sharp rear corner. If the cause is the same, please close this as a dupllicate.
When I have a model with a sharp corner, I rotate it on the build plate so the corner is the rear-most feature, and I set the seam position to "rear".
This usually works, but sometimes it doesn't. In this example, the seam is set to "rear" but it appears in three places along the edge, not at the corner that is obviously the rear-most feature on the build plate.
It doesn't matter if it's Classic or Arachne, it doesn't matter if I set staggered inner seams or external perimeters first, it does the same thing every time.
Description of the bug
This may be related to issue #8841 from 2022 (still open) although that issue is more about seams on curves. This is about a seam that should be on a sharp rear corner. If the cause is the same, please close this as a dupllicate.
When I have a model with a sharp corner, I rotate it on the build plate so the corner is the rear-most feature, and I set the seam position to "rear".
This usually works, but sometimes it doesn't. In this example, the seam is set to "rear" but it appears in three places along the edge, not at the corner that is obviously the rear-most feature on the build plate.
It doesn't matter if it's Classic or Arachne, it doesn't matter if I set staggered inner seams or external perimeters first, it does the same thing every time.
Project file & How to reproduce
boxcoverplate_seamtest.zip
The attached project file is for a Prusa MK3S with MMU2S.
Checklist of files included above
Version of PrusaSlicer
2.8.1
Operating system
Windows 11 - build 22631.4317
Printer model
Prusa MK3S/MMU2S
The text was updated successfully, but these errors were encountered: