This is QIDIStudio v2.02.00.61. This version includes the configuration for the newly released Q2 machine.
Based on this, some features have been optimized, and several known bugs have been fixed.

Bug Fixes

1. Fixed compatibility with non-QIDIStudio 3mf file configurations. (#115)
2. Fixed the bug where filament information in the Box could not be synchronized when the printer was set with a user account. (#108)
3. Fixed the bug where the cooling mode—exhaust fan settings in the filament settings were ineffective.
4. Fixed the bug where GCode generation with decimal points as commas caused printing failures (in some countries, such as Germany and Italy). (#102)
5. Fixed the bug where importing non-QIDIStudio 3mf files repeatedly would result in blank material fields.
6. Fixed the bug where the post_process script path with double quotes would become invalid after saving and reopening. (#68)
7. Fixed the calibration model for Pressure Advance.
8. Fixed the bug where adding a physical printer would incorrectly validate identical IPs (e.g., 192.xx.xx.10 and 192.xx.xx.1 were mistakenly flagged as duplicates).

Miscellaneous

1. Fixed the issue of oversized icons on MacOS systems. (#114)
2. Added configuration for the Q2 machine.
3. Added filament configurations compatible with the Q2 machine.

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.