I am also using the Snapmaker Artisan. The scratching happens when a new print is recently started. The toolhead’s first action is to lower on the Z-axis until the buildplate is reached. After that, it travels to the right and finally to the front until it reaches the place where it cleans its nozzle. The scratch happens precisely on the second move mentioned and is barely noticeable but sufficient to damage the nozzle.
I didn’t change anything in the original machine G-Code yet, so it should be running the same routine as yours hopefully. However, just to make sure, I’ll attach my startup G-Code.SnapmakerArtisanStartup.gcode (7.3 KB)
Steps taken:
I installed Orca 2.2.0 and Luban 4.15.0 on my Windows PC.
I connected to my printer (A250 Dual +QS & B Kit) using Luban via WiFi connection.
I sliced a file using Orca and selected the ‘Upload and Print’ option; the print has started remotely.
Current state:
On the printer screen it is displaying the ‘home page’ with a DISCONNECT button.
The file is printing and is displayed on my PC in the Luban Workspace.
Questions:
If I press ‘DISCONNECT’ on the printer, will the printing halt or continue?
If I ‘Disconnect’ from within Luban, will the printing halt or continue?
If my PC goes to sleep or powers off, will the printing halt or continue?
I have been using PrusaSlicer for a long time and am considering transitioning to OrcaSlicer. There are some parameters that I am unclear about, so as a reference, I installed SmOrca. I added my printer, but it doesn’t show up at all in the selection list. To add to my frustration, OrcaSlicer has several options for the SM250, but SmOrca doesn’t even have a setting for Single. When will the next release after beta 1.1 be? What is the point of using SmOrca… I have serious doubts.
Is it possible to move the tool to the priming tower before changing active nozzles of the dual extrusion module? Changing the nozzle while the tool is still inside the workpiece results in wiping the nozzle into the object at the start of travel to the tower.
This should be the solution (was posted in mod group and I pasted it here) :
Add a line to the Change filament G-code of the printer: G0 X [next_wipe_x] Y [next_wipe_y]. This means to move to the wipetower position first and then switch.
I’ve been testing the Orca v1.1.0 beta for a few days now, and honestly, it’s been a pretty frustrating experience. There are some cool ideas in the update, but the execution feels rushed. I’ve run into multiple bugs — UI glitches, unstable connection with the machine, and some slicing issues that weren’t there before.
I really wanted to like this update, but it’s hard to rely on it when basic functionality isn’t consistent. Definitely feels more like an early alpha than a beta. Hoping the devs take the feedback seriously and push some fixes soon, because right now it’s just not usable for regular work.
I tried to print 4 objects with Orca and all failed with horrible results.
But i just tried to run it out of the box with the presetted profiles and with snapmaker filament. I had no interest in bug reports or tweaking the slicer. I have a tweaked Cura, so why should I invest time and filament? It is just another bad experience for me with snapmaker driven software.
I’m testing 1.2.1 and I have noticed a few things. The connection issues probably need to be fixed in Luban, but the thing I want in general is more confirmation that a job that has been sent is in progress or rejected. Sometimes it takes a minute between seeing the file download on the touchscreen and anything else happening. Something in the controller firmware to show if it has been rejected or else just needs more time would be great.
I’ve been having a slicing issue with the prime tower not appearing in the right place for the second material, although this is visible in the slicer and seems to be fixed by toggling it on and off.
Other than that, everything I have tried to do with Orca has yielded a superior result to Luban, so I’m willing to give it some time to mature.
I’m seeing an issue where the toolhead keeps moving to X0 Y0 without a Z hop. This is happening during the nozzle change process. I don’t see anything obvious in the G code that would cause this although I am not sure what exactly happens during the [edit]G92 on layer change.
The result is at minimum a diagonal line scored across the surface of the object between where this movement begins and the front left corner of the plate. With some materials this results in layer separation and ultimately the failure of the print.
I have only noticed this since switching to Orca, although I am also upgrading to dual extrusion and attempting large multimaterial prints as well for the first time. Any way to turn this off?
[Edit] Trying to comment out the G92 on layer change results in a warning about floating point accuracy, so it sounds like I am stuck with that part. I am currently trying adding a z hop of 0.2mm on retract, and retracting on layer change.
I run
Ubuntu 24.04.2 LTS
Kernel: Linux 6.8.0-58-generic
Hardware Model: ThinkPad P17 Gen 2i
When I run
Snapmaker_Orca_Linux_Ubuntu2404_V1.2.1.AppImage
the installation stops with a popup “Snapmaker Orce will be set up in several…”
The logfile says
[warning] 2025-04-22 20:16:23.583291[Thread 0x000079db0e390500]:Failed to load to hints.cereal. File does not exists. /home/phenning/.config/Snapmaker_Orca/user/hints.cereal
[error] 2025-04-22 20:16:23.864196[Thread 0x000079db0e390500]:calc_exclude_triangles:Unable to create exclude triangles
[warning] 2025-04-22 20:16:24.019889[Thread 0x000079db0e390500]:08:16:24 PM: Warning: Error running JavaScript: Unsupported result type
[warning] 2025-04-22 20:16:24.022560[Thread 0x000079db0e390500]:08:16:24 PM: Warning: Error running JavaScript: Unsupported result type
[warning] 2025-04-22 20:16:24.023975[Thread 0x000079db0e390500]:08:16:24 PM: Warning: Error running JavaScript: Unsupported result type
[error] 2025-04-22 20:16:25.436962[Thread 0x000079db0e390500]:calc_exclude_triangles:Unable to create exclude triangles
If I try to run the older Snapmaker_Orca_Linux_Ubuntu2404_V1.1.0.AppImage, I get the same result, with identical log output.
If I try to run the version for older distros Snapmaker_Orca_Linux_V1.2.1.AppImage
I get a shared library error:
/tmp/.mount_OrcaSlxL0BtI/bin/orca-slicer: error while
loading shared libraries: libjavascriptcoregtk-4.0.so.18: cannot open shared >object file:
No such file or directory
If I try to run the vanilla OrcaSlicer_Linux_AppImage_Ubuntu2404_V2.3.0.AppImage
I get the same result as with the Snapmaker optimized version.
Has anyone an idea what the reason is? Some incompatibility with a JavaScript core library?
I don’t think it makes much sense to report most bugs here.
SmOrca is a derivative of OrcaSlicer and relies on OrcaSlicer for the slicing engine,
so Snapmaker doesn’t make any fixes to that part.
Bugs and feature requests should be submitted to the OrcaSlicer GitHub repository.
Even if fixes are made in OrcaSlicer, it takes a long time for them to be reflected in SmOrca.
I installed SmOrca expecting it to have print settings tuned for Snapmaker, but there was nothing.
There is no advantage to using SmOrca. You should use OrcaSlicer.
I think Snapmaker should have officially adopted OrcaSlicer and allocated development resources (human resources) to other areas.
Hi, thank you for your feedback, and sorry for the delayed response.
Since you’re experiencing the same issue with PrusaSlicer, it’s likely that the problem is not related to Snapmaker Orca but may instead be caused by the machine itself.
If the issue persists, we recommend reaching out to our support team at support@snapmaker.com for further troubleshooting. Please include your printing settings and any relevant logs to help us assist you more effectively.
Hi, thank you for your message, and sorry for the delayed response.
Before printing starts, the nozzle is intentionally heated to 250°C. This is done to ensure that any residual filament inside the hotend is fully melted and flushed out, effectively cleaning the nozzle. Once the actual print begins, the nozzle will follow the temperature settings you’ve configured in the G-code for the first and subsequent layers.
This is not an issue related to Snapmaker Orca itself, but rather a matter of how the printing process is managed. We recommend sending the G-code file to the machine via Luban and then starting the print directly from the printer’s touchscreen.
Starting the print from Luban (i.e., printing over a live connection) is not recommended, as it can be affected by network instability or the status of Luban on your PC. If the machine gets disconnected from Luban, or if your computer goes to sleep, powers off, or loses connection, the print may stop unexpectedly or result in print quality issues.
Sorry for the late reply. When switching hotends with the Dual Extrusion Module (single-tool), the machine will first go to the priming tower to purge any oozed material before starting the model. If you need further technical assistance, please contact support@snapmaker.com. Thank you!
