EDIT :
I had to check the wiki because I wasn’t understanding what I was reading. The thing is, I had always been using the correct timelapse mode—Smooth—without really knowing its name. So when the pop-up suggested I switch modes, I figured I was using Traditional all allong and needed to switch to Smooth.
When I went to the settings and saw the difference in print time, I went back to the wiki to double-check. That’s when it got even more confusing—because after looking at the GIF that shows the difference between the two modes, I realized I had never used Traditional before. So I couldn’t understand why it was suddenly enabled.
Somehow, it seems like Studio decided to switch the setting on its own, because the print I did just a few minutes earlier was definitely on Smooth.
and that is the case for also all the print i did before, so another bug ?
The traditional timelapse records a pic at the end of each layer regardless of where the print head is.
The smooth timelapse takes a pic at the end of each layer with the print head over the poop chute.
Due to possible oozing during the photo shoot, the nozzle is then primed on the prime tower.
=> So there are more travel and priming moves with the smooth timelapse.
=> For thin, tall models where layer time becomes a problem, enabling a smooth timelapse can force additional cooling time, preventing overheat damage.
So then why does the warning suggest that the traditional mode may cause surface imperfections?
Also confused by this, if the camera is just taking pictures between each layer and not moving the toolhead or doing any other adjustments, how does this cause imperfections? I would assume smooth mode is more likely to cause imperfections, as we have to move the toolhead, deal with additional part cooling, and then use the prime tower to purge/clean potential oozing
Logically, it seems like smooth mode has more potential to cause issues.
I regard it more as a disclaimer regarding oozing rather than an actual oozing. Although the introduction of “ramming” may have something to do with it. There are certainly some related issues with the H2D which need to be addressed. Can’t really go into it though as I do not have an H2D.