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 have been using APP for many years but recently I became baffled. On two different nights I took some lights of the Flame Nebula and the two sets of data were not perfectly centered so there is an offset with the lights that APP should easily fix. However, attached is what I get! I downloaded the latest Beta, switch to my internal drive... have no idea what else to do. This pic is from just 4 frames from each night to save time in experimenting. I get the same result with 70 frames. Any help would be appreciated. Understand that this is just to show the registration problem and by no means has been post processed corretly.
Â
Â
Actually fixed my own problem by reducing the max star count to 40. If there is a better fix, let me know!
Hi there. It’s happening exactly the same to me since few days.
