We are officially launching a public beta for Snapmaker U1 users. This beta decoupled the Orca web and Snapmaker App architecture for connected services and included several bug fixes. Since this decoupling involves major changes to the online connectivity system, we will first conduct a beta test to evaluate the stability and reliability of the new architecture before a wider release.
Ready to join the beta test? Check out the details below!
Compatibility
Snapmaker U1
Testing Timeline
Beta Duration: May 21st – May 31st
Tester Incentives
Rewards: Approximately 10 highly engaged participants will be selected to receive a $50 official store gift card.
Validity: The store gift card is valid for one year from the date of issue.
Release Notes
Snapmaker Orca
Decoupled the Orca web and Snapmaker App architecture for connected services.
Fixed an issue where nozzle and filament settings were not properly mapped when printing directly from the built-in model library.
Fixed an issue where printing failed to start after slicing in Snapmaker Orca.
Snapmaker App
Fixed the issue where the red dot on the message page did not disappear.
Fixed the issue where multiple printing consumables did not match.
Leave a comment directly below with a clear description of the issue and attach all necessary files (log files, G-code, screenshots, or videos) to help our team troubleshoot.
Important Test Rules & Notices
The beta software will not cause any damage to the printer hardware itself. Users can exit the beta test by uninstalling the beta software/Apps at any time.
Let’s slice, print, and perfect this software together!
I don’t use the app nor do I print through the cloud. My U1 is & always has been in the LAN mode. Still I’d be happy to test SN Orca beta if needed.
The Android app seems to be signed with a different key than the Play Store one - my phone therefore blocks the upgrade.
I’d suggest either using the same signing key or changing the package id (e.g. to com.snapmaker.lavaapp.beta), so users can have both installed in parallel.
Thanks.Testing Snapmaker Orca beta with your U1 in LAN mode is absolutely valid and helpful. We would greatly appreciate your participation.
Please feel free to test the slicing and local connection features, and report any issues you encounter.
I will test both Snapmaker Orca 2.3.2 and the android app.
As a first suggestion, please update the Snapmaker Orca so that the device page respects the Dark UI theme selected by the user. The main interface does but when the user switches to the Device tab, it is always shown in bright white.
Thanks! I also saw two more users in Discord mention the same request. I’ll check with the senior engineers and let you know if there are any updates.
However I’m not sure what you mean by decoupling Orca web?
Orca Slicer just released some major fixes with their 2.4.0 alpha release. Will Snapmaker try to align with this release sometime in the near future?
Also, have improvements been made to the user login yet? I find the SN Android App login fairly quick, but the SnOrca user login very slow and takes much too much time causing SnOrca to lockup until the login process is finished.
Hi, “Decoupling” is intended to allow the software to launch and slice locally without having to wait for a slow login process — which helps address the freeze issue you mentioned. This is something we are actively working toward.
As for whether there is a plan to align with newer Orca Slicer releases, there hasn’t been any official announcement yet. I’ll record this and check with the engineers later.
If it’s not already a known issue, the “filament for features” section that should allow for different extruders on walls/infill, etc, doesn’t seem to work. You can pick the different filaments as expected but it all slices as one filament. Tried it in normal Orca slicer and it works as expected.
It works with Nvidia drivers 535 in Ubuntu 24.04.
(Nvidia GTX 1060)
EDIT:
Tried this in Orca Slicer 2.3.4 and found that the AppImage from GitHub doesn’t work out of the box too. libopengl0 and libglu1-mesa need to be installed manually.
Maybe these packages are included in your AppImage and need to be updated?