The accessibility of Bambu Slicer for screen-readers for the blind isn’t great. I’ve sent through some suggestions but, whilst I wait, fingers crossed, for these implementations, I’d love to be able to use my slicer of preference, Prusa Slicer, from which Bambu Slicer is forked. I think I read on their FAQ that there are profiles for other slicers, but can’t find them anywhere, aside from one on Printables.com… Which I don’t really trust.
My ideal would be to slice in Prusa slicer, import the GCode into the Bambu Studio and print. A bit of a long route around, but might be the best solution for now. Other option is, for things such as supports, is to generate in Prusa slicer and export as an STL into Bambu, and simply print.
Trying to work out the easiest and most flexible work flow here.
So the one on Printables is one I created, after asking for the profiles for other slicers and being told they would not be provided.
Not trusting it is a totally understandable position though - it’s good idea generally to not run random people’s G-code unless you know exactly what it does.
I should really spend some time with it, including figuring out if the AMS can be used with it, but I don’t have an AMS, and the need I had for PrusaSlicer, is no longer current so I’ve just been using Bambu Studio lately.
I had plans to tidy it all up and submit it for integration into PrusaSlicer as a supported printer, but that’s quite a bit of work.
It would be great to get a profile for Cura sorted, and I made a start with that, but it’s not a slicer I’m very familiar with so the time that would be required to do it is sadly more time than I really have to spend on it.
With SD printing coming to the handy app, at least an agent said it was in the pipeline, this means the Prusa route becomes better, especially if I can set it up with a network attached micro SD… if such a thing exists.
how are other profiles created? Does it require the manufacturer’s input or is it something Prusa do their end? Seems like a lot of work if so. Also, will it work the other way around? For example, could Prusament submit profiles for their filament for Bambu Slicer? I’m guessing the calibration negates the need for this somewhat, but for things like the P1P, which I believe is going to rely on cloud based calibrations from other printers, it could be useful.