/* Feature request */ Meshmixer like tree support for FDM printing

[martinowren]

Is this a new feature request?
Yes

You have showed you can do it with the new Alpha SLA support. So make something like it for FDM ;)

[OopAck]

I would like that too...
Also would like to see "Optimize Orientation" on the i3 side too not just SL1

[cnlson]

+1 to both although tree support is more important.

[zheffie]

+1

[PatrikTheDev]

+1 for both

[PatrikTheDev]

And maybe make them like cura so they are more stable, they can be “like trees”

[kjgipp]

I would also like to see an added feature for Tree Supports.

[kmshort]

+1 Tree supports for FDM would be fantastic.
Code is already there for SLA, so how hard can it be?

Also, "painting" an area on an object that needs support, with supports being auto-generated to target that specific area. That would be really useful.

[bubnikv]

Tree supports for FDM would be fantastic. Code is already there for SLA, so how hard can it be?

The SLA tree supports will certainly not work for FDM without major changes.

Also, "painting" an area on an object that needs support, with supports

being auto-generated to target that specific area. That would be really useful. We were thinking about that as well.

…

On Wed, May 15, 2019 at 2:48 AM kmshort ***@***.***> wrote: Tree supports for FDM would be fantastic. Code is already there for SLA, so how hard can it be? Also, "painting" an area on an object that needs support, with supports being auto-generated to target that specific area. That would be really useful. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1514?email_source=notifications&email_token=ABMPSIZ6JJRRWNHC6V3Y7NTPVNMU7A5CNFSM4GMEFGVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVNGCWY#issuecomment-492462427>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABMPSI2TEK5TCORWWDE4DWDPVNMU7ANCNFSM4GMEFGVA> .

[vertigo235]

I really hope the PrusaSlicer team can get back to working on FDM features soon. Would really love to see some improvements with FDM supports and this is not limited to tree supports.

[3dprintingnewb]

I also would love to see tree supports on an upcoming release. I also use Cura and tree supports work quite well. I have contacted Prusa support requesting them and I sent Josef a message via reddit hope Prusa responds

[WarrenSchultz]

This is possible to hack with extra steps in the latest release if you use an SL1 profile to generate the supports on the base plate, then export as STL with Supports. You can then import that into an FDM project. There is extra support material on the bed, but it works. (And, because Prusa cleverly saved the STL into a part-based format, you can separate by parts and remove the extra bed layers as one big piece)

All that to say, Prusa has all the code it needs in place on the current alpha, just a bit of tweaking is required. :)

[dennyrgood]

I played with this a bit ... when I add tree supports to a model with the SL1 profile, save it with tree supports and bring it back in with it set to the FDM printer ... I can see the trees, but when I go to slice it the tops of the trees do not appear to touch/or come very close to the object.

I have not tried printing it yet, but has anyone else seen what I am referencing?

Mr Warren Schultz (and even others) has this been an issue for you?

Thanks!!!

[tonypartridge]

+1 please!

[gbomacfly]

+1

[kris2340k]

+1

[rveda]

+1

[stuartpb]

The SLA tree supports will certainly not work for FDM without major changes.

What major changes would those be?

[janrg]

+1

[ephramcohen]

+1

[Kiron21]

+10

[Ugars]

+1
Tree support is my only reason for using Cura.

[Kiron21]

And ironing.

[lars-sorensen]

Oh yes please!!

[Nandox7]

+1 Tree supports for FDM would be fantastic.
Code is already there for SLA, so how hard can it be?

Also, "painting" an area on an object that needs support, with supports being auto-generated to target that specific area. That would be really useful.

Maybe create a second FR for that.
That one of feature I miss form cura, where it highlights the overhang areas and we can go around "clicking" on the ones we want support (or the reverse, where you don't want)
On more complex parts it make the work of adding soo much easier and fast compared to creating one support enforcer for every single detail.

[valterfc]

+1

[thorkseng]

+1

[alienboyxp]

+1

[lukasmatena]

@devbyrd It is already being worked on. If you actually read the thread, you'd already know that.

[devbyrd]

@lukasmatena Understood. Thanks for the snarky response.
I have read the comments and the last "we're working on that" comment was from October of '21 (last year). 90% of the comments are "Cura is better! No, PrusaSlicer is better, but you have to spend an hour tweaking SLA supports, then reimport as an FDM model, to make it work".
The FR hasn't been assigned and it's not on any roadmap that I can find. So, the question was a legitimate one.
Another legitimate question: Is there any expected release this PR will be merged into, or some timeline for release?

[jDavidnet]

yeah, last I understood, was that Prusa was trying to outperform the cura style supports, and roll their own sort of thing to compete with them.

…

On Wed, Feb 23, 2022 at 8:42 AM devbyrd ***@***.***> wrote: @lukasmatena <https://github.com/lukasmatena> Understood. Thanks for the snarky response. I have read the comments and the last "we're working on that" comment was from October of '21 (last year). 90% of the comments are "Cura is better! No, PrusaSlicer is better, but you have to spend an hour tweaking SLA supports, then reimport as an FDM model, to make it work". The FR hasn't been assigned and it's not on any roadmap that I can find. So, the question was a legitimate one. Another legitimate question: Is there any expected release this PR will be merged into, or some timeline for release? — Reply to this email directly, view it on GitHub <#1514 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAB5CFUIKB4ZK5WBX37IN63U4UFABANCNFSM4GMEFGVA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- -- -- Justin Kruger Social Media Software Engineer - San Francisco, CA

-- http://jDavid.net http://twitter.com/jdavid http://www.linkedin.com/in/jdavid

-- ***@***.***

[larsrc]

I hope you don't let the perfect be the enemy of the good. As long as it's marked as experimental, you could make it available to get early feedback, and to show that there's progress.

[slartibartfass]

+1 for Tree Support

[davjam79]

+1 for tree support.

[blackdrum]

+1 tree support please

[nprocko]

Another vote for tree supports

[stepikovo]

We are already working on it, no need to vote for it anymore :)

[k1-801]

Is there a branch for the WIP feature we could check out? If the work has been going on for 5 months straight, what are the current issues? Is there any help needed with the code?

[fgoodwin]

Any idea when we might get an ballpark roadmap timeline on this one? Would be a wonderful feature to have in Prusa.

[psiberfunk]

Bambu Labs slicer seems to have done this AFTER forking off of the 2.4.0 branch … so clearly they’ve beat the Prussa team to it here. You can see their github here: https://github.com/bambulab/BambuStudio/releases

This is now a major slicer (Cura) and a new upstart that are lapping Prusa for an important feature.

[minkshaman]

Bambu Labs slicer seems to have done this AFTER forking off of the 2.4.0 branch … so clearly they’ve beat the Prussa team to it here. You can see their github here: https://github.com/bambulab/BambuStudio/releases

This is now a major slicer (Cura) and a new upstart that are lapping Prusa for an important feature.

Huh. Well, I know which slicer I’m trying out now.

[TerTerro]

So if there any ETA for this feature? Other slicers have it, Cura, Bamboo now that is forked from PS. Why not this one?
At least give us a Beta or enable same SLA tree supports in FDM, yes, not perfect, but dont need to fidle back and forth between export, import.

[MrExo3D]

+1 eta?

[WaveyWaver]

Been waiting for this for years already and surprised this isn't implemented yet
Would wish to switch to this slicer due to it being based on slic3r but i just refuse to leave tree supports behind

Would be cool to know where the development is at

[rcmaniac25]

https://youtu.be/G0LaFmconIc?t=3987

"PrusaSlicer Tree Supports? That's a bit of an evergreen, yes, the devs have been researching it for quite a while..." "...and and I think there is something special. Uh, I'm not sure if it will be in this version of slicer <2.5> but probably right after that"

[psiberfunk]

Wow , I thought that last comment was gonna be a meme reference … but no.. they’re really just not listening .

[fgoodwin]

Wow , I thought that last comment was gonna be a meme reference … but no.. they’re really just not listening .

At least it does give a ballpark timeline, relatively far out though it might be

[psiberfunk]

Yea , it’s just disappointing that there can’t be more transparency here .

[stepikovo]

As I mentioned recently, we are actively working on this. The polishing will still take a few weeks. Thank you for your patience.

[lukasmatena]

Organic supports are implemented in 2.6.0-alpha2. Closing.