Jan 31 2026: APP 2.0.0-beta40 will soon be released with many fixes especially for Linux, upgraded development platform and 10-20% performance boost !
Jan 15 2026: FIXED LICENSE SERVER VPN Tunnel issue
 The issue could have prevented APP to start when using a VPN tunnel or another complicated network configuration, like using APP on a remote computer on a different continent. This issue is fixed now and APP should start normally.
Jan 04 2026: 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. Unfortunately, Mabula was struck by a severe flu virus in the past couple of weeks and thus could not work. He is getting much better now and he has resumed work to release 2.0.0 as soon as possible. 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.
Nov 28 2025:Â APP 2.0.0-beta39 has been released !
Hi
I'm trying to process some data I've taken over the last couple of nights, it's a mosaic, I've selected the options APP wants as it's a mosaic and I've also got drizzle of 0.5 droplets and 2x scaling. The result of my Ha and OIII frames correctly build and I get the fits file at the end. My SII reliably gets an exception trying to write the fits file right at the very end. I've got nearly 900GB of free disk space, so it's got room. I've restarted APP and tried to process just the SII and it still does the same thing. The error message just says an exception occured, with no detail as to what exception, so I have no way to try and correct the problem. The console doesn't have much more information either (other than the last message before failure being "creating FITS HEADER...").
Any way to get any extra logging information so I can try and see what's going wrong?
Thanks
I upped the RAM that APP can use from 48 to 56GB (out of 64) and it seems to have progressed.
Mm, that still shouldn't just throw an exception I think, did it work out in the end though?
