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

[Request] Setting gap between the model and support in XY #53

Closed
lonelymyp opened this issue Dec 3, 2016 · 5 comments
Closed

[Request] Setting gap between the model and support in XY #53

lonelymyp opened this issue Dec 3, 2016 · 5 comments

Comments

@lonelymyp
Copy link

Add the possibility to set the gap between the model and support in XY
Current algorithm is worthless, the gap is chosen based on the width of the support.

@lordofhyphens
Copy link
Contributor

There's a pull request over at the main branch @bubnikv might be able to adapt to his purposes (increasing the gap).

@bubnikv
Copy link
Collaborator

bubnikv commented Dec 22, 2016

It will be part of the new supports I am working on.

@bubnikv
Copy link
Collaborator

bubnikv commented Jan 20, 2017

There is now a "support_material_xy_spacing" parameter in the current master. The UI part was taken over from the pull request by @lordofhyphens , thanks.

@bubnikv bubnikv closed this as completed Jan 20, 2017
@lordofhyphens
Copy link
Contributor

lordofhyphens commented Jan 20, 2017 via email

@bubnikv
Copy link
Collaborator

bubnikv commented Jan 20, 2017

Which were the commits that implemented this? I'd like to prepare a PR
against upstream.

Sorry, it has been many commits. It is only in the new C++ supports. If interested, you may just compile the latest master and play with them, but if you want to bring it to the @alexr Slic3r, it is better to wait until the feature fully stabilizes in the Prusa3D fork and then add the new files and fix the dependencies.

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

No branches or pull requests

3 participants