Yepp, it only aligns after a meridian flip if an alignment has happened after the last slew.
Also, it didn't do an alignment this time after the flip - likely because I didn't align before? Is that intended behavior?
The function that creates the new index has the following step:
Hm, why would that explain it?
// No updates during meridian flip if (meridianFlipStage >= MF_ALIGNING) return;
I haven't reproduced it 100%, but it might be a side effect of a code cleanup we did some weeks ago. Testing all situations that might happen between a capture is completed and the next one could start isn't that easy, since there are incredibly many variants. And I suspect that your case simply slipped through.
And why has it changed? I have never used the deviation limit, and have not seen overwritten frames until recently, and now it's always doing this.
In case that this happens, the currently running capture is aborted and restarted. This is a very neat feature for example in windy nights.
And checking that box would abort the sequence in case of hitting the limit, no?