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

Seam in vase mode #2047

Open
spartanJon089 opened this issue Dec 13, 2021 · 6 comments
Open

Seam in vase mode #2047

spartanJon089 opened this issue Dec 13, 2021 · 6 comments

Comments

@spartanJon089
Copy link

What happened?

Vase mode creating weird artifacts or "seams". appears as gaps or misaligned layers in the gcode previews.

image
image
image

Project file & How to reproduce

VaseMode.zip

Version

Version 2.3.57.6

Operating system

windows 10

Printer model

modified ender 5 +

@supermerill supermerill added the bug Something isn't working as intended label Dec 13, 2021
@supermerill supermerill added enhancement hard problem and removed bug Something isn't working as intended labels Jan 31, 2022
@supermerill
Copy link
Owner

currently, the vase mode is crude:
it continue to slice layer by layer
then it will change the z based on the distance % on a layer. So when it's at the top (end of the layer, it is at the same height as the next one, but not at the right x & y if there is a slope.
I tried to move the seam away from slopes, but there is no start position that won't push you into a slope here. So it's an unavoidable artifact of the current slicing algorithm.

@robustini
Copy link

@supermerill please check that project with the nightly, i can't slice it, empty result.

@supermerill
Copy link
Owner

@robustini
if you put G1 Z0.01 after the START_PRINT in the custom start gcode AND you uncheck the use_relative_e_distances, then the gcode viewer works again.

I don't why yet, I'll look into it.

@robustini
Copy link

G1 Z0.01

Thanks for the tip, that string after the start gcode was enough for me, the other option that is flagged or not in my slicing does not make a difference.

@BlackNet
Copy link

BlackNet commented May 10, 2023

I have noted this bug as well. When I went digging for what / why I found something interesting. This is a known bug in PS for several years now. prusa3d#2841 This is from 2019, there is a 'fix' listed but it's not a good fix at all and it does mess up the model. Here is the same bug in Orcaslicer SoftFever/OrcaSlicer#431

@Dougwar
Copy link

Dougwar commented Apr 4, 2024

any news about it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants