OK. You don’t have to wait if you don’t want to (for testing anyhow). I probably won’t be able to address this until next week. This should only be a problem with new sequences.
I’m pretty sure I know what the issue here is… no need for additional reports or logs.
In case it was not clear, this was not a new sequence, rather a very old one that I have been using for months (and through numerous SGP upgrades.) Luckily I had a backup copy to restore after it got zapped since it has my targets that I will continue shooting after the moon goes away.
Ditto. An old sequence I didn’t care about. I have not tried to continue using 2.5.0.4 after opening the sequence, but at a minimum, if you do, you will have to recreate the entire sequence since it zaps all your entries and comes up like a brand new sequence.
It was perfectly clear. Since I cannot fix it right now, I was suggesting
that, in order to expedite fixing of the more serious problem, folks may
want to create a simple sequence and reproduction the crash. Nobody else
can download this version.