*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***
Please include the following details in any bug report:
* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
That makes sense and I can live with that. I thought it could be another small bug somewhere.
I use PlateSolve3 as it works for my small FOV nearly 100% in less than 3 seconds. I tested SharpSolve and it does only work from time to time.
But as usual one has great other possibilities in SC
rethinking it it, it seems not to be the direct fault of PlateSolve3. You can see on all three screenshots the (nearly) same results of PlateSolve3 (which coincide with the real center of the frames):
RA=16:01:49.9,Dec=+17:56:42 (your screenshot with correct annotation)
RA=16:01:49.9,Dec=+17:56:41 (my first screenshot with incorrect annotation)
RA=16:01:49.9,Dec=+17:56:42 (my second screenshot with incorrect annotation)
and from an older try of me:
RA=16:01:49.9,Dec=+17:56:42 (when ngc6030 was completely out of sight)
So I think the culprit must something else.
As this is not a great showstopper (occurring once in about 50 different frames), it may not be worth to investigate
deeper, but I wanted to share my observations.
I use a german windows 10 with the separator set to . (point), as needed by PlateSolve3.
And I would think of an offset, not set to zero, triggered by this special frame (how soever).
50 other pictures work flawlessly. May be PlateSolv3 gives (by a glitch on this special frame) some additional info to SC, which
forces SC to render the annotation incorrectly (and differently after each start of SC !).
