Skip to main content

Lumina Studio 2.0 Development Report: March 2026

Historical backfill · Reporting period: March 9–31, 2026

← Changelog overview · Next: April 2026 →

Monthly overview​

After the 1.6.3 release, Lumina Studio moved into internal development for 2.0. The first work replaced several export, SVG, and preview paths that limited speed and maintainability, while beginning broader image-format, material-preset, and slicer support. March was a smaller month by volume, but established the foundation used by the hundreds of improvements that followed.

Highlights​

Much faster SVG preview and generation​

Several SVG path defects were fixed and the main preview stages were reworked. A representative workflow dropped from roughly 92 seconds to about 10 seconds. Complex SVG artwork reaches colour matching and 3D preview sooner without reducing final print accuracy.

Native 3MF export path​

The previous Python-built XML/ZIP export path was replaced with a native library. This reduces overhead on larger models and provides a stronger base for watermarks, slicer metadata, and multi-material project structures.

New features​

  • Added DNG image uploads, allowing more camera-source files to enter calibration and colour-extraction workflows directly.
  • Added XYD Xiaoming PLA LUT presets for 4-, 6-, and 8-colour workflows.

Slicers and 3MF​

  • Added Anycubic Slicer Next and Kobra profiles, with project metadata better suited to those slicers.
  • Added 3MF watermark support as a foundation for identifying finished files and their source.

Calibration and materials​

  • Aligned channel ordering across 6-colour calibration boards and recipes, reducing colour shifts between extraction, layer previews, and final models.

Stability, performance, and infrastructure​

The month also addressed pipeline debug previews, automatic temporary-file cleanup, frontend API addressing, launcher cleanup, and regression assertions. These changes did not add many visible controls, but made generated-file cleanup and development startup more reliable while preparing a stable baseline for April's larger migration.

Known limitations​

  • 2.0 was still in the early internal-migration stage; vector, material-profile, and modelling workflows had not yet been unified.
  • The new slicer profiles still required broader verification across real machines and nozzle combinations.

← Changelog overview · Next: April 2026 →

Comments