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.
This error happened as I was unchecking some of the files which had a low star count and bad FWHM after doing analysis. I had one error for each file I unchecked, and there after the error handler kicked in and said that that file probably had no stars. The program did not crash or anything. This is probably not intended behaviour?
Best regards
Helge
Hi Mabula
I tried to recreate this error today with the same set of files, but I could not. Not sure what happened yesterday , but it did.
Helge
Hi Helge,
Thank you for sharing this.
Another user has reported strange behaviour as well, when unclicking frames, so I will do some extensive testing to see if I can duplicate the error.
Were you unclicking frames while a process like star analysis/registration/normalization was still working?
The NullPointer shouldn't happen, so I need to find this issue 😉
Kind regards,
Mabula
