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'm running Windows 10 with all updates applied and have an Nvidia GeForce RTX 2080 Ti video card driving a Samsung G9 Odyssey monitor capable of 5120 x 1440 resolution. Â When in the step 1 load process, APP or Windows goes into a loop spawning multiple windows. Â The only way to make it stop is to change the screen resolution. Â I've tried running APP at every resolution the video card allows, but the same problem occurs. Â Thankfully, the problem doesn't occur at any other step in APP's processes. Â Has anyone ever seen anything like this?Â
Â
Could you have a read through this post? https://www.astropixelprocessor.com/community/windows/windows-64-bit-app-glitchy/paged/2/
It may be related with an issue that seems to crop up sometimes with Nvidia drivers/cards, incredibly frustrating bug somewhere which we're not completely able to find yet. There are some things that helped people in that post.
@vincent-mod,
Adding the line -Dsun.java2d.d3d=false to AstroPixelProcessor.cfg appears to have fixed the problem.  Thank you VERY much.  That was a maddening problem.
By the way, as Raymond Schilke mentioned in his post, I am also running an Alienware computer. Â That might be a clue. Â
Thanks again.
Jerry
Yes, apologies for that inconvenience, we hope to get this working better when we migrate to Java 11.
