tame mantle
It's really too difficult to tell from a fast time lapse video like that. You need to see the exact moment, in detail, to be able to know. Layer shifts can often just be the cause of a toolhead collision which will cause the motors to lose steps and suddenly think it is still in the same spot when it is obviously not.
It can also happen from a corrupted file or SD card, but since it happens at different spots with each print, that is not as likely.
wheat jolt
does it not happen if you use Cura? , if it does it's obviously not a slicer problem, also : do you have infill combination tagged by chance that will combine infill layers, in other words, if you use 0.2 layerheight it might print 0.4 layer infill, thus increasing the chance of knocking over your model.
try the same print with the same settings in Cura, if it behaves the same you know it's the printer, not the slicer.
my K1 max works fine with Cura and Bambu studio and prusa and orca.. you said yourself you haven't touched Cura in years, you realy base your assesment of cura on a years old version? get real
you are not realy willing to investigate just want to blame your printer or your slicer, ever thought that what you experiencing is the limitation of a printers resolution and of an STL file that consists of thousands of triangles?
i didn't say you have to use Cura, just try it to determine if it is orca or the printer, because how you present it you already have determined it must be the slicer or the printer.
how else would you determine if it is the slicer? you cannnot use prusa , bambustudio or creality print to try it out, since they are basically the same program. so that leaves Cura to test it
i have cura on my system, just for testing and it is just a matter of adding the k1 in the non -ultimate printer section, nothin mysterious about it, it works the same as in prusa based slicers.
wheat jolt
and if you want to avoid it in the future you have to investigate what causes it. i have used cura for a long time on my K1 and experienced no problem with klipper, I have printers that have klipper firmware and i have marlin printers with a RPI that runs linux with octoprint and those behave nicely in Cura, or whatever slicer. I myself use Orca as my daily slicer, but to figure out what is hapening, i'm alway willing to switch to a different slicer or 3d design programm to figure it out. i do not ignore a possible solution based on info that is 2 or 3 or 5 years old if the source has been updated since then.
tame mantle
I agree. Until we know the root cause, there is yet no reason to believe that either one is inherently faulty.
The crummy part of investigating these sorts of issues is that it can often waste a lot of time and material in testing since there is rarely any other way to discover the problems.
I hate to say it, but I would probably try printing it again and seeing if you can get more detail from the exact moment it happens. Things like grinding noises, a brief unexpected pause in movement, a power blip in the machine...anything like that. We basically need more symptoms to manifest and be noted in order to start narrowing it down. One thing you could try is printing the model in a different filament just for testing, like PLA, or a different brand/color of TPU.
wheat jolt
one of the things i said was: "ever thought that what you experiencing is the limitation of a printers resolution and of an STL file that consists of thousands of triangles?