My first few runs with the new version have apparently discovered two possible bugs:
1 - I set the park position of my scope. Next session it was forgotten. I told the scope to park but it just moved a small distance and then ‘parked’.
2 - I am finding that several ‘mosaic and framing wizard’ tries result in a error claiming that this area is not available (several Messier objects). This caused serious hassle during the runs because I was adding further targets.
Not a bug, but me! When the plate-solve process is activated during a new target acquisition, it notes the pixel error is above my threshold but it then activates the scope to drive at high speed even when only a few pixels adrift. Is there a setting to reduce the drive speed during target centring?