After the release of 3.0.0 it has been cloudy where I live, so I have not been able to carry out real world tests.
I have however updated my darks library with several hours of exposures (only camera and filterwheel connected).
No issues seen so far.

I look forward to some clear nights for real imaging though, but weather forecast is still bad

/Odd

Hello Okhoydal,
I’m a total noob, so I may be missing something important, here. But why the FW for darks?
Cheers
Antonio

UPDATE
Today I captured Flats and Darks from the camera panel, with no glitches whatsoever during the 3 hours it took.
THEN I set up a simulator-only profile, fired up Ekos again and tried to build a sequence.
All of this in order to rule out any CCD/FW/cables hardware issues.
Lo and behold, the sequence panel is still sluggish in its responses when trying to create/locate/load an .esq file and, while it is thinking about God knows what, it renders the laptop totally unresponsive.
The I finally managed to get it to make and execute a sequence.
Then I got the "spinning beachball of death", which lasted long enough that I got fed up and force-quit KStars.
On the Mac, when you force-quit something, the OS asks you to send the report of the crash to Valhalla in California (I guess).
I copied the text and you'll find it attached
Enjoy the reading
Cheers
Antonio

Hi,

I have no problem with my laptop (ubuntu 18.04 LTS) and Kstars / Ekos directly connected to my equipment ( atik383, SW wheel, lodestar guiding with internal Ekos ,EQ6-R ( with eqdirect usb )), ...

Maybe the failure is to some operating system libraries ( Kstars is crashing to me with raspberry with ubuntu mate 16:04... I have a post in this forum to get some help).

I am wating reply from -> bugs.kde.org/enter_bug.cgi?format=guided...kstars&version=3.0.0

it's very important to share our experiences.
I cannot test it with OS X apple operating systems, sorry for that.
good luck with your tests

cheers

Guillem

Hi Antonio,

FW not necessary for darks, but in this case it was already in place and mounted on the scope. But you can of course take darks (and bias) with just a camera with a cap.

/Odd

Antonio Soffici,

Are you using KStars and INDI both on the same computer? In other words, are you connecting to a raspberry pi or other SBC from your Mac when you experience these crashes? I had some strange crashes in OS X version 3.0 right after I first build it when I was testing it, until I updated the software on the pi. Since then, I have not seen any crashes.

I can certainly make a new Mac build if there is something wrong with the current one, but first, we would need to figure out what is wrong. Is some incompatibility in the Mac build, is there a version conflict between the KStars build on the Mac and the INDI build on an SBC, or is there some other problem that is more general that affects all users on Windows, Mac, and Linux. For the last one, it could be an issue with KStars, with INDI, or with some dependency of those.

I know that PHD2 had some changes recently to how it communicates data back to the client programs and I am planning to look into how we need to update KStars soon to adapt to those changes, but I don't think that anything they did would cause crashes in KStars, nor does it seem to affect the quality of the guiding. But I will look into that one.

It would be very good if we can get a pattern or cause of any crashes, especially if they seem to be reproducible, so that we can narrow down the cause. For me, the crashes just happened randomly until I updated the software on the pi and then they did not happen anymore. I think sometimes it happened when I was trying to focus and sometimes when I was trying to run a sequence if I remember correctly.

Thanks,

Rob

Antonio Soffici,

I did just test saving and loading a sequence file using simulators on my MacBook Pro. It loaded almost instantly with no beachball or delay of 10-15 seconds. That is very strange. I am using the latest version of Mojave on this computer that I just tested it on and the computer KStars version 3.0.0 was built on is running El Capitan, so it should work for any system running El Capitan and later. Please see if there is anything else that is strange or sluggish, because that is definitely odd.

Also you might want to run KStars from the command line to see if that reveals anything about the sluggish behavior or the crashing that you reported. Try this:

lldb /Applications/KStars.app
run

Then try whatever you can do to produce sluggish or crashing behavior so it all gets recorded.

Thanks,

Rob

Oh, I forgot to mention, you might want to set the Logging to "Default" instead of "File" before you run it via lldb so that all of the logging gets sent to the terminal window along with any crash info.

Ah, ok.
So, no total noob, then

Hello rlancaste.
No, the Mac is connected directly to the equipment (only CCD and FW, as I haven't been able to connect the EQ8 mount, yet) via KStars
The guider goes to another USB port

Hello rlancaste,
tonight I tried what you suggested.
From the attached Terminal log you'll see I had a bit of a struggle with Terminal before being able to load KStars the way you suggested.
Unfortunately I read your last message only after having set up the sequence (but before loading it in the scheduler), so the sluggish behaviour may be only partially documented, if at all.
I managed to create the sequence, to load it and to run it (simulators only) without crashes, but then THIS happened:

What happened to the resolution of KStars?
I reckon there is some work to be done on the Mac version of KStars...
Terminal log attached, along with the screenshot

Hope this helps

Cheers
Antonio

Oh, forgot to mention: I've bought the Stellarmate, and with Jasem's help I have managed to make it work (mostly) like clockwork.
Just a few wrinkles to iron out, bot for that I need moonless nights and my cough to pass.
This is the reason I've been away from this thread for so long
Sorry...
Cheers
Antonio