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.
Have a frustrating problem in 1.083.4 on Windows as follows:Â
I have a three-panel mosaic of the Orion region; stretching from M42 to the Horsehead, comprising of 5 sessions over 5 consecutive nights.
All the subs are identical across all panels: 300s of Hydrogen-alpha at gain139.
There is no difference in configuration, other than that for each panel the telescope is pointing to a slightly different region of the sky.
Everything calibrates as expected, and all subs on all three panels are of high quality.Â
Yet when I come to do Registration, APP fails to register the stars ONLY on the panel that happens to contain M42 (Orion Nebula).Â
Not just on one session, but for every independent session on every different night, APP fails to register the stars on that particular M42 panel.Â
After Analysis, APP even reports that the number of stars in the failed panel are about the same as the working ones (400-500) So it's not that it can't find them!
There is no reason I can fathom why that would be the case.Â
To have the problem persist on every consecutive attempt to image that arbitrary bit of sky, when everything around it works just fine, is mystifying.Â
There is no visible difference on this panel, and every sub has plenty of sharp, bright, and well-defined stars; just like all the other panels.Â
Any commentary or insight on this, before I get into the trouble of uploading 200+ FITS files? Â
Did you try with the latest beta version as well? If so and it still fails, I indeed do need the data to look at. I can start maybe with the panels which would not be that much data.
