https://bugs.kde.org/show_bug.cgi?id=430365
--- Comment #11 from Hy <[email protected]> --- I was not able to reproduce this, however I did look through the code and tightened up a couple things and am submitting merge request https://invent.kde.org/education/kstars/-/merge_requests/430 that will hopefully improve the situation. - The previous code suspended capture if there were 2 or more guide iterations that exceeded the stated guide drift value, even if they were separated by hours (in a single capture sequence). This now requires 3 consecutive guide iterations to exceed the value in order to suspend capture. - The current code exempted the states GUIDE_DITHERING and GUIDE_MANUAL_DITHERING from broadcasting its drift to capture, but didn't exempt GUIDE_DITHERING_ERROR, GUIDE_DITHERING_SUCCESS, and GUIDE_DITHERING_SETTLE. It's possible that some drift computed in one of the latter states found its way to capture, and caused capture to suspend. BTW, the current code doesn't check the RMS value. That is, it isn't looking at an average over past N samples. It considers the most recent guide deviation and makes its decision based on that one or two samples (or now, based on 3 consecutive samples). -- You are receiving this mail because: You are watching all bug changes.
