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.
Hi,
I just installed v2.0.0-beta1 which I am testing with a dataset that works perfectly with version 1.083.4.
I have the following message:
I include the contents of the console
Seems to be a similar problem like I reported yesterday evening... Same error, unkown root cause. Strange thing is, the whole process went 100% fine from Calinbration through Integration, except the auto-save. Sadly there is no visible Integration in the imae viewer which one could attemt to save manually
Thanks for reporting, we've not seen this before and I'll inform Mabula about it.
@jochen-scharmann I see a question mark in the file name in the popup. This may indicate that there is a non-ascii character in the filename and given the location of the question mark I suspect a degrees symbol º. Can you rename the file(s) to not have that character and see if that works? If it does then we will know what to fix in APP. Thanks!
thanks Vincent,
what would be helpful for such type of error message is providing information to the user, what value exactly is wrong, so as a user I could take appropriate action. "Invalid" can mean anything, from special characters, naming, file size, numbers or other values
Jochen
True, however APP should be able to handle all filename characters, so in this case (if we can fix it) it should not happen again.
I confirm that the problem was the character °.
I renamed my files and everything works fine.
Good, that means it's the same issue. We're working on it, thanks for letting us know!
