Hello Snapmaker Orca Beta users,
We’re collecting the issues you’ve encountered when using Snapmaker Orca Beta V1.0.1 and trying to solve them asap.
Here’s how you can share your feedback:
- Submit a Support Ticket: Contact our support team directly by submitting a support ticket or emailing us at support@snapmaker.com.
- Post in This Thread: Feel free to discuss any issues or concerns here.
- Avoid posting feature requests here. Discuss them in the dedicated thread: Snapmaker Orca Beta V1.0.1: Features Request & Discussions
Before posting:
- Check this thread for existing reports and solutions. Your issue may already have been reported and addressed.
We appreciate your feedback!
Known Issues & Workaround
#1 Multi-Extruder Setup Bug
Description:
This is a known bug in Orca (Snapmaker Orca and Orca Slicer). This results in incorrect detection of extruder counts. Additionally, after Orca introducing preliminary support for multi-tool/multi-extruder, it has restricted the ability to add custom materials in multi-extruder mode, causing user confusion.
Example:
Solution:
Planned Fix: This issue will be addressed in Snapmaker Orca Beta V1.1.0.
Current Workaround: Switch to Single Extruder Multi Material and manually sync the material configuration. Orca treats material changes as tool changes in its logic. This workaround allows the use of Single Extruder, Multimaterial mode to simulate Multi-Extruder mode while the bug persists.
-
Open the Printer settings page.
-
Navigate to the Multimaterial tab and select Single Extruder Multi Material.
-
Return to the main interface, where you can now customize and adjust the Filament quantity.
#2 Port 5000 Occupied/Connection Issue in Luban
Description:
Port 5000 being occupied by the system, the following features cannot be used on macOS 14+:
Enabling Orca (Orca Slicer and Snapmaker Orca) to transfer G-code via Wi-Fi, using Luban as the transfer station to enable Orca to communicate with your Snapmaker machine through the OctoPrint protocol (protocol: Octo/Klipper; port: 5000).
Solution:
Planned Fix: An alternative port will be provided in the next Luban version (V4.15).
Current Workaround: Disable the Airplay Receiver as shown in the image below and restart Luban to establish the connection.
