OrcaSlicer's 22 September 2026 nightly package was an automated snapshot of the main development branch, not a frozen release. The exact file is identified by time and commit; the nightly label can later point to different content. This article is therefore updated as a safe testing and rollback guide rather than a feature list.

What nightly means

The official project description says packages can be built automatically after commits reach main for Windows, macOS and Linux. This gives developers fast feedback, but changes have not necessarily completed stable-release testing. Features can appear, change or be reverted, so newest is not the same as safest.

Back up the complete configuration

Do not export only a custom filament preset. Preserve printer, process and material profiles, important 3MF projects, the configuration directory, the current stable installer and one known-good G-code file. Removing the application may not remove or restore user data, and an older version may interpret a new field differently.

Run nightly with a separate configuration directory or isolated user environment where possible. Pause cloud and preset sync until you have established that it will not overwrite the production state.

Identify the actual build

Record commit, package name, operating system and download time. The official GitHub release page gives stronger provenance than a repackaged forum file. Verify a checksum or signature when the project publishes one.

A three-stage comparison

First open a simple single-material reference in stable and nightly. Second test the specific repair or profile that justifies nightly. Third use a project that previously exposed a regression. Compare resolved settings, layers, material estimate, time and critical G-code commands.

File size or a successful preview does not prove equivalent output. Inspect temperature, bed boundaries, start and end scripts, material changes, fans, volumetric flow and machine-specific commands.

The first physical trial

Make the first print small, inexpensive and supervised. It should not use the full envelope or an expensive multi-material job. Observe homing, heating, first layer, tool or material change and end motion. Never send unfamiliar nightly-generated G-code to a production machine unattended.

A reproducible issue report

Include commit, operating system, machine and firmware, exact steps, expected and actual result, and a sanitised project and log where necessary. State whether stable shows the same behaviour. Remove access tokens, internal network addresses and customer geometry.

Rollback is more than reinstalling

After reinstalling stable, restore the saved configuration in isolation and regenerate the reference object. Compare layers, estimates and critical commands with the known-good G-code. Only then treat the production environment as restored.

Verified fact and conclusion

It is verified that OrcaSlicer's official page recommends stable for most users and describes nightly as an automatically compiled work in progress. LAYERTIMES concludes that nightly is justified for a targeted fix or development test, not routine freshness. Isolation, commit-level traceability, G-code comparison and a rehearsed rollback route are the correct controls.