[2022-07-08T01:08:26.499 MDT DEBG ][ org.kde.kstars.indi] - INDI Server: "2022-07-08T07:08:26: Driver indi_aagcloudwatcher_ng: Unable to build skeleton. Error loading file /Users/packaging/Craft/BinaryFactory/macos-64-clang/share/indi//indi_aagcloudwatcher_ng_sk.xml: No such file or directory"
Jasem just showed this to me, it looks to me like an environment variable issue. This path should get set by the INDI Drivers Directory set by your Ekos settings. If you have the checkbox checked, then it should be using the embedded OSX mode and setting that automatically. The path you copied from the log would be the location a linux system would use. We will take a look at it to see where it got the path wrong. Just to check, you definitely have the checkbox checked to use the embedded INDI drivers directory right?
Rob, please let me know if the setting you was asking about is the same one that I took a screen shot of. That's the only INDI setting I could think of.
Yep it looks right in the screenshot. So now the question is how the path got hard coded in the INDI driver by craft when it is supposed to change based on an environment variable based on the drivers directory path from KStars
Better question, did the driver work in the past on the same system with the same configurations? If so, do you know approximately when or using what version it stopped working? On MacOS, you can always download older versions of kstars and try it using them. If it stopped working on a certain date, we could look at what changed then in the commit history. If it never worked, then that is a harder issue to solve.
Yeah, it was perfect over the last two years until the last few editions of the nightly. I’ll go back and see which version broke it. I actually went back last night to a version from April and it was fine. I think it was when the new auto guider method was introduced, as that was what made me grab a nightly.
I had these saved on my Mac, so I could test them quickly.
Build 22.05.26 works.
Build 22.06.17 works. Build 22-06-30 does not.
Every issue in July also fails.
I went online, and I don't have access to any version before July 3rd, so I cant test versions in late June,
The issue cropped up between June 17 and June 30.