You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
star rating was not updated and is stuck at 0 star
#38882
The star rating of 8718 maps could not be calculated and also does not update no matter what. As you can see in the attached screenshot the sorting is set to the range from 0.0 to 0.0 stars. With this setting osu can find and display the faulty beatmaps. if I increase it to 0.1 to 0.2 stars the maps get hidden. Osu thinks they are all 0 stars. There is no way to process all beatmaps manually like in the old client nor does it update them at any point. I also tried to delete the client.realm file but this also does not force osu to process the maps again. Is there any way to fix this issue? The reason for this could be that I switched from Windows 10 to Linux recently. But I am not 100% sure if this issue also existed under Windows. Logs are attached below. logs.zip
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
The star rating of 8718 maps could not be calculated and also does not update no matter what. As you can see in the attached screenshot the sorting is set to the range from 0.0 to 0.0 stars. With this setting osu can find and display the faulty beatmaps. if I increase it to 0.1 to 0.2 stars the maps get hidden. Osu thinks they are all 0 stars. There is no way to process all beatmaps manually like in the old client nor does it update them at any point. I also tried to delete the client.realm file but this also does not force osu to process the maps again. Is there any way to fix this issue? The reason for this could be that I switched from Windows 10 to Linux recently. But I am not 100% sure if this issue also existed under Windows. Logs are attached below.
logs.zip
All reactions