Apr 9 2026 APP 2.0.0-beta40 has been released !
It has a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration, for mosaics even faster! 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. Improved Outlier Rejection with LN 2.0 rejection. macOS CMD+A works now in file chooser ! And more, all will be added to the release notes in the coming hours...
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 was trying to process a session with 360 lights, 120 darks, 120 bias and 120 flats on my windows 10 machine with 32GB ram. The processing would randomly just stop without any error message. I could drag around the windows, the UI would still render fine. But everything seemed stopped. Finally after hours I decided to kill the openJDK process. This happened every time i tried since then. But it stops at different points in the workflow. At one point I just tried the 360 lights, and master dark, bias and flats. It managed to produce the integrated fit, but it was stuck after that. I had to kill the process. Any idea what could be happening ? Am i hitting an upper limit of files it can handle at one go?
It never seemed to use more than 4-5GB RAM.Â
rebooted machine just to be sure and tried again. happened again at 84% of integration after 6-7 hours of processing. time to try something else.
Hi @app3sashimi,
With wich APP version does this occur? With the latest 2.0.0-beta20? If so, we are working on a stability issue at the moment, so that might be your problem as well. I think I have a solution as well and I am working to fix it a.s.a.p.
Edit: If you are using Windows, can you try this version:
and let us know if this fixed your issue?
Â
Mabula
Thanks Mabula, kicked the process off. will report tomorrow.
Mabula fixes worked! Thank you.Â
