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.
Today I attempted to Mosaic 2 images together by loading all of the 200 images and the master calibration frames.
This processed up to 6) Integrate where the following error message popped up.
This is where it errored out.
I was not able to find a way to increase RAM in the CFG.
Any way past this?
Hi Paul @paul-from-northern-mi,
Thank you very much for reporting this. With which version is this happening? One of the new beta's I think? If so, yes, we need to remove the message that you can still adjust RAM, since in the 2.0 beta's you can no longer or need to adjust this.
A mosaic of only 2 panels should not have a problem processing with 14GB of RAM for APP, so something is off and it might be caused by the way you are processing. Best would be to process the 2 mosaic panels separately first using normal registration, giving you 2 mosaic panels.
Then simply load the 2 mosaic panels as lights and register them as a mosaic. This workflow is much !!! faster and more robust.
Please let us know if this helps 😉
Mabula
Mabula,
Yes, the error shows up in version 2 beta 6.
I have found that processing each individual frame and then combining as a mosaic does work well.
I was looking for an alternative however as I have observed some degradation of detail on a large mosaic project that I have been working on (20 plus tiles).
When I tried an individually processed 2 panel Mosaic I had no issue.
Yesterday I tried a 23 panel Mosaic, which processed but gave me a very strange result.
Only 1 fully rectangular image resulted, and it was rainbow hued.
Dear Paul @paul-from-northern-mi,
That is caused by OpenGL. Disabling OpenGL with the top left OpenGL button solves that. It is caused by a bad graphical driver on your computer, which probably does not report correctly the maximum openGL texture size. Is your mac up-to-date?
Mabula
Mabula,
Yes, the error shows up in version 2 beta 6.
I have found that processing each individual frame and then combining as a mosaic does work well.
I was looking for an alternative however as I have observed some degradation of detail on a large mosaic project that I have been working on (20 plus tiles).
Okay excellent @paul-from-northern-mi, thank you for your feedback.
Â
Thank you Mabula.
 I have always been using the defaults.  This did work well with just 2 frames in the mosaic.
 I will certainly change settings and retry.
