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

Keep only bridges does not respects bridge_infil_margin setting #1155

Closed
qwewer0 opened this issue May 15, 2021 · 1 comment
Closed

Keep only bridges does not respects bridge_infil_margin setting #1155

qwewer0 opened this issue May 15, 2021 · 1 comment
Labels
enhancement fix is live in the last release Please download /build the last release and try to reproduce.

Comments

@qwewer0
Copy link

qwewer0 commented May 15, 2021

Describe the bug
When Keep only bridges is selected for no_perimeter_unsupported_algo the bridge_infil_margin setting with a value higher than default doesn't have any effect. (lower value does work)

To Reproduce
Steps to reproduce the behavior:

  1. Generate a Bridge flow calibration
  2. Slice the object
  3. See the result (bridge area)
  4. Select Keep only bridges for no_perimeter_unsupported_algo
  5. Change bridge_infil_margin to a value higher than default
  6. Slice the object
  7. See error (bridge area)

3D Model and Slic3r Configuration Export
Bridge calibration.zip

Expected behavior
bridge_infil_margin should work with Keep only bridges

Screenshots
bandicam 2021-05-15 13-57-43-161

Desktop (please complete the following information):

  • OS: Windows 10
  • Version 2.3.56.0
@supermerill supermerill added the fixed for the next version That means that you should be able to test it in the latest nightly build label Oct 7, 2021
supermerill added a commit that referenced this issue Oct 7, 2021
@supermerill
now "no perimeter on bridges" -> "only bridges" follow bridged_infill…
5abd2fc 
…_margin

#1155
@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 Oct 8, 2021
@qwewer0
Copy link
Author

qwewer0 commented Nov 7, 2021

Fixed.

@qwewer0 qwewer0 closed this as completed Nov 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement 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 @qwewer0