First carousel load doesn't sort beatmaps with the user's choice
See original GitHub issueDescribe the bug: In my case, the carousel should sort by Title
, but it seems to sort by Artist
.
Also, looks like this issue happens when entering Solo right after starting the game (but I can’t be precise on this).
Screenshots or videos showing encountered issue: Video
osu!lazer version: 2020.629.0
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
osu!(lazer) updates (@osu_lazer) / X
a PR has been opened to implement the new "beatmap carousel" design, which is the first step of many towards the new beatmap...
Read more >Untitled
Divya bharti telugu songs hd 1080p, List disk v2 6 zipper, Recopilatorios 2013 descargar musica, Tomahawk wisconsin zip, That's my kind of night...
Read more >Untitled
#and Karaoke nhac song bai bac trang tinh doi, How to sort books in kindle collection! ... Minecraft trolling first person troller intro,...
Read more >Untitled
#stars Cant connect to wifi first media, How to follow up application after ... Young living indonesia price list, Excel macro selection custom...
Read more >Lazer 2022.723.0 · changelog - Osu!
This will nuke all local beatmaps' difficulties once. Seems like a good move to get everything in a consistent state. This will also...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Interesting to note that when this issue happens, the carousel doesn’t hide incompatible rulesets. As you can see, the selected ruleset is osu!, but the carousel also shows taiko/mania beatmaps in this screenshot:
I’d also appreciate runtime.log when this occurs.