QOL Bambu Studio-Show Selected Printer, Plate, and Temps

There are two quality of life/informational updates that seem like they’d be very simple to implement in Bambu Studio and would save users (especially me) time while using the app.

  1. Show the name of the selected printer on the Prepare and Preview tabs. The selected printer is the one chosen in the dropdown list on the Device tab. I don’t care about being able to change it on the Prepare and Preview tabs, if that causes a lot of additional coding. But, at least show the name of the one you are slicing for. This matters when certain printers in your inventory have different nozzle sizes and/or build plates. Typically the nozzle size of 0.4 and 0.6 give different dropdown options in the Process dropdown. But, if users create custom profiles, they could have the same name and cause confusion as to which printer you are creating the gcode for. The flow of working in Bambu Studio is wonky when you first need to go to the 3rd tab (i.e. Device tab) and then go back to the Prepare tab.

  2. Show the temperatures that have been assigned to the filament you’ve picked. Also show the temperature for the Plate type. Again, this can be read only, but this information should be available without additional clicks in the Prepare and Preview tabs.

  3. Show the name of the build plate, filament, and process profile (0.20mmm Strength @BBL X1C, etc.) on the “Send print job to” popup window and/or on the Device tab, under Printing progress, where it shows the title and stats about the print. This would help confirm that the AMS is pulling filament with the temps you put in the slicer.

All of this information is just helpful to confirm things while working with multiple printers. Working with just 1 printer isn’t an issue. Working with many that have different configurations that could print very poorly based on how it was sliced would make things a whole lot better. I know there are some built-in checks regarding build plate types and nozzle size, but more preventative information and not relying on those validation pieces would add to peace of mind.

Thank you for your consideration on this.

The printer you are slicing for IS the one listed in the Prepare or Preview tab. It does not matter which machine is selected in the Device tab. You don’t need to have ANY machine connected to prepare or slice. The generated g-code will be for the printer profile selected in the Prepare tab.

Where on the Prepare tab does it show the PRINTER you are slicing for? It only shows the nozzle, plate, and filament. The gear icon opens the wizard to add more printer profiles.

I suppose I missed a step. I’d like the settings I’ve assigned to Printer_A (0.4mm nozzle, PEI Textured plated, AMS with 4 filaments) to autopopulate those in the Prepare/Preview tabs. When I select Printer_B (0.6mm nozzle, Smooth High Temp Plate, AMS with 4 different filaments from Printer_A) I want these settings to autopopulate in the Prepare/Preview tabs.

I understand what you are saying that you’re slicing for the settings on this page. I’m saying, I want to save these presets and have them tied to the printer you select in the Device tab. That’s how PrusaSlicer kind of does it. You select a MK3S with MMU2 and it gives you all the filaments, adds the prime/purge block, etc. You select the MK3S single 0.4 or 0.6mm nozzles and it prepopulates those settings for you.

So this is why I say I want the Device tied to the settings when you have multiple printers. Because the workflow is that Printer_B just finished it’s print. Let me select Printer_B from the devices and then add the models I’m going to print for it’s settings. I don’t want my workflow to be that Printer_B finished, let me look up that Printer_B has a smooth high temp plate with a 0.6mm nozzle and then rescan the AMS. Or, what I’ve been doing is keeping 2 windows open for my 2 printers and then checking the device tab to make sure I’ve got the right window open, since it’s very difficult to tell at a glance if you aren’t on the Device tab.

I hope that makes sense and better explains why I made the suggestion.