I wanted to try photographing the comet and used Kstars/Ekos as I always have.
But at the end after taking 300 Light, 41 Dark, 41Flat and 41 DarkFlat, the photos are not there!!!
Or rather there are, but each generated folder contains only one photo which, even if it has the number 001, is the last image and all the others are not there!!!
And during the sequence, I saw that the photo changed with each shot, but as I said, there aren't any.
I've searched all over my Mac, but nothing. What could I have done wrong? Otherwise where could these photos have gone?

Thanks to whoever can help me.

Have you tried looking in the Analyze module to see if it shows a record of all the frames you shot (you can reload the file from the session in question if needed? If you can see the frames that EKOS captured in the analyze module timeline, if you click on one of them the display at the bottom of the window will show you the directory path of the stored file. Maybe that helps if I understand your question?

Best of luck in any case.

I did as you said, I uploaded the log from last night's session and I can see everything there,
but if I click on the various photos, it gives me the path but the files all have the same name!
It seems like every time it downloaded one photo, it went to replace the other one.
I feel like crying!

Mimmo,

I've never had EKOS not increment a file name for each frame in a sequence. Out of curiosity and to see if others might be able to help, what is the name of the one light frame that was saved?

The name is: 2022 E3 (ZTF)_Light_20_secs_001.fits
And all the files you see in the Analyzer log have this name.

This happened to me too. I noticed that a plus sign in the file name also causes this data loss. (e.g. "PNV J00215475+5231007"). Fortunately, only a quarter of an hour of material was lost the second time.

Anyway, it's an excellent software, I've been using it for several years with great satisfaction. Thanks for developing it!

I don't know. Maybe he was bothered by the parentheses?
I did test it with a sequence using the same name, though, and
everything worked normally.

Looks like this is a bug in the Windows version: see here

Are you using the scheduler? I've had something similar a while back, and unchecking the option 'Remember job progress' solved it for me. But again, your problem may be more related to the bug that is reported.

Yes, I use scheduler too. I have to leave the option on The "Remember job progress". There was no such problem in previous versions.
Version: 3.6.3 Stable, Build: 2023-01-31T10:34:48Z, OS: Kubuntu 22.04

I realized one important thing: the error only occurs if the file name contains the "target name" (%t).
This is what I use now in the format text box: /%t/L_%F_%e_ So everything is fine!