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

Floating Supports #12326

Open
2 tasks
hugo-so opened this issue May 23, 2022 · 2 comments
Open
2 tasks

Floating Supports #12326

hugo-so opened this issue May 23, 2022 · 2 comments
Labels
Status: On Backlog The issue / feature has been reproduced and is deemed important enough to be fixed. Type: Bug The code does not produce the intended behavior.

Comments

@hugo-so
Copy link

hugo-so commented May 23, 2022

Application Version

5.0.0

Platform

Windows 11

Printer

Creality Ender 3 Pro

Reproduction steps

  1. Imported STL
  2. Tweaked settings to use tree supports
  3. Sliced model

Actual results

Supports are generated with brim, but one area of supports is generated floating off the build surface. This causes print failures, since there is nothing for these supports to adhere to.

Expected results

Supports should all be generated touching the build platform or other parts of the part.

Checklist of files to include

  • Log file
  • Project file

Additional information & file uploads

Fan Case V2.zip
image
image
@hugo-so hugo-so added the Type: Bug The code does not produce the intended behavior. label May 23, 2022
@DerGenaue
Copy link

Unfortunately there kinda is no way around this problem since it appears wherever the tree branches into more than two branches.
Usually you can just ignore them and they well stick somewhere to the walls of the Tree Support but not affect the stability of the supports too much.

Even the Tree Support V2 Mod is not immune to this (it just happens more rarely)

@Vandresc
Copy link
Contributor

Vandresc commented Jun 7, 2022

Hi @hugo-so , thank you for your report. We do have a ticket in our backlog related to this issue. Devs see CURA-9170 for our internal reference.

@Vandresc Vandresc added the Status: On Backlog The issue / feature has been reproduced and is deemed important enough to be fixed. label Jun 7, 2022
@DerGenaue DerGenaue mentioned this issue Jul 23, 2022
Closed
2 tasks
@DerGenaue DerGenaue mentioned this issue Sep 25, 2022
Open
2 tasks
@DerGenaue DerGenaue mentioned this issue Dec 25, 2022
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Status: On Backlog The issue / feature has been reproduced and is deemed important enough to be fixed. Type: Bug The code does not produce the intended behavior.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@DerGenaue @hugo-so @Vandresc