Mar 28 2026 APP 2.0.0-beta40 will be released in 7 days.
It did take a long time to have the work finished on this and it will have a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration. We extensively optimized many critical parts of APP. All has been tested to guarantee correct optimizations. Drizzle and image resampling is much faster for instance, those modules have been completely rewritten. Much less memory usage. LNC 2.0 will be released which works much better and faster than LNC in it's current state. And more, all will be added to the release notes in the coming weeks...
Update on the 2.0.0 release & the full manual
We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version.
Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.
That's a strong gradient indeed, any lights in the neighborhood? And are you using calibration files?
Apart from that, in APP there is a tool to reduce gradients. If you have your final image, you can go to tab 9, tools and do light pollution correction. Place a few small squares (like 3) close to the bottom, spread out. Then another 2 left and right from the object in the middle. And then 2 close to the top on the left and right. Click "calculate" and check what happens.
@vincent-mod Light Pollution Correction didnt really help Results of that are below, if anything made it worse. As for light pollution and calibration files. i was in the middle of a field (bortle class 4) with not ambient light sources around and i used Darks, Flats, and Bais frames (30 each). I processed the same way i have my other images, never gotten a gradient like this before and have no clue why.
Â
Ah excellent, yes a flat that has an issue (or any other calibration data) causes issues like this indeed.

