Automatic slicing for A1 mini printer fails with print by object

I have found that the new(ish) feature that adds support for the A1 mini when that was not the original target printer, but, the print envelope is small enough - fails when ‘print-by-object’ is set on the plate.

How to reproduce

  • Set the target printer to P1S (could be any non-A1 mini printer)
  • Set the plate option for print order to - 'print by object"
  • Auto-arrange the objects
  • Save the profile
  • Upload the profile to MW

The A1 mini is NOT found in the supported printers list.

Assuming this might be a layout issue, I tried this…

  • Set the target printer to A1 mini
  • Set the plate option for print order to - 'print by object"
  • Auto-arrange the objects
  • Set the target printers to P1S (could be any non-A1 mini printer)
  • Save the profile
  • Upload the profile to MW

The A1 mini is STILL NOT found in the supported printers list.

It doesn’t appear that any arrangement, number, or height of objects fixes the problem.

I even tested the issue with a single object, but it failed.

From my testing, it appears as simple as…

If you set the print order to by-object and target any printer other than the A1 mini, your profile will not be compatible with the A1 mini no matter what other choices you set.

The only resolution is to target the A1 mini to start with and have the print durations all appear significantly longer than they would have had the profile target the P or X series.

Uploading two print profiles (one targeting All printers and one targeting just the A1) as a workaround sets up future issues that should be avoided.

@Tanklet

For by-object printing sequence, because A1 mini has bigger clearance than P1S, so we blocked this compatiblity to avoid slicing error when printing from Bambu Handy (although it rarely happen and will not cause real printing failure).


The cloud service will not do auto-arrangement for a place. The auto-arrangement feature may generate splite one print plate into two and its arrangement algorithm may change on different versions of cloud slicer.

It would have been helpful to tell people when it was announced that this huge omission was in place.

It makes sense why, but, people (me included) became used to the improvement and it was pure luck I spotted the profile missing out a printer they should have included had this significant exception been known about.

Forewarned is forearmed…

I went a few days entirely unaware that I had excluded a whole section of people because I trusted what I had been told and experienced right up until finding what appeared to be a massive bug.

I now know (only because I reported it) it is a known, yet, unpublicised exception.

Actually, the page haven’t made any claims about the exact printer types that a print profile will be compatible with.

The UI indicates “auto-check” of compatibility, the cloud slicer will do a general compatibility check before giving the compatible printer list.

It was in the announcement.