Cura
Cura copied to clipboard
[4.7 beta] Tree supports start in the air
Application version 4.7 beta
Platform Windows 10 x64
Printer Cr10S
Reproduction steps
- Tree support
Screenshot(s)

Actual results tree supports start in the air in some spots. On the right side, it also stops much before it should, at the point the support is useless. It's probably because of the x-y distance being too low, but then the support shouldn't be there.
Expected results Supports should not start in the air and not be created if they don't support something plausible
Project file Tell me the e-mail I can send it to privately, thank you.
I'd love to see that project file indeed. You can send it to r dot dulek at ultimaker if you like.
It looks like the branch of tree support is initially generated with sufficient distance from the mesh, but then shifts to a location where it thinks it can't escape to the build plate any more, and then tries to go towards the inside of the model instead.
Sent it, the project shows both the issues, I don't know if they are related.
Thank you! With this project file the issue reproduces. We'll discuss this with the team.
We've decided to put this fairly high up in the backlog. Hopefully we can fix it for 4.8.
This was fixed in version 4.8, through this PR: https://github.com/Ultimaker/CuraEngine/pull/1319
This was fixed in version 4.8, through this PR: Ultimaker/CuraEngine#1319
Hi, in 4.8 beta it still sometimes happen. Sending a mail to you.
The same happens in the hole inside. not only it starts in the air, but it doesn't reach the model at all.

Another example.
I'll send again via mail because it's 2.5x the size allowed on github
Plus, I tried with an x-y distance of 0.1mm and the branches, from example on the glasses, are very far and not really supporting. I reported it in #8622
Devs see CURA-7800 for our internal reference.
I'm using Cura 4.12.1 and this is still happening(Caused print to fail):

This happens in cura 4.11.0 as well
The same issue - Cura 5.0.0
Same issue in Cura 5.1

Hi @war4peace, we prioritized the ticket related to the issue high on our backlog, could you please share a project file so I can add it to our ticket, the more models we can reproduce the issue with the better. Thank you!
Hi @war4peace, we prioritized the ticket related to the issue high on our backlog, could you please share a project file so I can add it to our ticket, the more models we can reproduce the issue with the better. Thank you!
Hello,
I can't share the model publicly because it is licensed, but I can send it through e-mail if you want to. FYI, the same issue occurs for various versions of Cura which I tried: 4.13, 4.13.1, 5.0 beta, 5.0 release, 5.1 beta, 5.1 release
Currently I have Cura 5.1 and 4.13.1 installed, I could export project files from both if you need them, just let me know which e-mail address I should forward them to.
I can't share the model publicly because it is licensed, but I can send it through e-mail if you want to.
Thanks for the reports.
I'm currently working on this ticket, and need a model where it can reproduce clearly. (Since the model I'm working on now turned out to have the number of support walls set to 0 for that printer.) You should be able to reach me at /remco/burema/ultimaker/com (remove the first slash, and replace the others with the expected characters).
I can't share the model publicly because it is licensed, but I can send it through e-mail if you want to.
Thanks for the reports.
I'm currently working on this ticket, and need a model where it can reproduce clearly. (Since the model I'm working on now turned out to have the number of support walls set to 0 for that printer.) You should be able to reach me at
/remco/burema/ultimaker/com(remove the first slash, and replace the others with the expected characters).
E-mail sent.
FYI: This issue should be solved in the new Cura 5.4 release
Tested in 5.4, while the tree supports are quite improved...i found some issues with the tree-support interface where they appear mid-air
Interesting. Can you please create a new issue for this? It is quite separate from the old issue where sometimes branches just got cut mid-air; @ThomasRahm should have solved all those cases with his new TS algorithm that got merged in 5.4