Comment by WJW

Comment by WJW 3 days ago

12 replies

Am I weird in not being too surprised? It don't have experience with wire EDM but every toolpath generator or slicer I've ever used was just local software.

pests 3 days ago

Bambu Labs ~recently had some drama around requiring an account / harvesting data for their machines. Might be what that's about.

  • gmueckl 2 days ago

    IIRC this was about the machine firmware. Their slicer software is a fork of PrusaSlicer, which is OSS.

  • jacquesm 3 days ago

    Bambu is great hardware but the software (and the firmware) is just terrible.

    • steve_adams_86 3 days ago

      Truly. The slicer is able to generate bugs I've never seen before, in around 6 years of printing with several slicers and firmwares. Cura, Flashprint, Orca, Prusa, using Marlin, Sailfish, Klipper. None of them produced the weird stuff I find with Bambu's pipeline.

      When the bugs don't creep up it's absolutely incredible, though.

      • jacquesm 2 days ago

        The slicer even introduces bugs in things that were working perfectly in the software they ripped off.

        For the A1 and P1S you're better off backporting the profile to PrusaSlicer or Orca.

        And don't get me started on the network plug-in (the lack of transparency there makes me fairly suspicious that something is up) and the lack of directory structure support on the SD cards. Really, how could you mess it up.

godelski 2 days ago

No, running locally is pretty standard.

Also what's weird is that this project seems to be primarily written in javascript. I can't imagine that's a pleasant user experience for generating tool paths...

  • s0a 2 days ago

    it's a combination of JS, WASM, and WebGPU. the JIT engines are so much faster than you would imagine, especially if you tune your code right. workers allow for parallel processing on all of your CPU cores. WebGPU, at least in Chrome, is kind of amazing.