UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Before I release it, I will make sure that everything is working properly and then I will release it.
I imaged two galaxy targets 3 nights ago; same optics, filter, etc. One integrates beautifully; the other gives me a circular image. I've Blinked the subs in Pix and don't see any abnormalities. I've reset all the parameters from 0 to 6...same weird result.
I was able to image same again 2 nights ago. It integrated perfectly. Then I combined the data from the night before and got a circular image again. I then started integrating 2 subs at a time from the weird dataset and got the circular image no matter what I integrated...guess I'll just throw out the set. 🤪 -john
oh boy, did you use a round telescope instead of a square one? 😂
No kidding: I have had the same in 1 occasion. It was solved by either switching off dynamic distortion correction or same camera and optics. Don’t know why, but it worked….
Hi John @favalessa,
Ah I already answered in the duplicate topic, I will delete the other one. Indeed, dynamic distortion correction needs to be disabled here. Thanks @michel82 for helping out here.
"This problem can occur if you enable dynamic distortion correction in 4) Register, if your data really does not need it. So please disable it in 4) Register and try again and let me know if all is okay now 
On our issue list, this issue is noted to be fixed as well."
Mabula
@mabula-admin Yes all is well when I disabled dynamic distortion correction. I did reset all 1 to 6 to defaults in my testing, but that must have not been disabled. I just checked and it does get disabled when I reset 1 to 6. not sure why it didn't before...I don't remember ever enabling it. I so appreciate your efforts and that I took your time with this. I did create a duplicate of my post as it wasn't showing up after a day...I think I didn't "confirm" soon enough via the confirmation email. -john
Hi John @favalessa,
No problem, I am glad all is okay now 😉 we will fix the issue going forward with dynamic distortion correction.
Mabula
