Enabling/disabling overlays won't have any effect. The images are all loaded on startup regardless if they're currently set to display.
Memory use and Virtual Memory are two different things . I'm not familiar with MS Windows. This page says look at "committed pages":
Autofocusing on stars has been the only thing supported. That said, John and I were thinking of looking into whether measures like Fourier Power that John added, or another one I have in mind (not yet added) might work for the Moon or Sun.
If anyone wants to try and report back, please give a shot at focusing on the Moon with the Fourier Power measure and report back (bad weather here). You'd definitely want to make sure that you're not overexposed--we expect that Fourier Power will not work well with overexposed/clipped pixels.
I don't know why the plate solving would be more reliable. Perhaps you're using the accurate scale now and you weren't before?
Re the number of images the overlays are kept in memory. (A less lazy coder than me might have done some on-demand loading, perhaps I'll do that in the future someday, but probably not really soon.) So, whatever virtual memory the images take will be your limit. You could experiment by adding 10 more and seeing the increase in virtual memory for the kstars process. Then add 10 more and verify you have a similar increase. Then you could decide--let us know.
Note: The file size won't tell you the answer--jpeg compression won't be taken advantage of. The full image stored in memory in a QImage doc.qt.io/qt-6/qimage.html (e.g. so the memory use will likely be something like width * height * bytes-per-channel * # channels. That is, if all your images are RGB and the same resolution then they'd all take the same amount of memory. If you're curious, you can see the code that loads the images here:
A good way to debug issue with the internal solver's plate solving is to use the FITS Viewer's solver.
See docs.kde.org/trunk5/en/kstars/kstars/kst...f#fits-viewer-solver in the handbook to describe how to use that.
Also, FYI if you look at the main "Configure KStars" menus, the bottom tab is called "Developer". If you go there and check/apply "Saved Failed Align Images", then fits files for failed alignment is saved (on Linus in the ~/.local/share/kstars/align/failed/ directory).
Given such a fits file, you can load the file into a fits viewer, and (after inspecting to make sure it is a reasonable image, e.g. in focus, "enough" stars) then see if you can get the fitsviewer solver to work, and report back.
BTW, often the issue is incorrect scale or position, so common advice is uncheck "use scale" and "use position". That's worth a try. However, sometimes with minimal stars or some-such you really need the scale. So, my advice is if you're sure of scale (and after trying unsuccessfully with both unchecked) try again with "use scale" checked, the correct scale (in arcseconds/pixel) entered in the box, and "arcseconds/pixel" chosen as the unit.
If you're using Stellarmate, then please reach out to the Stellarmate support and they can help you identify the crash.
If it's KStars and I have a little down time, I can try and reproduce the crash--I only run on Linux here, so hopefully it would reproduce on Ubuntu 22.04.
Please make sure you can repeat it, then send me:
- the fits file you used to crash the system (was it one of those you already sent?)
- the log file
- which OS/computer you're using,
- which version of KStars
- assuming linux, please send ~/.config/kstarsrc ~/.local/share/kstars/userdb.sqlite
PS If you are a programmer--e.g. this makes sense to you--please also do this
- run kstars under gdb
- when it crashes get a stack trace with the bt command
You can try the fitsviewer solver even if it is cloudy!
Use load that image into fitsviewer and solve it.
Sorry, I don't have time in the next week or two to mess with other things.
Got your two images.
I am debugging this with the FITS Viewer's solver, and you can try and reproduce my experiments.
Open the fitsviewer solver, which is documented in the KStars handbook, currently on page 169
I was able to solve solve2.fits with the configuration below using my align profile
Did not work for me, tried that unsuccessfully before and just retried same. It says "This does not look like a FITS file". It is only 4Mb.
Please post your original file somewhere and send the link.
Please upload these two files somewhere so I can download the fits files onto my machine.
Not sure why online doesn't work, but I'll be we can get offline working.
Please post an image that you can't get to solve with the internal solver.
FWIW, I have a FOV of about 1/2 degree wide with my 10" RC and have no issues solving.