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.
Hi,
Ā
I'm trying to stack 1809 light frames saved in .fit type file.
At the end of star analysis I get popup windows with information like on the attached screen below.
I've tried to search in the console window for any information with broken frames, but I couldn't found any useful information. The console buffer to keep information is to small to cache all frames processed with information.
So, does APP have any option that I could turn on, to get a log file with detailed information about processing all frames? It could help me to find few brokenĀ frames in the bunch of 1809 lights.
Other ideas beside to check each frame manually ? this will hurt.
Not really I think, but aren't the broken frames indicated to have no registration in the list of light frames itself?
@vincent-mod
Huh.... I didn't think to look in obvious place 😳 🤣Ā
Thank you Vincet for quick hint.
Topic closed.
