Mar 28 2026 APP 2.0.0-beta40 will be released in 7 days.
It did take a long time to have the work finished on this and it will have a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration. 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. And more, all will be added to the release notes in the coming weeks...
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.
Version 1.082, OSX latest version
Appears consistently, tried on different stacks and combinations.
Wasn't the case in previous versions (at least with 1.080).
Thanks!
Thanks for notifying, do you have a screenshot of what exactly you mean? I can't actually see this black border for instance in the above comet integrations.
@vincent-mod Ahhh... sorry Vincent, it was a completely misunderstanding - please don't care about it, because I mean for black collums on my photo, not borders! But maybe it was a calibration error from my fault, I don't know. If it's not problem, I delete my previous comment and please care about Rodolphe Goldsztejn's commet!
No worries. 🙂
Hello @vincent-mod
See attachments.
Direct outputs from APP, loaded and stretched in PixInsight.
Hope this shows clearly in the screenshots.
If FITS needed, I will share from OneDrive - they are too large for attaching.
Thanks
.
Â
This does look like you had slightly different field of views (very tiny rotation) and APP stacked them with this in mind? Would you be able to try this on a dataset that you know doesn't have this?
Hi,
makes sense indeed. Will check with other data sets but not sure I can find one with absolute 0 rotation.
Anyways, this is really not a critical issue, I can live with it as solutions are trivial to fix it.
Thanks!
