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.
I am following the tutorial but I am getting anerror message when registrating. Any ideas what causes this?
Best Rgards
Dennis
Were you able to select the comet etc?
@vincent-mod
Yes. Then the comet position was dtected in each frame and then the error occured.
Strange...
I closed APP and tried it again with exactly the same settings. Now it worked. 🤔
Interesting, maybe a very specific glitch. A new version will be released soon and it will be more robust by then as well.
Hi @vincent-mod,
I have a large set of very short exposures that cannot be aligned with APP currently, as they contain less than 10 stars per sub and a bright core of a planetary nebula. I wanted to use the comet registration feature to align those cores to get around this problem and ran into the same error message after selecting the comet:
I also remember getting the same error message last week in another case - but I guess I cannot reproduce that one for you again. Has the cause of this problem been identified and will it be addressed in the next beta and do you have any idea, when to expect the second beta?
Best,
Phillip
This is not possible yet with the comet registration. There are some good improvements for star detection though in the upcoming beta, due to the work on comet registration and star reduction, Mabula managed to get that improved as well. So, we have to wait for that release and then try again I think.
I was getting this error message. Switched from OpenGL to CPU, and it seems to have gone away... I'm on an M1 MacBook Air.
I have experienced a bit different error in 1.083-beta2:
Yes it's not perfect indeed in this beta yet. Mabula is improving it and the new release will have some improvements here as well.
Hello, I also registered today and downloaded the 30-day free trial version 1.082 and upgraded to version 1.083-beta2. I encountered an error in my first comet operation. It's a sad situation!
