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 tried to do a short integration on Comet C2023E Atlas, only 5x each of LRGB at 60 seconds each, and it hit 74% on integration, then stayed there for over 12 hours in a completely unresponsive state. I finally used task manager to kill it this morning. I had 97 gb free space on the C drive which I was using for everything, a 400gb Intel 750 nvme drive. I have plenty of RAM at 128gb and an 18 core/36 threat Xeon in this computer with an AMD 6900xt video card so it shouldn't be resources. Here is a screenshot of it:
Hi @imnewhere,
Thank you for sharing this.
This is a bit weird and very likely not specific to beta20, because nothing changed in the integration module in beta20 when compared to beta19. The process states it is at 74% but the process console shows it is just loading the first image, that is not correct. I think the process console is not showing the last lines is it?
At 74% the integration process should actually be integrating the last pixels before closing. Did you check the output in the general console? Did this problem occur more often or just once? If just once, it is likely caused by your Operating System or other software claiming/blocking the harddisk probably.
So my suspicion would be that it is probably be caused by a block in IO for APP (read/write in the storage device/harddisk) I would think. Like your operating system or security software blocking APP somehow.
Mabula
