This is QIDIStudio v2.02.01.60. This version fixes some operational logic and optimizes certain printing parameters.

Bug Fixed

1. Fixed a bug where the printer could not parse gcode when the object name contained special characters.

Miscellaneous

1. Optimize the material change logic for the Q2 machine.
2. Optimize the default selected consumables, defaulting to QIDI PLA.
3. Optimize the display and default selection of machine models on the guide page, with all machines selected by default.
4. Add an Enable_multi_box toggle on the print sending page, allowing control over whether the printer uses box consumables or external consumables. After synchronizing box consumable information, the Enable_multi_box toggle will automatically turn on. If box consumable information has not been synchronized, Enable_multi_box will be disabled by default and cannot be edited, and print tasks will use external consumables for printing.
5. When importing non-QIDI 3mf files, retain parameter modifications in process.
6. Update translations.
7. Optimize the print height for the Q2, adjusting it from 260 to 256.

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.02.00.61_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.

2. 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.

3. 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.