this time I’m going to keep my opinion to myself, but still i’d like to let you know my findings and would be interested in your opinion.
Some of you might have noticed, or might have not, but when you turn clumping detection OFF - it actually stays ON.
which in my case creates defects on almost every print and there is apparently no solution as they refuse to let us (the end-user) decide.
What this does: On layer 3 the print-head moves off the build plate for an instance and then goes back to printing, leaving on that exact spot a hole, cut, blob, or string.
Just received their 3rd response and they’re not going to let us choose.
Therefore the only option without having to mod every single g-code was do downgrade Studio to version 1.9.1.58 with which I will stay unless Bambu decides to let us (the user) decide which detection we want to run*
*Ironically the current firmware 01.03.01.00 still offers a “Clumping detection On/Off switch” in the menu. (Which as you might have noticed by now - is useless)
I see you too are dealing with this nonsense. I personally just remove the timelapse Gcode as a whole from the printer setting in bambu studio. You will have to repeat this if you reset the modified value to a default printer setting but it is a viable workaround at the moment.
If it is the case that this feature is being forced, then it is a shame and not good for the hobby. The few posts I can find seem to indicate that this is a bug.
I am leaning currently toward that notion. First this is governed by Gcode within the timelapse section. When you slice a plate it will show all of the travel motions for a timelapse print. If you run the print with timelapse off the print head will not make any of the moves planed in the slicer for the timelapse. BUT is does still run the 3rd layer clump detection. If you delete the timelapse Gcode or add false && to the beginning the software will slice without the travel moves for timelapse or the 3rd layer clump detection.
I just tested it by erasing the entire timelapse gcode (not doing any timelapse anyhow) and the annoying move has stopped! You can’t believe how happy this makes me. I tried to get around this for hours, but seemingly searched at the wrong spot (thank to bambus support) who said it had nothing to do with timelapse but was a clumping detection that could not be switched off.
Lesson learned: Do not always trust support - Think different - Try anything.
