home.social

#orcaslicer — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #orcaslicer, aggregated by home.social.

  1. Meh, #PrusaSlicer *also* doesn't know the difference between an outer or an inner bridge (inner = the first layer of a top wall).

    I might just move over to #OrcaSlicer. PrusaSlicer seemed way better than Cura, but Orca apparently is the most advanced right now.
    #3DPrinting

  2. Habe jetzt das Seitenteil nochmal mit dem #PrusaSlicer (Teil rechts im Bild) gedruckt. Links sieht man einen der drei Fehldrucke mit #OrcaSlicer. Die Temperaturen für das Filament und Heatbed habe ich quasi übernommen. Evtl kontrolliere ich auch nochmal Retraction und Druckgeschwindigkeit, aber das sind schon Welten. Wahrscheinlich bleibe ich aber beim PrusaSlicer. Der hat out of the box damals funktioniert und überzeugt einfach. #Creality #CR6SE #3DDrucker #3dprinting

  3. 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 called OrcaSlicer_V1.6.4-beta2_Linux.zip so I figured I give it a try. I was a bit concerned when I opened that zip and found it contained a file called OrcaSlicer_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
  4. 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.

    @3dprinting #3dprinting