Yes it can be extremely fast. But I have found that sometimes it doesn’t solve a field that astrometry.net will solve. But that is a small price to pay for software that tends to solve much faster while requiring much less configuration. So if it doesn’t solve, just try a different exposure time or move to a new spot of sky
Read More...
That could have something to do with the fact that you might still be using KStars 3.3.6 on your client machine, I'm not sure. In a couple of days, you should have 3.3.7 and then maybe it will be fixed.
Read More...
Yep, to be fair, my advice was to get the 2GB version since that's all you should need memory-wise. However, I myself instead opted for the 4GB version, just because it was just a little more money. So you can do what I said or do what I did 
Read More...
I would recommend 2 GB at least. Sometimes on my raspberry Pi 3, it uses more than 1GB, so it goes in to the Zram swap. But with Zram enabled, there is no reason 2GB is not enough.
Read More...
So that should not make a difference. Note that KStars doesn’t talk to another KStars. It talks to the INDI server. INDI has changed some recently since the last release but not enough to matter for this.
So yes absolutely you can test KStars 3.3.6 on Mac with a stellarmate that hasn’t been updated to 3.3.7
Read More...
So I found that the issue for ZWO was in the ID of two of the ZWO library binary files. I used otool to fix it. I reuploaded the dmg. Please test it again. If it works out, I will put in a pull request for the new library files for ZWO.
Read More...