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.

Sign up for GitHub

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

Jump to bottom

Different precision with the same settings #2477

Closed
macchinette opened this issue Mar 3, 2022 · 1 comment
Closed

Different precision with the same settings #2477

macchinette opened this issue Mar 3, 2022 · 1 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.

Comments

@macchinette
Copy link

What happened?

I made a comparison between the latest night version 2.4 and the latest 2.3 and I noticed that the aesthetics of the wall between the versions with the same settings does not match and gets worse by activating the random stitching.
I would have expected the same look and path with the same resolution.

Thanks

image

Project file & How to reproduce

Load the project file for the version and slicer.
To see that the problem is present more lightly with the back seam, change it and re-slice.

Spessore TEST.zip

Version

SuperSlicer_2.4.58.1_2022-03-01

Operating system

Windows 10

Printer model

Anycubic I3 Mega S
@supermerill supermerill added bug Something isn't working as intended fixed for the next version That means that you should be able to test it in the latest nightly build labels Mar 7, 2022
@supermerill
Copy link
Owner

supermerill commented Mar 7, 2022 •
edited
Loading

Prusa added a "gcode resoution" (that I may not use, I'll see). Forgot to remove a "simplify" line from the merge. my bad.

supermerill added a commit that referenced this issue Mar 7, 2022
@supermerill
Correctly disable gcode_resolution from prusaslicer.
0b2f2a1 
using internal_resolution istead for brim
using max_g1_per_second and min_length for gcode
using nothing (resolution from slicing) for generate_perimeter
May use it for gcode reduction, to add a junction derivation filter before the max_g1_per_second.
#2477
@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 Apr 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Milestone
No milestone
Development

No branches or pull requests
2 participants
@supermerill @macchinette