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.
I notice that after stacking a night of data, if I take that FITS file and load it into a new instance of APP it remembers how much data is in the file. Would stacking 2 suck files together give the same result as would stacking all the lights from scratch?
Not exactly, theoretically stacking frames together is better, but if you have enough data per integration (>40-50 frames), I personally don't see much difference anymore and it is a way to combine data for sure.
Ok, I had been stacking master light frames in APP for quite some time now and never run into any problems I was just wondering verifying that I wasn't unknowingly shooting myself in the foot.
You can always run 1 test for yourself, that's the best way to convince yourself what, if any, difference it might make.
