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.
I'm running Windows 10 with all updates applied and have an Nvidia GeForce RTX 2080 Ti video card driving a Samsung G9 Odyssey monitor capable of 5120 x 1440 resolution. Â When in the step 1 load process, APP or Windows goes into a loop spawning multiple windows. Â The only way to make it stop is to change the screen resolution. Â I've tried running APP at every resolution the video card allows, but the same problem occurs. Â Thankfully, the problem doesn't occur at any other step in APP's processes. Â Has anyone ever seen anything like this?Â
Â
Could you have a read through this post? https://www.astropixelprocessor.com/community/windows/windows-64-bit-app-glitchy/paged/2/
It may be related with an issue that seems to crop up sometimes with Nvidia drivers/cards, incredibly frustrating bug somewhere which we're not completely able to find yet. There are some things that helped people in that post.
@vincent-mod,
Adding the line -Dsun.java2d.d3d=false to AstroPixelProcessor.cfg appears to have fixed the problem.  Thank you VERY much.  That was a maddening problem.
By the way, as Raymond Schilke mentioned in his post, I am also running an Alienware computer. Â That might be a clue. Â
Thanks again.
Jerry
Yes, apologies for that inconvenience, we hope to get this working better when we migrate to Java 11.
