Issues with slicing embedded single line text
Hello,
I'm having problems with printing single line text embedded into an object. There are a few issues with Prusa Slicer that I submitted on GitHub nearly a year ago, but they were abandoned.
1. Both Arachne and Classic have their own ideas about extrusion width. Even though my font has a constant stroke width and I have a single fixed extrusion width set in slicer, the generators modify the extrusion width, messing up the letters.
2. Arachne is creating too short extrusions, so if you have letters 'H' and 'D', 'H' has a smaller height. Classic works correct in this regard, but it makes some parts of letters disappear completely.
3. And finally one of the most annoying things to watch, which also creates more stringing and random quality drop, is that the order of printing of embedded objects has no "traveling salesman" optimization, so the extruder is just running back and forth across the plate instead of going one letter after another. I checked that this issue is not present in SuperSlicer, but I guess Prusa is behind.
Links to GitHub for more details:
https://github.com/prusa3d/PrusaSlicer/issues/12136
https://github.com/prusa3d/PrusaSlicer/issues/12135
https://github.com/prusa3d/PrusaSlicer/issues/11959
Since I lost hope for any help on GitHub, maybe you guys have some idea how to work around these problems? Maybe some of the slicer settings can be adjusted to make these issues go away? Thank you in advance for any help.
RE: Issues with slicing embedded single line text
I wish I knew of a solution but this — insert here the opposite of "optimization" — of the travel path seems more rampant now than in prior versions. It is indeed particularly irritating when the first layer contains text. I haven't found anything in PS that would allow one to adjust the path calculation.
Formerly known on this forum as @fuchsr -- until all hell broke loose with the forum software...
RE: Issues with slicing embedded single line text
49 minutes spent on travel in a print. I don't know why Prusa is ignoring this for such a long time, while this is clearly an issue that can be fixed. It is working in SuperSlicer.
PrusaSlicer:
SuperSlicer:
Unfortunately, I'm working on Prusa XL 5T, so I'm stuck with PrusaSlicer for now.