An inelegant "exclusion area" override work-around (Bambu Studio Bug)

Here’s a (rather very hacky) workaround for those affected by this.

DISCLAIMER:

The process…

  1. Browse to the machine settings folder:
    C:\Users\{..your username..}\AppData\Roaming\BambuStudio\system\BBL\machine

  2. Pick the profile you want to use and create a copy, name it something meaningful:
    image

  3. Open the file; update the name to match the file, override the inherited exclusion zone as shown below:
    image
    ** I updated the “setting_id” to the (seemingly) unique value “GM006”. Not sure if this is necessary…

  4. Add a section to the config manifest for the new config (use the section of the copied config as a template):
    C:\Users\{..your username..}\AppData\Roaming\BambuStudio\system\BBL.json
    image
    ** Ctrll^F is your friend on this one :wink:

  5. Re-load Bambu Studio and select the modified config:
    image

  6. Hopefully your exclusion zone is gone:

  7. Go do something nice for someone.

2 Likes

If you use the previously excluded area, won’t the lever for the filament cutter collide then?

3 Likes

Thanks Alex, Disclaimer updated :slight_smile:

1 Like

I tried it and it works for me, you just have to be very careful !

Little precision, in the BBL.json file, the part that you have to copy paste is at the very bottom of the text

1 Like

In the initial post, @flz included a link that has an STL you can print that will hold the lever out of the way while printing.

1 Like

I figured this out on my own but approached it slightly different.

I tried saving a preset so I was able to navigate to

C:\Users{WindowsUserName}\AppData\Roaming\BambuStudio\user{Profile ID}\machine

And was able to simply add the bed exclude as a new JSON object (who knew my AWS work would come in handy?) to my user config.

I think going with the user preset will prevent it from getting overwritten with an update . Not sure if this happens, but the directory is the system dir for bambu studio and I would not be surprised if they nuke things that are not “standard” during an update.

1 Like

Yes, he added the link because I had asked the question :wink:

2 Likes

Care to share more details about your modified steps and I’ll update the process? Your way is probably safer