Released milestoneRelease retrospective

Windows and Linux join NetVista Studio as 3D animation develops

Native Windows and Linux packages expanded desktop access, while the next beta developed Mac scene animation and checked, data-only Mods.

Recorded milestone
13–14 August 2026
Version / context
1.2–1.3 Beta 1
An editing desk with a camera, monitor and photographs
NetVista Studio artwork. An illustration of the studio, not a screenshot of the features described.

Three desktop editions

NetVista Studio 1.2 Beta 1 was published on 13 August 2026, adding Windows and Linux downloads alongside the Mac application. The new desktop editions used Qt and FFmpeg rather than a browser wrapper. Their editing workflow covered media import, multitrack arrangement, cutting, clip movement, timeline zoom, preview rendering and project saving.

Shared .netvistastudio desktop projects and expanded export choices were important parts of the release. Resolution presets reached 16K, with custom sizes and codec options where the available FFmpeg build supported them. A listed resolution was not a guarantee that every computer could render it: memory, encoder support, storage and time remained practical constraints.

Animation and a bounded Mods system

Published on 14 August, 1.3 Beta 1 expanded the Mac 3D workspace with object and camera keyframes, a dedicated scene timeline, procedural maps and physics settings. Imported models with an existing skeleton could expose bones for posing and rotation keyframes. This release did not create a skeleton or paint skin weights onto an unrigged model.

The same beta introduced Mods across the desktop editions. Packages could provide bounded themes, native declarative pages and checked catalog descriptions. They could not execute arbitrary creator scripts or native code. Newly installed packages stayed disabled until enabled, and catalog entries did not automatically insert assets into scenes.

Shared projects did not mean identical tools

Advanced animated SceneKit editing remained Mac-only. Windows and Linux could preserve scene data without providing that native rendering workspace. Extracting the complete desktop package was also essential: the executable depended on its accompanying runtime files. These releases widened access while leaving clear platform differences that continued through later betas.