It makes sense, but it’s very confusing. Maybe there a warning should appear when there is deck:current (and the current deck is different, if the window could track that in real time).
I have submitted a PR to fix two bugs just now:
4 Likes
rc2 is now available: Releases · ankitects/anki · GitHub
Please let us know how you go. If no major issues are found, a stable release is expected in a couple of days.
8 Likes
WOOOOOOW
THANK YOU the MAIN ANKI WIZARD, appreciate it!
1 Like
You should be thanking everyone who’s contributed to this release 
8 Likes
I usually use “deck:current -is:suspended” to test the parameters, but “Enhance main window” shifts the gear button far from the deck name by default, necessitating scrolling, and the hover highlighting is as grey as the current deck one.
I wonder what happens if I Optimize All Presets with a “deck:current” in a query.
The deck selector in Stats can’t choose or indicate filtered decks.
I think I may be still experiencing the issue regarding retrievability.
This card displays a retrievability of 40%, but was shown before cards with retrievability 70% when sorting by Descending retrievability. If I check the Retrievability column of the Browser, it shows a value of 70%.
I haven’t had a close look at what L.M.Sherlock tried to do in the fix for this issue.
But, IMO, the only possible “fix” is to calculate the R in the card info using the same hack which is used in other places, instead of calculating it accurately.
Please send me your collection, I need to reproduce this problem to fix it.
2024-11-22 minus 2.74 months is 2024-09-01. But the actual last review date is 2023-09-09. That’s the problem.
Due to the performance issue, the retrievability displayed in browser column is inferred from due and interval of card instead of the last review date queried from the review logs which is used to calculate the retrievability displayed in card info.
I can do nothing here because the due and interval could be changed by other operation that I don’t know.
1 Like
Hi all,
24.11 has now been released as stable. If you encounter any issues, please let us know in a separate thread.
An AnkiMobile update will hopefully be approved by Apple in about 24 hours.
9 Likes
I’ve tested 24.11/FSRS 5 and I’ve noticed one thing, I’ve left learning and relearning steps empty; as mentioned that FSRS can handle it, but I encountered 1 issue? Not sure if intended or not, but basically I had a relearning card I clicked on “Again” and it just loops to “Again”, “Hard” and “Good” all(<11.1 hours) intervals, while only “Easy” is (2d) interval, even if I click “Good”(<11.1 hours) with it, well, it just becomes infinite and shows up with the same interval(<11.1 hours), I’ve got a learn ahead limit of 999 mins so that’s not the issue. Is this working as intended? Reviews literally don’t end and just loop the same interval.
Yes, “Easy” (2d) interval is an option, but I only use “Again” and “Good”, is this an issue?
Didn’t encounter it yet with learning steps, but I’m assuming the same scenario is possible.
Its set to 999 mins. So I see, so there’s no way around it? The way it works before is even if it shows something like that (<11.1h), if you pass it, it will just go to its next interval instead of becoming an infinite loop, if the feature is intended I guess I’ll just change my learn ahead limit
There’s a way around it – reduce your learn ahead limit! That’s what is causing it. FSRS is obediently rescheduling the card for 11h from now, and then your learn-ahead limit is looking ahead 16.65 hours and pulling those cards forward. (A 999m learn-ahead seems to defeat the point of having steps at all …)
Unless these FSRS updates changed something about the learn ahead limit (L.M.Sherlock, did you?), it should be working the same as it did when you had learning/relearning steps – and the same as it did under SM-2. However, if you study the card later in the day, that 11h interval should still follow day-boundary rules and the card will be pushed to tomorrow. (No changes there either, right, L.M.Sherlock?)
1 Like
When I right click in browser, error message pops up.
Anki 24.11 (87ccd24e)
Python 3.9.18 Qt 5.15.2 PyQt 5.15.5
Platform: Windows-10-10.0.19045
Traceback (most recent call last):
File “aqt.editor”, line 1631, in contextMenuEvent
File “aqt.editor”, line 1471, in _opened_context_menu_on_image
AttributeError: ‘EditorWebView’ object has no attribute ‘lastContextMenuRequest’
Shift + Anki start is not solution…
1 Like
Should I be able to download version 24.11 here? Because it’s still showing 24.06 for me.
