I imaged the Orion Nebula last night using the Beta software on a Macbook Pro. QHY183M camera, ZWO ASI120 Guidescope, Moonlight Focuser and an EQ6 Pro mount. Everything worked flawlessly. Stellar solver was very quick, guiding was spot on. Thanks very much.
It appeared to happen when I was trying to figure out why 3.5.1 stable would not connect to my ZWO guide camera. I had restarted KSTARS several times - (also checking USB cables and connections and testing the camera wouild connect with just PHD -it did) 3.5.1 had worked fine before but I was unaware of the ZWO problem since hadn't been able to image for several weeks in our winter weather. and after installing it, had only tested it with M50 CR3 raw imaging camera and its driver. So when I loaded 3.5.2 to try it the settings that were 'ooff' got carried over. Once I found the 'unchecked' settings in the Options-iNDI panel in 3.5.1 and relaoded both versions, did it function again. - BTW - I normally guide with PHD, but While using both cameras the other night to both test cameras on 3.5.2 I did not try to use it with PHD as I j was unaware of the that other reported problem. I ust did some unguided images to test tht the cameras and plate solving (ASTAP) and imaging modules all worked. -those worked fine. Using Macbook Pro -, Intel I5, 16 gig ram, Mojave Mac OS-X.
I did some test guiding this evening with KStars 350 and KStars 352
As usual I could guide with KStars 350 but not with KStars 352
My guiding camera was a ZWO CCD ASI174MM
The sky was really not good (even to find a guide star)
The two logs (KStars 350.txt and KStars 352.txt) are in the compressed folder at : dl.free.fr/rCADOFLpd
Celestron EdgeHD 11 on Celestron CGE Pro
Celestron OAG and MicroTouch Autofocuser
ASI2600MC Pro + ASI174MM
Jean Claude, Not really sure what going on.
Can you please try SEP MultiStar and see if things are better with that?
To turn that on (see screenshot below) go to the guider tab, options on lower right, guide section (2nd from top on left), and for algorithm choose SEP MultiStar.
What guiding scheme are you currently using?
Ok, it turns out that this is much simpler than it sounded. The only file that was missing from 3.5.1 that made it not work was one of the libraries, I copied that in and the camera worked right away.
As I had said before, it was just a broken link in my build folder that made 3.5.1 not work with ZWO. But it turns out that most of the files in there were good, it was just that one file.
Just copy this file into 3.5.1 from 3.5.2 and see if 3.5.1 works with ZWO for you.
Then if you can guide with 3.5.1, we can narrow down what is causing your guiding issue.
So I don't think there is anything we can really do about this. This issue has been there since I first ported KStars to Mac in 2016. Basically, on Linux, there is a concept of parent and child windows and that works very nicely where the child windows will be on top of their parent windows so that the KStars skymap will pretty much always be in the background and the other things will appear in front of it. But on Mac, windows are pretty much independent of one another unless they are like modal dialog boxes requesting user feedback. So, when I first got KStars building on my Mac, I found it very annoying that many windows would go behind the skymap when I would click on the skymap. The best solution that I found was to make all the other windows "always on top" and for the most part this works well. The unfortunate side effect of that is that sometimes a few dialogs will end up behind those windows. But I think that is much better than them disappearing behind the whole skymap which is usually a much larger window, so thats why I did it that way. Its not perfect, but I think it is the best option