Beta 4 expands photo, colour, 3D and Game Maker tools
Mac photo, grading, scene and game workflows expanded, with recovery-aware in-place updating and explicit limits for other editions.
- Recorded milestone
- Version / context
- 1.4 Beta 4

A wider Mac creative toolkit
NetVista Studio 1.4 Beta 4 was published on 19 September 2026. Its largest additions were in the native Mac application: layered photo editing expanded with blank documents, painting and erasing, brush controls, supported ABR brush import, selections, masks and adjustments. Editable photo projects remained distinct from finished image exports.
Colour grading gained wheels, curves, qualifiers, scopes, grade nodes and custom cube LUT export. The 3D scene workflow also developed, with improved object manipulation, rigging and animation controls. These tools broadened what a Mac project could contain without making the beta a finished replacement for specialist production applications.
Game authoring and safer updating
Game Maker supported empty 2D or 3D projects, imported assets, visual logic and a native play preview. It could export Three.js or Python source projects. Character and sprite-sheet animations still had a narrower boundary: they could preview natively but were not supported in those source exports.
The Mac update system gained in-place installation, project recovery and rollback support for compatible future releases. These protections were designed to preserve work through replacement and restart, but they did not remove the need for backups. End-to-end updating on a separate test Mac had not been verified for this release.
Different editions, different capabilities
Windows and Linux received updated Qt packages with account sign-in and periodic account verification, while retaining their timeline, export and package-update workflows. They did not receive the Mac Photo Editor, Game Maker or advanced 3D workspace. In-place updating was Mac-only. The Apple-silicon Mac package was ad-hoc signed and not Apple-notarized; Windows/Linux users needed to extract the complete application folder. Those boundaries are part of the release, not footnotes to a claim of full platform parity.