-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Orca is leaving a wide gap in the seam #6378
Comments
Do you have the same issue in other slicers? |
I've tested on creality print and cura... It really only happens when printing more than one STL in the same plate. |
The below can cause what you're seeing:
In general this issue happens either due to incorrect setting of the seam gap (too large) or because your nozzle is leaking material during travel or due to wrong PA. To combat the leaky nozzle (especially with a 0.6 nozzle) you need higher retraction values and faster travel speeds. The other two are just calibrations /settings that just need to be set correctly. |
Just Tested. Still... out of 6 machines (Usually printing with same gcode configs), 2 beds had 1 stl each with open gaps... Still trying to investigate further causes. |
If it was me I’d combine the fastest travel speed you can do together with a bit higher retraction. From what you’ve said it appears to be due to nozzle ooze. Maybe also try slightly lower filament print temperature (like 5-10c) to reduce how “runny” it is. too low a Pa can cause a delay in material flow when you’re starting to extrude, resulting in gaps. If the gap is at the start of the seam it may be too low PA. If it’s at the end it may be too high. But without seeing your PA test I can’t tell. Check out the below test and see how the start is under extruded with low PA and the end is under extruded with high Pa. finally you can try decreasing the de-retraction speed to 30mm/sec to allow for time for the nozzle to pressurise. |
This is definitely related to multiple objects and rounded corners. I printed the same box, with the same settings, multiple times, always get this when I have more copies at the same time, and funny thing: I tried 3 copied, 1 was perfect and the other 2 have these same games. Watching it closely it looks like it only starts extruding after it does the curve on that corner. And it looks like the issue only happens in the back left corner, I'll try to move the seam to see if changes something. |
I'm seeing some very similar issues on my X1C with there being a seam gap despite adjusting the likely culprit parameters: set seam gap to 0 and 0%, dried filament thoroughly, switched between arachne and classic, tuned PA manually and used the auto calibration. None of that seems to work. The only difference for me is that I didn't need to attempt to print multiple parts to see the issue. The STL I was printing, however, did have a lot of thin walls and it seemed like a few layers were not as problematic as others. I also tested printing a single wall cylinder and the seam was okay, but there were certainly slightly larger gaps at various heights. The other interesting part is I have so far not been able to recreate it on any of my other printers (all bedslingers); I only see it on the X1C. I've only tried to recreate the single wall cylinder at this point though (will attempt to test the problematic STL when I get a chance). |
Can confirm. I set seam gap to 0, 2.5, 5, 7.5 and default 10 (all percents) and the gap is still the same. All exactly the same witdth. A mm or two wide. I already have PA calibrated etc. |
This was not an issue previously in orca 1.8 or so. Now it is and IDK why after updating. |
Here is a simple test case I use which recreates the seam issue I'm seeing with the X1C. I'm wondering if others can run this test and also recreate it (should be relatively quick and use minimal filament):
Print the file and not if you are still seeing the same seam gap. If you are able to slice with a version of Orca Slicer that then successfully removes the seam gap with the same settings and filament profile, try adding up the extrusion distance for a single layer and compare the totals. I've got to go to work now so can't really do more testing right now but based on what I'm seeing on my machine, it does seem like there is something underlying changing my total extrusion distance per layer in 2.2.0. |
I've played around with various settings and I still haven't identified the issue or found what I would consider a good solution (I've messed with a lot of different factors one at a time and to various extremes). At this point in time, I think my best path moving forward is to use the Extra Length on Restart for deretraction moves. I do get slightly better results lowering my retraction to an absurdly low amount (0.05mm as one example) but that does cause a little bit more stringing on retraction test models. Plus I'm using a Bambu X1C whose base 0.8mm retraction distance is somewhat dialed in. Just as a note, I think the reason a few people above said they only see it with multiple items could be related to the retract on layer change setting. For my one wall cylinder test print, if I disable that setting the cylinder prints fine as long as there is just one since that removes the retraction that would normally occur at the seam. However, with multiple objects on the plate, that retraction would still occur before a travel move. |
Is there an existing issue for this problem?
OrcaSlicer Version
2.1.1
Operating System (OS)
Windows
OS Version
Windows 10
Additional system information
Device name HikiSRV
Processor AMD Ryzen 9 7900 12-Core Processor 3.70 GHz
Installed RAM 64.0 GB (63.1 GB usable)
Graphics: RTX A4500 20gb
Printer
Elegoo Neptune 4 Max / Neptune 4 Pro / Creality K1Max
How to reproduce
Just add 2 STL's with thin walls (I've tested with 3, 4, 6 walls)
Seam gap of 0.1, 0.05, 0.01, 0.
Retraction works fine for any other print and even for the same STL if it's alone on the plate.
Actual results
Expected results
Normal closed seams
Project file & Debug log uploads
Plates2.zip
Checklist of files to include
Anything else?
No response
The text was updated successfully, but these errors were encountered: