"played=0" filter resets difficulty range after playing beatmap

[adriankiezik]

Type

Game behaviour

Bug description

Steps to reproduce:

1. Enter "played=0" filter
2. Select any difficulty range
3. Play a beatmap (you can exit it right away)
4. All difficulties are shown disregarding selected range (only for current beatmap)

Screenshots or videos

Version

2024.906.1-lazer

Logs

logs.zip

[m1ntleaf]

please submit logs. it takes literally 5 seconds

[peppy]

I can't reproduce this.

[Joehuu]

Still seems to happen on latest release. Can seem to reproduce on a fresh database with recommended maps (clean-install), but not on my 200+MB database.

[adriankiezik]

@peppy Included logs & video with issue occurring on latest ver.

video.mp4

[bdach]

I'm not sure the video above is showing what it's claiming. I believe what is happening could be considered a little unintuitive, though.

Before I elaborate, the symptoms that I am seeing is as follows:

1. I set a difficulty range filter via the slider
2. I set a text played=0 filter
3. I enter any map and exit out immediately after player loads
4. I see that the mapset I was playing has the filter unset for it, but all other mapsets are still correctly filtered to unplayed and within the difficulty range set

In other words, the "difficulty range reset" only happens in the context of the single mapset that has just been played.

If that is what everyone is seeing (@adriankiezik @Joehuu can you confirm for me?), then that is somewhat "intended," because song select will forcibly bypass filters when exiting out of player, in order to preserve the selected beatmap:

osu/osu.Game/Screens/Select/SongSelect.cs

Lines 524 to 529 in b5afca9

	// Even if a ruleset mismatch was not the cause (ie. a text filter is applied),
	// we still want to temporarily show the new beatmap, bypassing filters.
	// This will be undone the next time the user changes the filter.
	var criteria = FilterControl.CreateCriteria();
	criteria.SelectedBeatmapSet = beatmap.BeatmapInfo.BeatmapSet;
	Carousel.Filter(criteria);

A big portion of this is the played=0 filter which is the reason why just entering the beatmap triggers this pathway.

It could potentially be changed, at the expense of the current track forcibly changing when exiting gameplay, which I'm not sure how to feel about.

[peppy]

It could potentially be changed, at the expense of the current track forcibly changing when exiting gameplay, which I'm not sure how to feel about.

That's not what we want. It should disappear when selection changes, though, I guess.

[Joehuu]

This is what I see.

On fresh database with recommended beatmaps (same behavior as OP):

osu._OpTX1kxjmV.mp4

On a 200+MB database:

osu._FzfXHlvKBG.mp4

The 200+MB database video seems to be the desired behavior for OP, but it looks broken? Either way there is some kind of race condition.