This is QIDIStudio v2.02.00.60. This version is synchronized with BambuStudio2.2.0 Public Beta.
Based on this, some features have been optimized, and several known bugs have been fixed.
¶ New Features
-
Added Fuzzy Skin Painting Tool
Allows users to customize fuzzy skin painting on the model surface, excluding the top and bottom of the model.
-
Added Window Adjustment Feature
If the sidebar is not fully displayed, use Ctrl+W. The window will automatically adjust.
To manually resize the sidebar, modify Open Configuration File -> QIDIStudio.conf -> enable_sidebar_resizable and set it to True. Restart QIDIStudio and use the Ctrl+W shortcut. After these steps, the sidebar can be manually adjusted.
¶ Bug Fixes
- Fixed the bug where multi-filament multi-color printing forced BOX synchronization.
When using multi-filament and multi-color printing, a synchronization pop-up will appear. If you do not wish to proceed with synchronization, simply click Cancel/Close. The print submission pop-up will then appear as usual. - Fixed the bug where clicking the material browsing window in the single-tray printing popup without synchronized box information would cause the software to crash.
- Fixed the bug where the generated wipe tower in multi-color printing exceeded the print bed limits.
¶ Miscellaneous
- Optimized print time calculations.
- Optimized filament color matching logic.
- Optimized filament change GCode.
- Added compatibility for some new filaments.
- Updated partial translations.
- Added tooltips for some parameters.
¶ 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.
- 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.
-
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. -
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.