MAY 4 2026: APP 2.0.0-beta44 has been released !
New improved internal memory controls should now work on all computers
May 1 2026: APP 2.0.0-beta43 has been released !
Improved internal memory controls (much more stable and faster on big datasets), fixed CPU image viewer, fixed Narrowband extraction demosaic algortihms.
Apr 29 2026 APP 2.0.0-beta42 has been released !
New improved Normalization engine, Fixed random crashes in integration, fixed RGB Combine & Calibrate Star Colors, fixed Narrowband extraction algorithms, new development platform with performance gains, bug fixes in the tools, etc...
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.
General
4
Posts
4
Users
0
Reactions
1,248
Views
Topic starter
July 15, 2024 14:39
Can anyone help on why I am getting this strange integration result. Each single fits file looks fine. This is result from a Oiii-Sii filter. I have performed this integration before (on a different set of data) and it was fine.
This topic was modified 2 years ago by Srini C.
July 16, 2024 02:55
Give it a try with dynamic distortion correction unchecked on registration.
November 23, 2024 18:31
Dynamic Distortion Correction does not seem to matter or work for me when i encounter this result. Did it work for you?
November 27, 2024 17:59
Hi @sj_chavez,
This problem occurs when you enable dynamic distortion correction on data that does not need it all. So if you disable it, the data should look as expected. Did it not?
Mabula
