A G-code path goes beyound plate boundaries?

It seems impossible to have objects that sits on both horizontal and vertical areas of the exclusion area (X1cc). The objects can be sliced individually without problem (by toggling printable) but if both are very close to the exclusion area, the error shows up. Any idea why?
To reproduce this issue, you can simply put two cubes on to an empty plate, position them closely around the exclusion area without coliding each other. Size of the cubes do not matter, and you don’t even have to put them really close to each other.
I can’t understand any reason for that, apart from the “travel” may goes inside the exclusion area. If this is correct, can’t the slicer avoid travelling over the exclusion area? It shouldn’t be difficult, just let it goes around should fix it, right? Are there any other reasons for this particular issue?

1 Like

Found the same problem. The true unprintable area seems to be a right angled triangle at the corner with the hypotenuse cutting through the 18x28mm point. And it is at least double of the size of the claimed 18x28mm rectangle from Bambu wiki. The G-code path beyond boundary prohibition seems to be solely determined by the positions of the objects instead of the actual path of traval. It is triggered even when object print order is arranged so as to avoid crossing the exclusion area. This is a huge waste of print area and I don’t understand why this issue is not addressed.

There is a way to override that. I am looking for the reference.

Thank you for the link. Yes I am aware of that. I meant leaving 18mm x 28mm reserved for the cutting tool is perfectly ok for me. And I don’t want to disable the filament cutter. The problem is, as in my attached screenshots, even when my 2 cubes are far away from the restricted area, and the G-code path is not entering the area except for the cutting, the slicer is still assuming my object/path goes beyond boundary incorrectly. That should be fixed at program level.


I can’t seem to replicate?

Can you attach your .3mf?

Sure. Not the exact locations but they should be close enough.
example1.3mf (19.0 KB)
example2.3mf (21.1 KB)