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.
Those errors are weird and should be fixed. I have never seen this in all my testing to be honest. Is this happening with this dataset each time? Or did these problems only happen once?
If it happens each time, we need to see the data so we can fix it properly, please upload the data here then:
I have fixed the issue in FindBestRegistrationModel. I will work now on the other bug in FrameDataCalibration. Can you possible upload your data so I can solve this properly?
Fixed ArrayIndexOutOfBoundsException in FindBestRegistrationModel
As reported here https://www.astropixelprocessor.com/community/main-forum/arrayindexoutofboundsexception-in-findbestregistrationmodel-while-registering/#post-34227 an ArrayIndexOutOfBoundsException could be thrown when registering in the FindBestRegistrationModel module. The issue will be caused when dynamic distortion correction is enabled. When disabled all works as expected. The issue would manifest if APP tries to calculate distortion correction on data that really does not need it for already perfect registration. The issue is now solved and prevented by simply disabling distortion correction completely in the 2-view registration phase on data that has very little movement in the stars between the images. The user can simply leave distortion correction enabled, internally, APP will disable it for the specific registration task.
Thank you dear Mabula. That’s good News. Please tell me whats kind of info do you need me to upload? I have been experience this with any of my integrations. Didn’t happened with older versión. I changed with the 40 and 39 versión and happened similar. But I know you will fix it
This post was modified 2 months ago by hector Duran
Please make a folder with your name and issue like: Hector-CalibrationError
and upload the dataset into that folder. Then please let me know once you have completed the upload. I will make sure the issue will be properly fixed then.
I already located the error to the Bias calibration. Do you load many bias frames to make a masterbias, or do you load perhaps multiple masterbias frames? Please share as much detail as you can, so I can repeat the error on solve it with 100% certainty.
