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

Add support for "Non-Planar Top Layer Fuzzyskin" #7152

Open
1 task done
misterjmw opened this issue Oct 17, 2024 · 4 comments
Open
1 task done

Add support for "Non-Planar Top Layer Fuzzyskin" #7152

misterjmw opened this issue Oct 17, 2024 · 4 comments
Labels
enhancement New feature or request

Comments

@misterjmw
Copy link

Is there an existing issue for this feature request?

  • I have searched the existing issues

Is your feature request related to a problem?

It would be nice to have a toggle-able feature to support fuzzy skin on non-planar, top surfaces.

Which printers will be beneficial to this feature?

All

Describe the solution you'd like

A dev has created and tested this feature with several slicers and is open source. It would be nice to see an integration of the functionality from https://github.com/TengerTechnologies/Fuzzyficator as an Orcaslicer feature. Discussion on the project can be found here.. The feature should work with Marlin and Klipper.

Describe alternatives you've considered

The only alternative I'm aware of is GCode post-processing, which is a nuisance.

Additional context

No response

@misterjmw misterjmw added the enhancement New feature or request label Oct 17, 2024
@kdegeek
Copy link

kdegeek commented Oct 17, 2024

You beat me to this by 13 mins haha

@Rickthebig
Copy link

"The feature should work with Marlin and Klipper"
What about RRF? Something against implementing it also to work with RRF?
Or just completely agnostic of the gcode flavor used?

@misterjmw
Copy link
Author

misterjmw commented Oct 17, 2024

"The feature should work with Marlin and Klipper" What about RRF? Something against implementing it also to work with RRF? Or just completely agnostic of the gcode flavor used?

The form only asks about Marlin and Klipper. Anything outside of that, I have no/too little experience to provide an answer. Generally I feel that a casual omission should not be taken as a statement of explicit exclusion, e.g. "It will not work with ________".

@vgdh
Copy link
Contributor

vgdh commented Oct 18, 2024

Have you tested it? How is the quality? I would love to see some photos.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants