UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred  after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Â Before I release it, I will make sure that everything is working properly and then I will release it.
Especially during this time of the year (without dark skies at my place), but always if there ist some gradient by moon or simple light pollution, i experience weird quality scores that may be an issue (or not) in selecting/ordering the "best" frames for integration.
Since the quality score seems to be correlated (an it surely is dependent) on star shape/size and noise, it is higher on images taken at dawn/dusk, because stars are "smaller", noise is "lower" (because of higher background levels).
So, if i do want to have these images in my integration stack but dont want to emphasize their impact on the final image. What can i do? There are two measures that clearly are opposed to quality score, namely "dispersion" and "sky background". Both can't be selected manually if selecting a manual average integration. (And this surely is not a good thing to do?)
To illustrate my observation have a look at the following screenshot showing 6 different nights ready for integration.
As i know it would be best simply not to take broadbad images during moon or summer nights and drop images taken at dusk/dawn, is it possibe to use those in the final stack without having them identified as "best" images by quality score?
My bad.
I did start new and put every night in a different session. This time I got very similar quality scores. I did not know that this makes such a big difference. Will give this another try tonight posting the different settings and scorecharts. Just to get a feedback what i did wrong there...
Well my first post showed the results normalized "multiply" - because of images taken on different nights with strong gradients.
If I set it to "multiply-scale" (which is not advised for strong gradients!) the results seem much "better", at least the images on dusk/dawn are not as prominently high quality scores as "multiply"...
I will give it a try, what the resulting integration may look (as it is a 2-panel view i was not able to remove the remaning gradients in the first integration)
