this post was submitted on 24 Jan 2025
60 points (98.4% liked)

3DPrinting

16130 readers
57 users here now

3DPrinting is a place where makers of all skill levels and walks of life can learn about and discuss 3D printing and development of 3D printed parts and devices.

The r/functionalprint community is now located at: or [email protected]

There are CAD communities available at: [email protected] or [email protected]

Rules

If you need an easy way to host pictures, https://catbox.moe may be an option. Be ethical about what you post and donate if you are able or use this a lot. It is just an individual hosting content, not a company. The image embedding syntax for Lemmy is ![](URL)

Moderation policy: Light, mostly invisible

founded 2 years ago
MODERATORS
 

TL;DW: A fairly automatic postprocessing script to convert your print's walls to brick layers to attempt to achieve more tensile strength in the Z axis, i.e. against layer separation. Some brief description of the current patent clusterfuck, and an observation that the new patent in question (which is probably void anyway) has not been filed in Europe...

Link to the author's github for this: https://github.com/TengerTechnologies/Bricklayers

It seems from the github issues report that this is not 100% perfect, but it appears to be at least mostly functional for those of us who would like to mess with this and not have to do it manually.

Note, I am not the author of this.

you are viewing a single comment's thread
view the rest of the comments
[–] TootSweet 7 points 6 days ago (2 children)

I'm definitely excited for this technology to start getting into slicers. In the meantime, I might have occasion to want so much strength in a part that I'd go to the trouble of using a script.

I currently use Cura, but I'm disgusted with Cura and looking to switch to PrusaSlicer. Cura's a great slicer, but a terrible program. I use Raspberry Pis as desktop systems frequently. Cura used to work on ARM, but doesn't any more. I'm also switching my main x86_64 box to Gentoo. It seems like they've added just tons of ridiculous libraries as dependencies to Cura that make it so hard to build Cura, the Gentoo devs have given up trying. Cura also doesn't play nice with Wayland. And it will only run on an old version of Python, which makes getting it to run on a modern system challenging. In short, the slicing isn't the problem. It's getting it installed and running on your system of choice.

So, given that I'm probably switching to PrusaSlicer soon anyway, I'll be in just the right place to start using scripts for PrusaSlicer/Orca/etc like this one. Hopefully this feature makes it into PrusaSlicer upstream soon as well.

(I do say I'm probably switching to PrusaSlicer. I don't really have a good grasp on what features I've depended on in Cura are absent in Prusaslicer. Like, does it have tree supports? Support blocking? Top surface ironing? Not that all of those things are deal breakers, but some might end up being a big deal to me. And if so, I might have to go to the trouble of wrangling building Cura or holding off on switching to Gentoo or running Cura in Docker or something. We'll see.)

Final thought:

"Fuck Patents. All my homies hate patents."

[–] brightandshinyobject 4 points 5 days ago (1 children)

If you're thinking about switching to prusaslicer just make the jump to Orca Slicer. It's a fork of Prusa and Bambu sliver and has awesome community support. Make sure you only get it from the GitHub, there are a bunch of sketchy websites trying to serve you less reputable versions.

[–] [email protected] 1 points 3 days ago (1 children)

I've been using Prusaslicer for a while and am quite happy with it. Why would I move to Orcaslicer?

[–] DokPsy 1 points 1 day ago

Built in tuning for filaments and printers was what sold me

[–] dual_sport_dork 4 points 6 days ago

Prusa has tree (organic) supports, support blocking, and ironing. It does not have the combing option or anything that is quite exactly equivalent which is the only thing from Cura I really miss.