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.
Hi team,
Loaded all my lights, darks, flats & dark flats as usual but for some reason whenever I reach step 5 it crashes and I get this message.
Encountered error in module: CalculateScaleInCropworker
Error Message
java.lang.NullpointerException
Cause:
null
s.a(unknown Source)
s.doInBackground (unknownSource)
javax.swing.Swingworker$1.call(swingworker.java.295)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
I've run this four times on two different machines (macs) with the latest version of the App installed.
Very frustrating, can you help?
cheers
Andy
Sorry for the inconvenience. What APP version are you using?
@vincent-mod
Hi Vincent, as stated in my op, I’m using the latest version App 1.075
cheers
Ah right, I overlooked the "latest version" part. What I notice is that many crashes seem to be related to the data itself. Could you perhaps try this again without calibration data? And then add them separately to see which data is causing it? I can then ask you to upload that and will pass it on to Mabula.
Ok, took a while to get it done but it eventually worked. Seems a master dark flat was the issue. Good call to work through it that way. Thanks!
Superb! I think this is the cause many times, it would be nice if APP could somehow recognize this better, but at least you got it sorted. Interesting to know if you saw anything weird with that frame?
