[BUG] Ugly seams

[Mikyner]

The seams look terrible and are very visible. On one of today's copies there is a gap instead of a seam (marked with an arrow on the photo)

[sirgrej]

I can confirm this issue on mk4 with fw 5.1.2 and prusaslicer 2.7.1.
first I thought it is an input shaper issue but I looks the same without input shaping

[MichaelJLew]

Seams are likely more to do with the slicer than with the firmware, so maybe have a look at the PrusaSlicer issues on GitHub.

I will draw your attention to two requests for the same feature: seams that can be nearly invisible. prusa3d/PrusaSlicer#11621
prusa3d/PrusaSlicer#11948

You might like to give the post-processor script that is linked in the second of those posts a go. In any case you might comment on those pages to give them a bump.

[FutureSharks]

This is a duplicate of #3286

Maybe just close this and comment there?

[Mikyner]

I confirm that this is a bug in Prusa Slicer and not in the printer FW

[uncovery]

Same here. It's a disaster. MK3 never had this issue.

[Mikyner]

Same here. It's a disaster. MK3 never had this issue.

It's a slicer problem, I'm using Orc

[Mikyner]

It's a slicer problem, I'm using Orca now and everything is fine.

[FutureSharks]

I think just close this and refer to prusa3d/PrusaSlicer#11914 ?

[bryn51]

Exposed and obvious seam lines have been with Prusa printers for a long time.
Now, both Mk4 and XL printers have finer steps it ought to be possible to at least reduce the seam gaps somewhat by way of the higher accuracy of movement.
I have never seen a rational reason given as to why we must tolerate them.
If prusa saw fit to spend huge resources fixing resonance aberrations with the IS thing, the seam lines ought be worth at least as great an effort since the impact is in fact much greater.
The open seam lines not only look bad, they weaken the print too.

[MichaelJLew]

Try the latest development build of OrcaSlicer. It has scarf joint seams that fix many seam issues.

…

On Fri, Mar 1, 2024, at 7:16 PM, Bryn Parrott wrote: Exposed and obvious seam lines have been with Prusa printers for a long time. Now, both Mk4 and XL printers have finer steps it ought to be possible to at least reduce the seam gaps somewhat by way of the higher accuracy of movement. I have never seen a rational reason given as to why we must tolerate them. If prusa saw fit to spend huge resources fixing resonance aberrations with the IS thing, the seam lines ought be worth at least as great an effort since the impact is in fact much greater. The open seam lines not only look bad, they weaken the print too. — Reply to this email directly, view it on GitHub <#3651 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBXJAZKGCHTBODQOXLP35S3YWA2MHAVCNFSM6AAAAABBIQAF4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZSG4YTQMZQG4>. You are receiving this because you commented.Message ID: ***@***.***>

[bryn51]

Thanks for the suggestion. Buuut… I’m of an age not to be constantly trying new products, preferring the safe road. If Orca can fix this issue why not Prusa ? Sent from Outlook for iOS<https://aka.ms/o0ukef>

________________________________ From: MichaelJLew ***@***.***> Sent: Friday, March 1, 2024 21:18 To: prusa3d/Prusa-Firmware-Buddy ***@***.***> Cc: Bryn Parrott ***@***.***>; Comment ***@***.***> Subject: Re: [prusa3d/Prusa-Firmware-Buddy] [BUG] Ugly seams (Issue #3651) Try the latest development build of OrcaSlicer. It has scarf joint seams that fix many seam issues.

On Fri, Mar 1, 2024, at 7:16 PM, Bryn Parrott wrote: Exposed and obvious seam lines have been with Prusa printers for a long time. Now, both Mk4 and XL printers have finer steps it ought to be possible to at least reduce the seam gaps somewhat by way of the higher accuracy of movement. I have never seen a rational reason given as to why we must tolerate them. If prusa saw fit to spend huge resources fixing resonance aberrations with the IS thing, the seam lines ought be worth at least as great an effort since the impact is in fact much greater. The open seam lines not only look bad, they weaken the print too. — Reply to this email directly, view it on GitHub <#3651 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBXJAZKGCHTBODQOXLP35S3YWA2MHAVCNFSM6AAAAABBIQAF4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZSG4YTQMZQG4>. You are receiving this because you commented.Message ID: ***@***.***>

— Reply to this email directly, view it on GitHub<#3651 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAZV5KKRTVNITY27DH4O6U3YWA2XFAVCNFSM6AAAAABBIQAF4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZSG4ZDENJUGI>. You are receiving this because you commented.Message ID: ***@***.***>

[MichaelJLew]

The fix is in Orca, not yet PrusaSlicer. Use it or don’t. It’s not that you are too old.

…

On Fri, Mar 1, 2024, at 7:52 PM, Bryn Parrott wrote: Thanks for the suggestion. Buuut… I’m of an age not to be constantly trying new products, preferring the safe road. If Orca can fix this issue why not Prusa ? Sent from Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: MichaelJLew ***@***.***> Sent: Friday, March 1, 2024 21:18 To: prusa3d/Prusa-Firmware-Buddy ***@***.***> Cc: Bryn Parrott ***@***.***>; Comment ***@***.***> Subject: Re: [prusa3d/Prusa-Firmware-Buddy] [BUG] Ugly seams (Issue #3651) Try the latest development build of OrcaSlicer. It has scarf joint seams that fix many seam issues. On Fri, Mar 1, 2024, at 7:16 PM, Bryn Parrott wrote: > > > > Exposed and obvious seam lines have been with Prusa printers for a long time. > Now, both Mk4 and XL printers have finer steps it ought to be possible to at least reduce the seam gaps somewhat by way of the higher accuracy of movement. > I have never seen a rational reason given as to why we must tolerate them. > If prusa saw fit to spend huge resources fixing resonance aberrations with the IS thing, the seam lines ought be worth at least as great an effort since the impact is in fact much greater. > The open seam lines not only look bad, they weaken the print too. > > > — > Reply to this email directly, view it on GitHub <#3651 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBXJAZKGCHTBODQOXLP35S3YWA2MHAVCNFSM6AAAAABBIQAF4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZSG4YTQMZQG4>. > You are receiving this because you commented.Message ID: ***@***.***> > — Reply to this email directly, view it on GitHub<#3651 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAZV5KKRTVNITY27DH4O6U3YWA2XFAVCNFSM6AAAAABBIQAF4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZSG4ZDENJUGI>. You are receiving this because you commented.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub <#3651 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBXJAZPXKVOGQZ5VDUSVAETYWA6UDAVCNFSM6AAAAABBIQAF4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZSG43TCMBTGI>. You are receiving this because you commented.Message ID: ***@***.***>

[mixer3d]

#2997

[GithubUser99999999]

Still not fixed

[github-actions]

This issue has been flagged as stale because it has been open for 60 days with no activity. The issue will be closed in 7 days unless someone removes the "stale" label or adds a comment.

[MichaelJLew]

Maybe stale, but still not fixed.

[bryn51]

Its true. I do not see why Prusa do not have this as a priority, as the code they need is already developed by others and just needs to be ported over (ok maybe more complex than "just", but still the broad algorithm has been developed already).

Maybe stale, but still not fixed.

[danopernis]

Perhaps that's because this issue is open in the wrong repository. This is not a firmware bug. Also, it is a duplicate of #3286

You can read more about this issue at prusa3d/PrusaSlicer#11914 (comment)

[bryn51]

Perhaps that's because this issue is open in the wrong repository. This is not a firmware bug. Also, it is a duplicate of #3286

There is a likely disagreement in definitions of what is a bug and what is an enhancement.

In my understanding one must refer to the product specification (if one exists). The user guide and any release notes function as a specification in the absence of a comprehensive document.
But Prusa development these days release software with minimal release notes or user guide updates. That is no excuse.
In the absence of any of the above then customer expectations of product behaviour are prima facie the specification.Customers are always right and their needs are first priority, or at least they ought to be.

If the product functions according to its specification and you want to alter it, then it's an enhancement.
If the product does not behave according to specification then its a bug.
But unfortunately it does not end there.
If a new version is released and the product is unstable or gives up an error then its a bug in development.
And so it goes on.
Rules differ according to who you speak to and their role/perspective.
It is totally unreasonable for professional developers to refuse to look at an issue based in an incorrect user classification, and certainly reprehensible to dismiss user reports based solely in misclassification by a user. And yet thats what we see prusa staff doing on this forum.
Whats more reasonable is for a management staffer to look at each report and simply assign it to an appropriate team no matter its original classification (and if necessary reclassify if if that makes sense).

How can I say this so confidently ? 25 years in IT development, as a developer, contractor, manager.