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.
Any idea what would cause my final integration of the Lion Nebula
to look like this? I went through my data, and it looks good. I haven't changed any settings since my last time. Askar FRA300 paired with a 533MC Pro. This is the first time this has happened to me after over year of using the software, so I'm stumped.Â
I integrated one session by itself, and it did the same thing. Then I integrated one session of data all post meridian flip and it turned out fine. APP is having an issue aligning pre and post meridian flip data. Is there a way to resolve this?
I've used APP since it first came out. It's been pretty much my goto stacker. Unfortunately, I have been getting far too many errors and poor stacking results as of late. The issue you are having is one of them. Whether I am stacking a mosaic, or a single frame, I get this type of result more often than not. My equipment hasn't changed, the way I take and use my calibration frames hasn't changed, there is something that has changed in APP. I can use Pixinsight to stack, and I don't get this result. I prefer APP, but it is becoming time consuming and unreliable. Sorry I could not help you with this issue.
Hi @aceshighjedi,
This issue will happen when you enable dynamic distortion correction on data that does not need it at all. So disable it in 4) register and all will be okay.
@sj_chavez, for a mosaic, it is a bit more complicated. Do not try to make the mosaic from all the individual subs, instead make mosaic panels first withour dynamic distortion correction enabled. And then register them as a mosaic with dynamic distortion correction enabled. Then it should work fine. Otherwise, please share your data and I will have a look at what is happening.
Mabula
