I am putting this here as an all-in-one stop for how to deal with this issue.
First it appears that BL is attempting to force this option to still function at least once at the 3rd layer. Many of us disagree with this choice of action. While I personally understand the motivation to “improve safety and the machine” I feel the end result is not in the interest of the community at large.
Here is a comment in the Git Hub declaring this as intended
I work in the aerospace industry, and we work with complex machinery on a daily basis. The greatest lesson learned is that when a complex machine is made in a way that oversimplifies its use, the user becomes complacent. I understand the desire to make this hobby safe and user friendly, and for one I commend them, but it should not promote complacency nor remove usability and customization.
Enough of the soap box ranting.
The issue at hand is the nozzle clump detection process. With the A1 and A1 mini, at least, it seems that BL has decided to force this process to run at the minimum for the 3rd layer. Even if you select in the printer option to turn it off.
This is forced in the Timelapse Gcode.
With this setting intact slices look like this.
The yellow highlighted section is the timelapse travel moves. The green is the 3rd layer clump detection moves. If timelapse is off the printer will disregard the timelapse moves but will still make the clump detection move.
There are ways to get around this if you’re having print quality issues due to this forced feature.
You should have a default printer setting for each nozzle type you use.
The green highlighted area will take you to the setting screen and under the machine code tab you can alter or erase the timelapse gcode. Remember if you do this, timelapse will not function, as the travel moves will not be created in the slicer.
As for altering the code User Eried suggest adding “false &&” to the beginning of the timelapse gcode.
Either way you are negating the timelapse gcode from functioning. Once done save this as a user profile for quick future use.
Now when you slice plates with the modified Gcode it will look like this.
I will say I am concerned that BL will find another way to lock this feature in. If they do, I personally will work hard to get around it or sell the printer and move to a more open platform. SO… If you’re reading this BL reconsider the direction you are going.
I hope this helps others.