OrcaSlicer 2.4.0-alpha: Is it worth the risk?
OrcaSlicer 2.4.0-alpha brings interesting novelties, but with a series of open bugs that can compromise the user experience, especially on Linux and macOS. Before updating, it is essential to know the known issues to assess whether this unstable version is suitable for your workflow.
Critical bugs on Linux and macOS
*The alpha version presents severe instability on Linux and macOS systems, with frequent crashes and interface rendering problems.*
Linux users using Wayland must prepare for frequent crashes. Bug #13836 reports critical instability on flatpak and native builds: crashes at startup, during device loading, and when sending prints. The problem is confirmed on CachyOS with Wayland.
Even without crashes, the experience on Wayland is compromised. The Device tab is extremely slow even on powerful hardware like the NVIDIA RTX 3080. Mouse scrolling is too slow and requires fallback to X11 to be usable. The application icon appears generic instead of the Orca logo.
- Frequent crashes at startup and during use (flatpak and native builds)
- Device tab with severe lag even on performant hardware
- Mouse scrolling unusable without X11 fallback
- Popup “Slice” and “Print” positioned out of place on Hyprland/NixOS
On macOS, the hover menu on Slice (X2D/H2D) disappears too quickly. The only workaround is to move the mouse more rapidly. Additionally, dialogs do not resize correctly on first launch: they must be closed and reopened.
Functional regressions compared to 2.3.2
*Some established functions such as multi-material supports and cloud sync show malfunctions compared to the previous stable version.*
Bug #13983 documents a critical regression on multi-material supports. The interface layers no longer adhere to the support as in version 2.3.2. This compromises the quality of complex prints that require optimized supports.
Cloud sync forces the “Retract Before Wipe” setting to ON at 100%. Disabling it locally has no effect: the change is not saved to the cloud. The issue is confirmed on macOS Tahoe.
| Function | Version 2.3.2 | Version 2.4.0-alpha |
|---|---|---|
| Multi-material supports | Interface adheres correctly | Interface layers do not adhere |
| Cloud sync preferences | Local settings respected | Retract Before Wipe forced ON |
| PA Profile (Bambu) | Bug present (#13204) | Not yet resolved |
Other open issues include the PA Profile not available in the Device tab for Bambu printers (bug #13204, already present in 2.3.2 and not resolved). The cloud is invisible in Stealth Mode without any warning, leading users to believe it is a malfunction.
Promising but unstable new features
*Despite the bugs, the 2.4.0-alpha introduces interesting features that could justify the update in the future.*
Orca Cloud represents the main novelty: profile synchronization across multiple installations, version history, and bundle sharing. For those working with multiple computers or managing machine fleets, this feature eliminates the manual transfer of configurations.
Z Anti-Aliasing improves inclined curved surfaces. Fuzzy Skin Ripple offers more controllable textures compared to the traditional random mode. The Optimized Gyroid infill promises more resistant structures, developed in collaboration with Brown University and NASA Space Grant.
Machine Input Shaping allows managing X/Y axis frequency and damping directly from the slicer, with support for Adaptive Klipper, RRF, and Marlin 2. Native Wayland support should improve the Linux experience, but current bugs compromise its effectiveness.
Support for Bambu Lab X2D is present but incomplete: the track switch is not recognized correctly and the camera is choppy compared to Bambu Studio. Separate nozzle speed adjustment in Process Settings is also missing.
When it is convenient to switch to the alpha
*Updating is recommended only for advanced users who want to contribute to testing; for daily use, it is safer to wait for the beta.*
Those using the printer for production, clients, or deliveries should avoid this version. Linux crashes, support regressions, and cloud sync issues can block work. It is better to keep the stable 2.3.2 as the main version.
The 2.4.0-alpha is suitable only for those who want to test new functions and contribute to the project by reporting bugs. In this case, it is advisable to install the alpha in parallel with the stable version and use copies of the profiles, not the working ones.
Procedure for safe testing
- Full backup: Export all printer, filament, and process profiles from the stable version.
- Parallel installation: Install 2.4.0-alpha without uninstalling 2.3.2, using separate directories.
- Test on copied profiles: Import copies of the profiles into the alpha; never use the original production ones.
- Bug report: Document issues with screenshots, .3mf files, logs, and operating system on the GitHub tracker.
Windows users may have fewer issues than Linux and macOS, but functional regressions remain. For those printing with Kobra X, the printer does not appear in the host list for network printing. The error “Failed to send print job” with Bambu Cloud using “Print plate” has been confirmed.
Conclusion
OrcaSlicer 2.4.0-alpha is full of potential, but open bugs limit its reliability on non-Windows systems. New features like Orca Cloud, Z Anti-Aliasing, and optimized infill are interesting, but they do not justify the risks for those who rely on the slicer for work.
The alpha version is intended to gather feedback and fix issues before the stable release. Those who want to contribute to the project can test it with the necessary precautions. For everyone else, waiting for the beta or final release ensures a more reliable experience.
**Have you already tested this version? Report your results in the comments or on the official tracker on GitHub.**
article written with the help of artificial intelligence systems
Q&A
What are the main critical bugs in OrcaSlicer 2.4.0-alpha on Linux and macOS?
On Linux with Wayland there are frequent crashes at startup and during use, as well as severe lag in the Device tab and mouse scrolling that is almost unusable without falling back to X11. On macOS the hover menu on Slice disappears too quickly and dialogs do not resize correctly on first launch, requiring them to be closed and reopened.
What functional regressions does version 2.4.0-alpha have compared to stable 2.3.2?
Multi-material supports suffer from a critical regression whereby interface layers no longer adhere correctly to the support. In addition, cloud sync forces the "Retract Before Wipe" setting to ON at 100% and disabling it locally has no effect, while the PA Profile for Bambu printers remains unavailable in the Device tab.
What are the main new features introduced in OrcaSlicer 2.4.0-alpha?
Among the new features, Orca Cloud stands out for synchronizing profiles and histories across multiple installations, Z Anti-Aliasing to improve sloped curved surfaces, and Fuzzy Skin Ripple for more controllable textures. Rounding out the picture are the Optimized Gyroid infill, developed with Brown University and NASA Space Grant, and Machine Input Shaping to manage axis frequency and damping directly from the slicer.
Who is the update to the alpha version recommended for and what precautions should be taken?
The update is recommended only for advanced users who intend to test the new features and contribute to the project by reporting bugs. It is essential to install 2.4.0-alpha in parallel with stable 2.3.2, use copies of profiles, never production ones, and document any issues with screenshots and logs on the GitHub tracker.
What specific hardware issues have been detected with Bambu Lab X2D?
Support for the Bambu Lab X2D is present but incomplete: the track switch is not recognized correctly, the camera is choppy compared to Bambu Studio, and separate nozzle speed adjustment is missing in the Process Settings.
Is it safe to use OrcaSlicer 2.4.0-alpha for daily or professional printing?
No, it is not safe for production or professional use due to frequent crashes on Linux, regressions with multi-material supports, and cloud sync malfunctions. Those who rely on the slicer for work, clients, or deliveries should keep the stable 2.3.2 version and wait for the beta or final release.
