June 24 2026 APP 2.0.0-beta46 has been released !
Improved internal memory configuration (lower ! memory usage), fixed beta45 startup issue, fixed Set Save Directory & 2-panel mosaics.
May 27 2026 APP 2.0.0-beta45 has been released !
Fully Multi-Threaded LNC, many improvements for the registration engine, platform upgrade, and further tuning of internal memory consumption and memory release back to OS.
Apr 14 2026: Google Pay, Apple Pay & WeChat Pay added as payment options
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 unfortunately captured my lights at the wrong gain compared to my flats, darks, dark flats. Â I understand I can't calibrate the lights with these masters, but the application should probably tell the user that vs throwing the javascript error below. Â Also, it might be interesting to give the user a choice, just to see how it turns out. Â My gain is only slightly off.
Â
Encountered error in module:
CreateCalibrationDetails
Â
Error Message: java.lang.NullPointerException
Cause:
null
bV.a(Unknown Source)
bV.doInBackground(Unknown Source)
javax.swing.SwingWorke$1.call(SwingWorker.java:295)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
Yes, that would be a better flow, I agree. A somewhat more readable error maybe. 🙂 We aren't changing the rules of the program in the sense of giving the user a choice to use data that doesn't work with calibration, it wouldn't result into data that is nice to look at. In cases like this it's better not to calibrate at all or at least retake the bias and darks with another gain.
