just a thought... If color coding is the direction, allow the user to choose some of the colors to help different contrast settings, color blindness, themes, etc.

.This is great, thank you for this great upgrade!

As far as blind plate solving, would you uncheck in Scale and Position the RA and DEC vs leaving that and entering 0? (As read in another thread)..

Also would it be proper to leave the corresponding . update check marks in place?

A side question, are nightly builds equivalent to bleeding builds?

Thx

For the plate-solving in polar alignment, I wouldn't change the plate-solve parameters from what already works for you with normal align/plate-solve.
Personally, I tend to use Scale and Position if I'm using the Internal Solver, and I tend to disable (uncheck) them if I use ASTAP, and I tend to use both.
However, if plate solving is not working well, and other things look good (focus, weather), then I'd disable scale and position.

I'm not familiar with the "entering 0" advice, haven't heard about that.
I would keep both update checkboxes checked.

Yes, I think "nightly builds" == "bleeding edge builds".

Hy

Thanks for your reply!

That advice was in this thread:

indilib.org/forum/general/11826-nexstar-11-alignment.html#83567

Thanks for this great new addition to the PAA.

I had the opportunity to test the "Plate Solve" mode yesterday as my PA was off by more ( > 2 degrees ) than my CCD field of view but the "Updated Err:" stop updating/refreshing after a few iterations and even disappeared. Any clue as to why this happened?

Thanks in advance.

Here's a thought. Stellar Solver is capable of running parallel plate solving operations on the same image with different parameters. But given already established parameters, image scale and location, it might instead be possible to use parallel solvers on different images as the refreshes come in. This way if there is a bad frame, it can automatically be aborted if a more recent frame solves first. Just update the position with the most current successful solution.

Happy to look at a debug log. Other than that, all I can say is that shouldn't happen.

Given that this is a semi-permanent installation I don't need to PA often, but whenever I feel like doing a PA again, I will gladly generate debug logs.

I also made sure that I gave enough time (I hope) between alt-az mount motion before relying on the plate solve results but then. that may not have been enough.

Thanks again.

I don't think this alt-az movement thing is a big deal. It just means one plate solve may fail due to scope movement, but the next plate-solve comes automatically soon after and will likely succeed.

It is a great update for the PA in kstars

I can't help to try it

This is a pretty good feature. I used it last night.
Plate solving went off into the weeds a few times, but that may have been due to some high-altitude clouds coming in (and the one time my scope was pointed at a tree!).

Hi, first of all i'd like to thak you for this great software. Without it i would never ever had the chance to spend so many sleepless nights .I've been using Kstars 2.5.7 for about a year and just installed the 3.6.3 version . Only had short time to test the PA and i'd like the window to behave similar to the older version - the left side had fixed width and the right side with the picture was variable.
Is there a way to change it in the current version ?