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.
Hello,
As the subject says: are there recommended settings in the integration tab, when you have frames with slightly diffrent spike positions (resulting from different sessions - and let's say these frames are about equal in number)?
Kind regards, Stephan
Good question, but I'm not aware of a specific workflow for that. APP registers star positions and usually spikes don't move between sessions, did your setup change a bit in between?
Well, this happens, when you have to take away your cam from the scope or switch from landscape to portrait orientation. When bringing back the cam the positioning can differ slightly, only 1 or 2 degrees, thats the accuracy you ususally achieve, but unfortunatly it's visible in the spikes...
They can differ in that sense yes, but alignment should take care of getting the exact same orientation again right? I must say I never take photo's in portrait and then landscape, I tend to try and use a similar orientation always for a target. I never saw an issue with my spikes if I did that. But I do think that if you do, it's something that needs to be solved on the hardware side.
