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.
When I try to use the light pollution tool, it begins by neutralising the background of the image, so I can no longer see the light pollution! This is before I have drawn the boxes. What am I doing wrong? This did not use to happen for me.
Then you likely already have a very nice background. You probably can still get it to show up by stretching more, try a stretch preset (on the right under the DDP checkbox) for 30%.
You don't understand. Immediately after integration the pollution was clearly visible. When I selected the tool, without drawing any boxes or telling it to calculate, it was not visible, and nor were most stars. it looked like an unstretched image.
That seems like a data issue then. I may have to have a look at it, can you show a before and after screenshot?
Unfortunately I did not take screenshots. I was able to process the problem image by putting it back into APP. It was made from 30GB of input data, so processing used up most of the available storage.
I have run APP with different data and the problem did not occur again.
Â
