Created attachment 152773 [details] Calibration plot bug SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Compare the Calibration plots obtained with KStars 360 and KStars 361 2. 3. OBSERVED RESULT KStars 360 : the calibration plots are orthogonal KStars 361 : the calibration plots are NOT orthogonal But guiding is still OK with KStars 361 EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Check Optical Train and make sure you selected the correct guider. Guider is NOT camera, guider is the the device that *receives the correction pulses* like your mount for example.
Created attachment 152796 [details] My trains Thanks for the suggestion and I checked again my trains (see attachment) : I use for guiding the secondary train including : - as guiding camera "ASI CCD ASI174MM" - as guider "EdgeHD" (a custom driver created for the config 2800@F/10.0
If this is using OAG, then the setup is indeed correct.
Created attachment 152861 [details] Guiding Yes I'm using an OAG . I repeated the guiding in KStars 360 and KStars 361 this evening and I got the same results (see attachment "Guiding") : non-orthogonality in the KStars 361 calibration plot
Yes, it's true. In fact I intentionally broke it in commit https://invent.kde.org/education/kstars/-/commit/77c4b156d5de91f04c461af41195ee11df158daa where I chose to make the calibration plot non-square (non-equal x and y axes scales) in order to make the drift target square. I wish I knew how to make both square. I prioritized the drift target over the calibration plot. You can make it square by resizing it or pulling the divider left or right. Doesn't seem to be a way to mark a bug as "don't know how to fix"!