Closed CuredPrusa closed 3 weeks ago
I fixed it, simplifying the overhangs detection. Not sure on exactly what prusa did here.
Thanks heaps! Now let's see about that nasty M106 :)
II have tried the same project on Version: 2.5.60.0 Build: SuperSlicer_2.5.60.0_2024-05-21 Operating System: Windows System Architecture: 64 bit Windows Version: Windows 10 (build 19045), 64-bit edition
and unfortunately it isn't any better .
on 59.10 release (an my edv branch, so should be on nightly also):
isn't what's you wanted?
The seam point is fine though, but travels are still messed up.
On such thin wall entering and exiting are visible, and it's not insignificant. In 2.4 (and Prusa any version) this model is sliced with uniform travels:
not so in 2.5:
fixed for next version, that was gapfill that discarded (wrongly) their reversibility.
Bug description I can not tame travel paths with seam orientation. There are many options to adjust the seam but none is delivering a uniform travel pattern as it was before. Maybe it works on simple models, but on a bit more complex, the seam travels are exiting and entering without much sense. Paint seam doesn't help. The seams looks like it's in the back (white dots), but shuffling the start and end point of the layer line messes up the appearance of the wall surface. I don't see a logical reason why creating a layer line should be as random as it is.
Expected behavior Seam in the BACK should be seam in the back, without some wobble and catching up "better positions". That's how Prusa has it still (2.7). Now I have to use SS 2.4.58 and drop additional settings from 2.5, because seam generator and travel algorithm just doesn't work as expected. I'm using now 2.4.58.4 and it works just fine.
!!>> Project File <<!! Here is the project, you can see that same project gives different seam in 2.4.58.4 compared to 2.5.59.7. Especially the travel moves. test.zip
To Reproduce Steps to reproduce the behavior: Select seam in the BACK. You can also see that using cost of angle and travel in 2.5.59.7 doesn't make significant changes. Changing to archane gives expected results, but that is archane not a workaround.
Screenshots
Desktop (please complete the following information):