I downloaded the latest 1.2.0-rc1 version on both a Windows 10 and 11 machines, and loaded a .fits image that was correctly being plate-solved by Siril 1.2.0-beta2. After following the same procedure of Dynamic PSF star finding, and then providing a more or less central star coordinate, plate solving fails ither using a local Astrometry.net solver or the online solver. After reverting to 1.2.0-beta2 it works correctly, and installing 1.2.0-rc1 fails again, on both machines.
I tried using the configuration dialog to point Siril to the local Astrometry.net and kstar catalogs, but it makes no difference.
When trying with the local astrometry.net solver, the emerging dialog shows a typical “Plate solving failed. The image could not be aligned with the reference stars”, plus the long text.
When trying an online solver, however, instead of the long text it shows “Could not load the star catalog (generic error)”, and the console shows “Failed to read the local NOMAD catalogue”.
I even used the same reference star on both cases.
I just tried with NGC 2070 and it still fails for me, whether using the online catalogs or the local astrometry.net solver. It works without issues again if I revert to 1.2.0-beta2. Maybe the issue happens in Windows machines due to a difference in compilation? Sadly I don’t have a Linux machine anymore to try it.
I also tried other star catalogs: if I force Tycho2, NOMAD and Bright Stars, besides the error message dialog, the console says it “failed to read the local NOMAD catalogue”. To emphasize, it still mentions NOMAD even if I choose Tycho2 or Bright Stars.
PPMXL does load correctly but fails to align even if I manually detect stars first.
Thank you. Are you using a Linux machine? If so, are you able to try in a Windows one, please? Otherwise maybe someone else could test that, if possible. Maybe there was a compilation difference for the windows version.
However, is it normal for Siril to complain about NOMAD when pointing to other catalogues for plate solving?
Apparently it doesn’t work on windows, that’s what it means… When the local catalogues are installed, they often take precedence.
Remove the reference to at least one of the four catalogue files in the preferences and it will return to the normal online mode…
I’m the only dev here with a Windows machine… and it does work for me, both local catalogue and astrometry dot net (both cygwin_ansvr and a local build with a more recent version). Could you run the command:
and paste the output here, check if I can spot smthg?
I created a new, clean windows user account with admin privileges. I downloaded the portable versions of rc1 and beta2, and with rc1 I get some results. Now I can solve with Tycho2 and PPMXL, but NOMAD fails no matter what I do, with or without local catalogues with either rc1 or beta2.
In rc1 a local astrometry dot net installation does not work.
In beta2 local astrometry works immediately and fast.
What I see in the “get -a” results is that the core catalogues point to a place in ~/.local/share/kstars, but they are actually at C:\astro2\kstars_catalog (unless the first one is just a pointer to the actual location).
After installing the local catalogues in beta2, Tycho2 and others now stop working for some reason (they worked in my other original installation before the release of rc1). Local astrometry works without issues.
So in terms of practicality, the main issue now is that with rc1 the local astrometry dot net solver is not working for me even with a clean installation. I’m using a 10 degree radius, beta2 solves without issues.
Yes, I only discovered this after learning the “get -a” command. To be fair, I have not tried offline solving and color calibration (besides astrometry dot net) until now.
On my Windows 11 machine they point to the right file paths.
I installed Ubuntu on VMware. I downloaded the AppImage, installed the astrometry-tycho2-* packages, and it solves with local astrometry dot net (to the surprise of nobody, I suspect).
I tried once again with the Portable Windows version of rc1 and beta2, and this time I unpacked the .xz files which I assumed were intended to be used in compressed format, as it happens in other specific software cases. Now rc1 solves using the local NOMAD database without complaints.
The remaining issue is that local astrometry net still does not work with rc1. I reinstalled astrometry dot net, and the issue persists. beta2 works, rc1 doesn’t. They access the same folders with the auxiliary executables and catalogues, and I triple checked this is the case.
One issue I’ve noticed is that when calling the local astrometry net solving, in beta2 a small windows briefly flashes: it emerges and closes itself immediately; it’s impossible to see what it is, but I’d wager it’s a console (terminal) window. This does not happen when doing the same in rc1.
I’ve had to change the way we handle 3rd party software for rc1 because we had many problems with some Windows configurations (losing handles to all these consoles allocated on the spot). We don’t need to allocate a new console like in beta2 because there’s already one available throughout the whole time Siril runs (it minimizes when you open Siril but it’s there).
Now, I will need to see some logs, otherwise, I’m just blind to what is happening on your end.
Could you please do the following? I’m assuming you still have the regular package installed. If not, modify the path below to point to the portable executable).
Open a cmd terminal and type “C:\Program Files\Siril\bin\siril.exe” >log.txt
In Siril, set as Home directory the location where the fit you have shared is saved (I saw in the get -a output none was defined)