https://bugs.kde.org/show_bug.cgi?id=430365
--- Comment #6 from mountainai...@outlook.com --- #1 I knew about (I was always slewing to M31) but is a great tip. #2 is a good point, I'll try it out!(In reply to Hy from comment #4) > Makes sense. The RMS measure inside the guider module, which is what capture > uses, includes samples from outside the capture. I added something in > Analyze to graph the RMS only in capture, but this is not what that checkbox > uses (nor would it be available to capture). I'll try and include a fix in > time for the next release. > > Could I see a log with debug logging turned on for (at least) guider and > capture? > > Of course, you can workaround by disabling the checkbox to abort capture > with large error. > > FWIW, this has not changed recently AFAIK. Has this been working better in > the past, or is this something new you just noticed? Sure, I will capture logs for you as soon as I can. AFAIK this has always been an issue. I actually emailed with you about it several months ago, but didn't open a ticket until now. I waited because the issue seemed to go away, but I later discovered that it was because I had somehow set my guider to use the main scope instead of the guide scope. All my error reporting was way, way smaller than it actually was. -- You are receiving this mail because: You are watching all bug changes.
