I have just been ignoring it. But, yes, mine does it also.
yeah, it doesn’t seem to affect the prints or cause any damage just trying to see if this is an intentional thing or a bug
I’ve had it happen too. It’s the same behaviour you would get for a timelapse. Each layer it would move to that area to get the photo. I’ve turned timelapse off and this issue still happens on the first couple of layers (not every print though).
Seems like some lines of the gcode are stopping for the timelapse even though it shouldn’t. This could stem from the fact that you can’t turn off timelapse in the slicer settings, only from the menu when you attempt to print.
So technically the timelapse movements are in the gcode, but unticking timelapse doesn’t strip it all out.
You can see that the gcode is originally generated with timelapse movements if you check “travel” on the top right after you slice (before you print). The lines are exactly where this left movement is. The sliced preview will show it happening on every layer, so like I said earlier, I suspect a few commands don’t get stripped out properly when printing.
I opened that issue couple of days ago while analyzing the travel movement and trying to debug the numerous issues I have with this machine.
This printer is 100% rushed and I have nothing but issues with it since day one.
There are layer shifts, auto flow is not working, pa gets shifted mid print, causing layer shifts, over and under extrusion in the same print, strange mechanical noises that don’t look right, the list is long.
I have a 10 days old open ticket that has 0 traction, not even an ack from the support.
I can’t even return the unit, as the support is non existent. I understand it’s holidays season, but ghosting your customers is not an option. One way or the other you will run out of business with that attitude.
OK, so I have edited the time-lapse portion of the g-code and I no longer get the movement of the printhead between layer 2 and 3. I’ve run multiple prints now without issue.
I see the same thing on my A1, though I only noticed it since I updated the firmware recently…
Can you specify what part of the gcode you changed? I’m having the same issue
i guess you guys are talking about that nozzle clumping detection
you can turn it off in the settings
Not really, there is some bug. This is the travel with or without changing the timelapse g-code:
With the g-code modified:
Thanks now i understand 
iys all part of the process.
Suspect it’s the timelapse camera, moving the print head out of the way to take a snapshot. The printer warned me this would cause print quality issues because I’m printing a part with small thin vertical members. Sure enough, filament oozing out of the printhead gets stuck in the surface of the print, marring the surface. Going to reprint with timelapse disabled and I think that will prevent this unnecessary movement that is messing with the print surface finish.
Thank you for this!!! I hate this when using PETG because it oozes from the nozzle and the head goes over to the camera and then right back to print with a booger hanging. Drives me insane.
So, I am having this problem now with my newly purchased A1. This is not a great fix as I have to redo it from time to time. I tried rolling the firmware back and even a factory reset to no avail.
Has anyone found a more reliable fix to this. It seems this is flying under the radar as far as issue go. I know it was working fine until I accidently turned on the nozzle clump detection but even after turning it off and the other fix attempts this is here to stay.
Hi,
I think Bambu Studio is overruling the printer settings with gcode…
Nozzle clumping detection is inside time lapse gcode on printer machine gcode.
You can save the original printer as a new printer by adding a descriptive description, delete the time lapse gcode and save.
This way, when you go for slicing or printing, you just need to choose this new printer you created.
Hope I had made sense…
I have compiled an all-in-one location for this topic with ways to get around the forced 3rd layer clump detection process.
Mine did this once, I thought it was Timelapse but that was turned off, hasn’t done it since.
I think its usually if its recalculating as if can sometimes hit the print a decent bit, not saying zhop should fix this but have used a bit myself
Man, this was driving me crazy i was searching all Bambu studio options and even I didn’t know how to describe it to get help many thanks it worked and saved a lot of time