Anki 24.10 Beta

Anki Beta Testing
230

To add to this, the same error appears when downgrading MacOS to 24.06 and trying to study a deck that was optimized with 24.10 (19 params).

231

The release notes of the beta have this warning:

FSRS parameters calculated with this Anki release are not backwards compatible. If you use the mobile clients or review on AnkiWeb, avoid optimizing your FSRS parameters for now, or you won’t be able to review on those devices until your parameters are changed again.

3 Likes
232

Thanks, makes sense. Sucks for me (now can’t review on mobile unless I manually del FSRS params) but 100 % my own fault then. :slight_smile:

233

After deleting the last 2 parameters, it would be better if you also press Optimize to regenerate the parameters on mobile because some other parameters also have slight modifications.

234

You don’t need to manually delete the FSRS weights, just install version 24.06, reset the weights, and recalculate.

235

What do you mean by “reset the weights”—how would I do that? The only way of how to do this right now is by going to each of my ~50+ presets and manually deleting the FSRS weights. :eyes:

236

image

237

Man, I’m lowkey sad that the word “weights” is not going away…
It’s been ages since we changed it to “parameters”. Was it too little, too late? Was just a few months enough for it to stick?

238

I believe it is due to Google Translate (or ChatGPT).
My language is not English

1 Like
240

Nevermind, I can’t reproduce it consistently.
I noticed that if I select the FSRS parameters field, the message appears even if I don’t change parameters, but I can’t reproduce the message popping up without me selecting anything.

241

So here’s what I found so far

  1. Selecting the desired retention field without changing the number itself triggers the “Discard changes?” message
  2. Selecting the parameters field triggers the message
  3. Selecting the learning steps field does not trigger it
  4. “Evaluate” does not trigger it
  5. “Optimize” does not trigger it if parameters are already optimal
  6. Switching to “This deck” and then back to “Preset” does not trigger it
    image
  7. Enabling “Reschedule cards on change” and then disabling it does not trigger the message
  8. Changing Easy Days settings and then changing them back does not trigger it
  9. Selecting the custom scheduling field does not trigger it
  10. Selecting “Historical retention” does triger it

Only 1, 2 and 10 are not intended.
I’m using beta 3 btw.

242

For me simply opening the options and immediately closing it is enough to trigger it 100% of the time for all my decks. I’m running the qt6 version on Linux in the GNOME desktop environment. There is no verbose output in the terminal when I do this, so no clues there.

243

But now something interesting: I’ve previously built beta 2 myself with just one cherry-picked commit in it from beta 3 (the one that enables same day scheduling) and it doesn’t happen in that one. I just checked it.

244

And I’ve just built beta 3 myself and it happens consistently in that one. So one of the commits between beta 2 and beta 3 causes it.

245

The issue has likely been fixed in Fix 'Discard changes' dialog appearing even when no changes are made by hikaru-y ¡ Pull Request #3495 ¡ ankitects/anki ¡ GitHub. So, we are just waiting for the next beta.

1 Like
246

Perfect. I just found out that this commit causes it.

By the way, @dae, I know that I can in no way expect this from you, but if you can find the time to release an iOS beta along with the next desktop beta, that would really be appreciated.

247

An issue with the tags editor that was introduced with Anki 24.10 beta 3 (Windows 10). Seems to happen when switching between tags causes the tags bar to increase or decrease in height.

248

image
image1919×999 46.1 KB

I have removed my learning steps. How is it that hard has a longer interval than good?
Hard 5d while good 3d

249

The Forgetting curve in Card Info should indicate the rating that reset Retrievability to 100%.

250

From what I see in the video, it looks to me like that undesirable tag bar behavior is not a newly introduced issue in Beta 3, but a longstanding one that @dae mentions here and here. Or perhaps you are referring to a different issue?

the differing length of selections can cause the currently-displayed input to wrap/unwrap.