This is QIDIStudio v2.01.01.52. This version is synchronized with BambuStudio 2.1.1. Based on this, some features have been optimized, and several known bugs have been fixed.

Bug Fixes

1. Fixed the bug where modifying the printer's heatbed type would not save properly (#98);
2. Fixed the bug where the filament bar would collapse when adding or removing materials after synchronizing the box filaments;
3. Fixed the bug where external filaments could not be used for printing after synchronizing the box filaments;
4. Fixed the bug where slicing would fail when using hybrid tree supports;
5. Fixed the bug where printing a multi-color model with filament changes would forcibly require synchronizing the box filaments when using "Print Plate" to send a print task (#93);

Miscellaneous

1. Optimized the filament change G-code;
2. Optimized the print completion G-code;
3. Updated some translations;
4. Corrected some Russian translations (thanks to @lishniy);
5. Added prompt messages for some abnormal situations on the print sending page;
6. Updated some filament information;
7. Updated the configuration information for printers;

Note for Linux Users

On newer versions of Ubuntu (e.g., Ubuntu 24), the software may crash when connecting to a printer on the device page. You can try the following three methods to temporarily work around this issue.

1. Configure WEBVIEW before launching the software (Only for Ubuntu 24).
   Use the following command to attempt opening the software:

   WEBKIT_DISABLE_COMPOSITING_MODE=0 WEBKIT_DISABLE_DMABUF_RENDERER=0 ./QIDIStudio_2.00.03.56_Ubuntu24.AppImage  

Note: Using the above command to launch the software ensures that the Fluidd page can be opened and print tasks can be sent normally, but it may result in blank home, guide, and login pages.

1. If the first method doesn't work, you can manually add port "7125" when adding a device.
   The downside of this approach is that Fluidd cannot be opened from the device page, but it ensures the software does not crash after sending or starting a print job.

2. If all the above methods fail, you will need to manually export the G-code file, then open the corresponding device's Fluidd in a browser.
   In the task list, select "Upload File" and then execute the print operation. See the example below.