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 just given this error message and have no idea what it means:
Astro Pixel Processor - 2.0.0-beta39
Oracle GraalVM 24.0.1+9.1 - Windows-64-bit
Encountered error in module:
StarAnalysisActionListener
Error message:
java.lang.NullPointerException: Cannot invoke "com.ariesproductions.myProgressMonitor.a.c()" because "this.a.a" is null
Cause:
Cannot invoke "com.ariesproductions.myProgressMonitor.a.c()" because "this.a.a" is null
astropixelprocessor@2.0.0-beta39/com.ariesproductions.starAnalysis.j.a(StarAnalysisActionListener.java:444)
astropixelprocessor@2.0.0-beta39/com.ariesproductions.starAnalysis.j.doInBackground(StarAnalysisActionListener.java:299)
java.desktop/javax.swing.SwingWorker$1.call(Unknown Source)
java.base/java.util.concurrent.FutureTask.run(Unknown Source)
Hi Julian @jaop2p,
Thank you very much reporting this error. I have not seen this error myself yet, but i have put the error on my issue list, to try to solve it 😉
I think that we can click the error message away, that all still works fine, or did it not? Did you see this error more frequently or just only once?
Mabula
Hi Mabula
The error message clicked away and the I was able to complete the stack. It has occured only once.
Thanks
Julian
Okay Julian @jaop2p,
Thank you very much. I have made a note of the error and I will try to avoid it from happening in the next release 😉
Mabula
