I have the same problem with the 'Sync' option being greyed out after doing a recompile of the bleeding edge version (using my own script or Nou's astro-soft-build scripts). This has been an issue for at least a few weeks for me.
I get around it by running Nou's build-soft-stable.sh script after running my own bleeding edge script which doesn't do an install as the last step, leaving 2 versions of kstars available for me, the installed stable build, and a separate folder for the bleeding edge version.
Note that running Nou's build-soft-latest also (for me) leaves me with a missing Sync option. The fact that running his stable build afterwards fixes the problem is curious, as when I run the lastest bleeding edge code from my own directory, the sync works (only after his stable build).
Sorry if this is a confusing explanation.
Read More...
In my case I augmented a 22.04 Ubuntu installation with Rob Lancaste's AstroPi3 setup script github.com/rlancaste/AstroPi3
Then when my own installer code had issues, I have subsequently used Nou's script for installing when I want to try the stable or nightly builds. gitea.nouspiro.space/nou/astro-soft-build
If you haven't try these, maybe they'd help?
Read More...
This isn't a very helpful response, but does it all work correctly when you use the simulators?
I'm running Ubuntu 22.04 on a MeLe Quieter 3C using a Celestron CGX, Pegasus FocusCube v2, Zwo 224mc for guiding and a Nikon Z7 DSLR on a Skywatcher Esprit 120, without problems at the moment.
Read More...
I believe the Mac nightlies can be installed from binary-factory.kde.org/job/KStars_Nightly_macos/. There are occasional hitches in finishing the compile run.
Read More...
I just downloaded this version (the May 4th version) and installed it over a previous version. It launched appears to work OK for me (not tested at night). binary-factory.kde.org/job/KStars_Nightly_macos/
Cheers
Read More...
Toni, that approach of using the simulator to capture an image and use it as the reference fits file is brilliant, thanks.
Read More...
I have to slew away from my home position to get the simulator to solve, but after that it works for me. Might be target specific. I see your point about repeated solving.
Read More...
I'm probably out-to-lunch here; the image from Tony above shows the simulator position after slewing to that position. I would then do a Align "Capture and Solve" Sync to get it to show exactly where it ended up. That adds a white rectangle labelled "Solver FOV". The Slew to Target option should get you exactly onto the target within the chosen accuracy. The Alignment tab does report PA in the solution. So would doing an align get you the values you need, when scoping out your target? Maybe the Simulators would let you do this during the day in advance.
Read More...
Just a follow up on this bug / issue... Using Nou's astro-soft build scripts.gitea.nouspiro.space/nou/astro-soft-build.
Building the stable release ./build-soft-stable.sh works, The Solver Sync radio button is enabled for my Celestron CGX.
Building the bleeding edge ./build-soft-latest.sh. results in a greyed out Solver Sync radio button.
All using the same setup. Would rebuilding the profile and optical trains from scratch help this?
I didn't see anything in the logs, when I last looked.
Read More...
I'm in: although weather, alignment issues with the bleeding edge version, and my innate ability to make mistakes might complicate things. 
Read More...