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 taken 30s, 60s, 120s, 180s exposures with my Altair 26c camera and also with my Canon 6D Mk2. In everyt case when it comes to clicking on the comet after registrtaion APP only automatically finds about 10% or less of the comet nuclei. I have variuos folders of several hunbdred files but can't process thewm as I dont intend clicking on the comet all day. Is tyhere a way of getting APP to find the comet?
This usually is the case if you have either a weak signal or are so close to a star it may be confused. Can you show a light frame of the comet where it doesn't detect the nucleus?
