https://bugs.kde.org/show_bug.cgi?id=430365
--- Comment #2 from mountainai...@outlook.com --- It's not a problem that the capture module doesn't start while Total RMS is high. The problem is that the error calculation seems to INCLUDE the intentional dither event. This causes artificially high error -- instead of the <1" Total RMS, it climbs above 10" where the guiding module is configured to abort. I've seen as high as 15. Even if the guiding module continues, it would take a long time to get back down to <2" where the capture module will continue imaging. It basically breaks my session. As soon as I turn dithering off, everything works beautifully with < 1" error. Unfortunately the weather has been just horrible lately so I can't test this further, but it did seem to happen in 3.5.0 during my one night outside. It could be related to another issue that seems new in 3.5.0: SEP Multistar will lose the guide star even with an SNR of 700 to 1100. It sometimes takes a few tries to get a good guiding session, then it's fine. I can easily reproduce this with the simulators. Click guide, it picks its primary and additional starts, gets to the point where it clears DEC backlash and then it loses the guide star and aborts. And yes, the stars are outside of the tracking square/circle. I run a RASA, so I take lots of short-exposure images. I definitely need dithering. -- You are receiving this mail because: You are watching all bug changes.
