Skip to content
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

Artifacts due to multiple causes #4061

Closed
Murrdo opened this issue Jan 8, 2024 · 2 comments
Closed

Artifacts due to multiple causes #4061

Murrdo opened this issue Jan 8, 2024 · 2 comments
Labels
bug Something isn't working as intended fix is live in the last release Please download /build the last release and try to reproduce.

Comments

@Murrdo
Copy link

Murrdo commented Jan 8, 2024

I apologize, I know that this defect has already been described in issue #3785. But it is marked as closed, I left comments in it, but no response.
It also seems to me that I have found more reasons for the appearance of artifacts.

Version: 2.5.59.6
Build: SuperSlicer_2.5.59.6_2024-01-05
Operating System: Windows
System Architecture: 64 bit
Windows Version: Windows 10 (build 19045), 64-bit edition

I found several reasons that provoke the appearance of perimeters hanging in the air:
1.Often the “wall thickness” parameter spontaneously takes on a value with 4 decimal places
image
image
If you change the value manually, removing the decimal places, there are no artifacts.
Also, some extrusion width values ​​lead to the same effect, but I did not understand the pattern
One artefact.zip

2.When the generation of arches (G2/G3) and "threshelod for overhangs" with arachne is turned on at the same time, a huge number of artifacts appear.
image
Many Artefacts.zip

Also, if you place this model in the center of the table in the default position, the slicer crashes with an error on layer 74.
If you rotate the model along the X axis, there is no error.
image
Error.zip

@supermerill supermerill added bug Something isn't working as intended working on labels Jan 8, 2024
supermerill added a commit that referenced this issue Jan 29, 2024
supermerill added a commit that referenced this issue Jan 29, 2024
@supermerill supermerill added fixed for the next version That means that you should be able to test it in the latest nightly build and removed working on labels Jan 30, 2024
supermerill added a commit that referenced this issue Jan 31, 2024
@TheBoojah
Copy link
Sponsor

TheBoojah commented Jan 31, 2024

I also found that setting "Model rounding precision" to 0 (default 0.0001) removes a lot or all of the hanging perimeters.
Tested on Nightly windows x64 #677: Commit [79eb38e]

@supermerill
Copy link
Owner

The issue was that the gcode reader wasn't refreshing its position from G2 move, and so the fan mover infer the wrong position, hence the lines going anywhere.
But if there isn't a G2 just before a G1 (both are G2 or both are G1, or it's G1->G2) where the fan is moved, then there is no artifact.
The gcode reader is fixed in the current nightly & next releases.

@supermerill supermerill added fix is live in the last release Please download /build the last release and try to reproduce. and removed fixed for the next version That means that you should be able to test it in the latest nightly build labels Feb 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as intended fix is live in the last release Please download /build the last release and try to reproduce.
Projects
None yet
Development

No branches or pull requests

3 participants