#orcaslicer — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #orcaslicer, aggregated by home.social.
-
Any chooms got some 3D printing advice?
I have a bedslinger (Sovol SV06 ACE, PLA), and any lower profile prints have been perfect, but I wanted to try this cool paper-holding rat to print for my son, and I have tried 3 times and it comes loose from the bed near the top of the print. Of course then it just air prints.
Things I have tried:
- Cleaning the bed with 96% ethanol (I do that before each print anyway)
- Using hairspray on the bed
- Increasing the first layer thickness
- Adjusting the z-offset for more squish
- Adding a skirt of 8mm
- Checking all the temp settings: bed 60C, first layer 210C print temp 200C (as specified on the PLA spool)
I'm using orcaslicer, I think the one thing that's left to try is reducing the print speed, but I hoped that wouldn't be needed...Maybe there is a way to slow the print as you get further up? Or maybe because I'm such a n00b I missed something obvbious
#3dprint #3dprinting #orcaslicer #slicer #bedslinger #AdvicePlease #AdviceNeeded #hardware
-
Did a bit'a readin and thought #OrcaSlicer looked like it had a few nice improvements to #SuperSlicer. Their GitHub releases page had a file calledOrcaSlicer_V1.6.4-beta2_Linux.zipso I figured I give it a try. I was a bit concerned when I opened that zip and found it contained a file calledOrcaSlicer_ubu64.AppImage, but hey, it's an AppImage right, should be fine...nope. First run from cli just to see what it spits out and what'a'ye know,error while loading shared libraries: libwebkit2gtk-4.0.so.37. A quick sifting through the AppImage contents and guess how many .so files it had in it; yup, not'a one.
What's the point of making an #AppImage / #Flatpak / #Snap if you're not gonna include the required libraries to run it?
♲ @[email protected]:Orca Slicer Is The New Game In Town
#3dprinterhacks #3dprinting #orcaslicer #slicer #hackaday
posted by pod_feeder_v2 -
I just tried #OrcaSlicer for the first time, I've just not had time to test it until now.
Because it was based on #PrusaSlicer, #SuperSlicer, and #Slic3r, I hoped that I could just import my PrusaSlicer config, but could not because it expected a .json file and PrusaSlicer outputs a .ini, but I might have done this incorrectly.
So I configure a "Generic Klipper setup" and copied the values by hand by comparing settings with my PrusaSlicer setup and a bit of experience and intuition.
My first resulting print, a custim part by me compared to the PrusaSlicer, was worlds apart. The finish was greatly improved with bridges requiring no supports, however it did print a bit slower, 28 minutes instead of 18 minutes, but this might still just be speed settings.
I like the UI, although I am more used to PrusaSlicer, and I especially love that I can access #Mainsail and #Klipper from within the app.