Really I don't understand what's happening here. I thought that the changes to use G channel by default was in place, but after a long pause for weather and health problems I've been again under stars with bad results.
I'm using 64bits Stellarmate with KStars 3.6.0 (the latest stable one).
On FITS viewer, I've configured 3D Cube checked and WCS checked (this latest is not needed).
On the focus module, I've configured detection SEP and SEP profile to the standard 1-Focus-Default. The algorithm used is Linear 1 Pass (but I think that doesn't matter)
With this configuration I expect that the focus algorithm will use the green channel or the average of them (I don't remember which one was the final decision). But what I've found is that it keeps using the R channel with bad results for the other two. This is the top left corner. You can see how the spikes of the bright star begins to duplicate and separate, also, this will show coma on G and B channels:
So my question is: are there any way to influence which channel is used that I'm not aware of if?. Are there any information logged out about the kind of image StellarSolver is using here?
Two things: Last time I tried focusing with my OSC camera I also got bad results, so you're not alone.
Second, I had the impression the stellarsolver lib does what it's supposed to, i.e., when getting a color cube image, use the green channel. If that doesn't work, the culprit (IMO) must be EKOS. Either it debayers but then sends only the first channel, or it sends the raw file (but there green should definitely dominate).
openSUSE Tumbleweed KStars git INDI git
GPDX+EQMOD, CEM60EC, ASI2600/1600/290mini+EFW+EAF