Cura
Cura copied to clipboard
Deactivate Combing Mode for the first Layer
Is your feature request related to a problem? Please describe. The "Combing Mode" is a great feature. The advantages are obvious. But IMHO the combing mode only makes sense on top of already printed layers. If you start with combing mode activated at base layer of the one part you get strings of filament traveling around with your hotend and probably destroying your object later on - of the other part the base layer gets ugly due to the chaotic additional filament tracks.
Describe the solution you'd like Attribute [checkbox] “no combing mode at base layer” -or- Attribute [integer] “starting combing mode from layer number x”
Affected users and/or printers Everybody and (esp. for optical reasons as mentioned above) all filament types are affected.
My cura builds already feature this setting, if you wish to try them go to https://www.dropbox.com/sh/s43vqzmi4d2bqe2/AAADdYdSu9iwcKa0Knqgurm4a?dl=0. Please read the README.md file there before using.
Great! Thanks! BTW: is it ok to leave bugs via this platform for Version "master" as well? (there´s still the crash problem when a users profile is corrupted)
If a problem exists just in my builds please report at https://github.com/smartavionics/Cura/issues but if it affects both my builds and the UM builds it would be better to report it here.
To prevent scarring (or "chaotic filament tracks"), disabling combing is not enough. Instead of combing it'll go in a straight line to the destination. It'd also need to Z hop then.
Also in my release...
You can ask for z-hop on the initial layer(s).
I've added this to the backlog as CURA-7572
We are constantly working on making Ultimaker Cura better. Our community is a big part of that by requesting new features and reporting bugs.
To be able to focus on the most requested and needed features from our community and from Ultimaker, we have decided to remove this feature request from our backlog. We believe we will not work on this anytime soon and will therefore defer this issue.
Since Cura is open source, you or anyone else is more than welcome to work on this issue and create a pull request yourself.
I've just noticed this on mine too: the combing on the inital layer causing really thin extrusion that doesn't adhere because its just what is oozing during the comb move (over not-yet printed walls). @smartavionics you say you're build already has support for this issue - is it something that is easily cherry picked?
Hello @MeirionHughes , the changes are trivial....
This is added to the travel section in fdmprinter.def.json
"travel_no_combing_on_initial_layer":
{
"label": "Disable combing on the initial layer",
"description": "Disabling combing on the initial layer can improve the adhesion of wall lines to the build plate.",
"type": "bool",
"default_value": false,
"enabled": "resolveOrValue('retraction_combing') != 'off'",
"settable_per_mesh": false,
"settable_per_extruder": true
},
And this fragment goes into GCodePath& LayerPlan::addTravel() before bypass_combing gets tested...
if (layer_nr == 0 && comb != nullptr && extruder->settings.get<bool>("travel_no_combing_on_initial_layer"))
{
bypass_combing = true;
}
I would also love this feature. When printing things made of many small complex parts, it does so much unnecessary travels over where once will be walls, it sometimes takes even more than 3 seconds of dancing into the position, instead of one fast 200 mm/s movement. This then leads to the start of the line not sticking well.
Hi 👋, We are cleaning our list of issues to improve our focus. This feature request seems to be older than a year, which is at least three major Cura releases ago. It also received the label Deferred indicating that we did not have time to work on it back then and haven't found time to work on it since.
If this is still something that you think can improve how you and others use Cura, can you please leave a comment? We will have a fresh set of eyes to look at it.
If it has been resolved or don't need it to be improved anymore, you don't have to do anything, and this issue will be automatically closed in 14 days.
This issue was closed because it has been inactive for 14 days since being marked as stale. If you encounter this issue and still have a need for this, you are welcome to make a fresh new issue with an updated description.