We too, we have strange problems on KStars 3.6.6 all of a sudden with the scheduler after a flip. The ensuing alignment cannot take place because EKOS is notifying an ongoing capture! I will investigate deeper and report back.
There is indeed a missing activation of the Load & Slew button in the Align module! I'll sign in a merge request right now.
I'm the author of the new rotator module and you are right, that's the rotator behaviour at the moment. For loaded sequence jobs you can override this with the option "Save camera Position Angle to Sequence Job", but that doesn't help you with a [Load & Slew].
But I'm working on a global "rotator flip policy" option which I'm testing right now on my rig. This allows to preserve the rotator angle (which is the current inherent policy) or to preserve the position angle (which exactly addresses your case) after a flip or after a [Load & Slew] with a "flipped" image. If all goes well I will present a merge request very soon.
From what I've learned about blocking signals, perhaps "updateRotator()" should block them too?
Did the fix make it into she solver issued with 3.6.6?
I don't think so! I hope Jasem is reading this, so he can update "Stellarsolver" for KStars 3.6.6 2023-8-1 on Launchpad.
The following line in the ASTAP-Log shows the wrong orientation:
[2023-08-16T17:27:54.639 CEST INFO ][ org.kde.kstars.ekos.align] - "Solver RA (303.86020) DEC (41.56064) Orientation (144.26970) Pixel Scale (1.19540) Parity (neg)"
Are there any new insights already?
If not, could you just try to replace the '10micron' with 'Telescope Simulator' and see how the 'Nitecrawler' reacts? This way we can exclude/include the mount as a source of the problem.
Did you try the source extraction method 'Internal SEP' together with Solving Method 'Local Astrometry'? I'm getting best and fastest results with this combination. (However you have to download all the required index files.) BTW, did you activate and update 'Use Scale' & 'Auto Update' and 'Use Position' & 'Auto Update' in 'Scale & Position' of the solver options?
Concerning ASTAP, I used to run 'astap' directly (standalone) for better insights. (I have to remark, that ASTAP failed always with focal distances > 2700mm!)