Hello.
I believe there are issues with the wall generator in Snapmaker Orca.
Situation: Two-color printing with text in a different color
- With “Classic”, the text elements are processed sequentially. This results in shorter travel paths.
- With “Apachne”, the elements are processed from back to front. This causes longer back-and-forth travel paths within the layer and most often leads to stringing at the nozzle.
I hope the videos illustrate the problem.
In my opinion, this is a software bug. Should I open a ticket, or does support monitor this thread?
Are you referring to this parameter? Can you screenshot which setting you mean by the second type of parameter?
I think the second parameter is also in your own screen-shot…
Only a problem when you have a big nothing in the centre, which is not that common, is it?
If ‘Classic’ works for you what is the problem?
Is it though? Certainly it might not behave the way you would like, but is it actually misbehaving? Something like Arachne is an exotic feature, and I don’t suppose Snapmaker have had any input to it – I expect you will find vanilla Orca does the same thing.
Nozzle travel is a “thing” in any print, not just prints with Arachne walls. The filament tuning should minimise stringing during travel, regardless of the reason for travel.
You could report the inefficient travel to the Orca devs, then if they roll out a fix it might eventually trickle down to SnOrca.
I have already reported it to the software team, but I think it is currently just an issue of inefficient pathing, not a core problem. However, it will be recorded in the future optimization and improvement items.
This is part of the slicing engine, NOT a small fix. This is why we have the choice. Neither is the right tool for every print. Some work better on classic some arachne. Thats how it is. Nothing to do with the u1. All my machines behave like this.
Actually you would want to refer this to prusa. THEY implement most of the slicing engine changes like this. Arachne never came to us untill they added it to their engine. And funny, Cura had it before all of them…. Could be a simple fix. Could be impossible cause of math. They would know best.
