It doesn’t appear in the color legend:
In this case, it sits between the orange outer wall and the light green support line.
As near as I can tell, it’s just empty space, but it has this curious shape to it tht starts very thin at the bottom and then gets thicker the higher it goes…until it gets truncated at the top.
It’s relevant to me because I can’t seem to get rid of this even if I were to set XY distance spacing on the support material to either near zero or zero, and consequently it leads to a problem with the second layer dispensing a support material there as a kind of bridge–which is made from a different filament (seen below in dark green):
or as light green if you look in the summary preview:
and I’d rather not have that happening, because it doesn’t always stick particularly well in this location and it’s an unnecessary filament switch. If it has to do it, I’d rather it just stick with PLA in this particular place. Unfortunately, I don’t see a way to modifier my way out of this, though maybe there is a way that I’m just not groking.
I guess it’s technically “support interface”. I tried to eliminate it by turning bottom support interface to zero layers,
but it persists anyway. And if I increase “bottom interface spacing”, it merely kicks the same problem to the next print level.
I suppose I could use a support blocker, and tried that a couple of times, but I have trouble orientating that across the entire model, because this problems repeats throughout the entire perimeter of the printer model.
“Height range modifier” would be the other approach I’ve tried, but it doesn’t seem to allow suppressing supports as part of it.
So, aside from being yet another reason I wish we could use orca slicer or prusa slicer, is there any solution, or will I just have to live with it until the BS slicer is someday improved?
Attached is the project file in case you want to play around with it or see for yourself.
2025Dec027__1345___posted.3mf (1.5 MB)
I suppose if I were to paste over the entire first layer periphery with mouse ears, I’d crush the problem that way, but that’s pretty radical. Or I could elminate automatic support generation and switch to painted-only supports, but that would be extra work and I’m not sure it would make any difference in this case.
Grok 4.1 thinks the answer is to reduce XY model distance to zero, but that comes with side effects. On the other hand, Chatgpt 5.2 complains that bambulab is preventing it from reading a link to this post and gives it a 402 instead. So, I fed it screen scrapes, and it maybe (?) nailed it:
![]()
Trying that: nope, it made no difference.








