SlicerShelf
Navigazione principale
Archivio indipendente delle versioni

QIDI Studio

QIDI Studio 2.0.3.55

Scheda ufficiale di QIDI Studio 2.0.3.55, pubblicata il 26 mag 2025.

Stabile4 pacchetti pubblici6543 download GitHub registrati

File ufficiali di questa release

Linux · 1 file

  • QIDIStudio_2.00.03.55_Ubuntu24.AppImageNon specificato nel nome del file · 92,3 MiB · 170 download
    Download ufficiale ↗

Windows · 2 file

macOS · 1 file

Modifiche ai pacchetti dalla release precedente

Rispetto a 2.0.3.54, tutti i conteggi classificati restano invariati con 4 file pubblici.

I conteggi sono viste separate dei nomi file dell’editore per piattaforma, processore e formato. Non garantiscono compatibilità o supporto.

Anteprima delle note

Estratto in testo semplice dalle note dell’editore. Apri la release ufficiale per il testo completo e aggiornato.

Le note dell’editore restano nella lingua originale. Questo estratto non è tradotto automaticamente.

QIDIStudio.logo

This is QIDIStudio version 2.00.03.55. The main updates in this version include: bug fixes, translation updates, and filament information updates.

Bug Fixes

  1. Fixed an issue where user configurations (materials or processes) could not be saved correctly when saving 3MF files.
  2. Fixed an issue with incorrect automatic naming when exporting to Gcode.

Miscellaneous

  1. Updated partial translations.
  2. Added new support filaments: QIDI Support For PAHT and QIDI Support For PET-PA (only supported by X-Plus 4).
  3. Added new TPU filament: QIDI TPU-Aero.

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: — ~~~cmd — WEBKITDISABLECOMPOSITINGMODE=0 WEBKITDISABLEDMABUFRENDERER=0 ./QIDIStudio2.00.03.55Ubuntu24.AppImage — ~~~
  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.
  1. 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.

2 00 03 54_git1

Release ufficiale ↗