Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Beatmaps star ratings recalculating every launch #30494

Closed
shrublet opened this issue Nov 4, 2024 · 5 comments
Closed

Beatmaps star ratings recalculating every launch #30494

shrublet opened this issue Nov 4, 2024 · 5 comments
Labels
missing details Can't move forward without more details from the reporter realm deals with local realm database

Comments

@shrublet
Copy link

shrublet commented Nov 4, 2024

Type

Game behaviour

Bug description

Game requires the same set of beatmaps to be recalculated every launch, degrading performance until it's done. I believe these maps all previously had local diffs that I've since deleted and were previously labeled local. Let me know anything additional I should attach.

Screenshots or videos

No response

Version

2024.1009.01

Logs

compressed-logs.zip

@bdach
Copy link
Collaborator

bdach commented Nov 4, 2024

Please attach client.realm from game files.

@bdach bdach added missing details Can't move forward without more details from the reporter realm deals with local realm database labels Nov 4, 2024
@shrublet
Copy link
Author

shrublet commented Nov 8, 2024

Sorry, late reply. Drive link since it's pretty large - https://drive.google.com/file/d/19YHCAI7HCefZ402rzRrBYHY8d4XC7jcm/view

@bdach
Copy link
Collaborator

bdach commented Nov 8, 2024

I'm not sure how this happened, but this database looks corrupted.

There are several BeatmapInfo objects with star rating missing:

1731066193

These would presumably be some sort of practice difficulties, I guess. The rows with null beatmap set are weird but ultimately not that interesting; what is more worrying is the rows where the beatmap set is present. Examining any one of them by going back to the beatmap set, and then examining the set of backlinks from beatmaps yields this:

1731066255

Or, in other words, the beatmap set object is reachable from the beatmap objects, but the beatmap objects are not reachable from the beatmap set object. That's not how foreign key relationships are supposed to ever work. Not sure what the remediation steps are.

@shrublet You can try replacing your client.realm with https://drive.google.com/file/d/1ahYwQ2KPb75Z118hNFLWNj55I92zgzkG/view?usp=drive_link to fix this (probably back up your existing one before, to make sure I haven't screwed up anything too bad when manually fixing). You might lose some difficulties though.

@shrublet
Copy link
Author

shrublet commented Nov 9, 2024

Thank you! This fixed it. I'm really not sure what happened to my db, but I had previous issues with the same install #24301 (since migrated a few times) idk if it's related at all. The only info I can give which you've already gleaned is that all the sets previously had local diffs which I had since deleted before the recent sr reprocessing iirc. I believe a lot of the diffs were imported from stable and then deleted in lazer, if that helps at all. Hope this info could be of use, else can just close this issue as a non-issue.

@bdach
Copy link
Collaborator

bdach commented Nov 11, 2024

I'll just tentatively close this as a one-off and hope I never see anything like this again...

@bdach bdach closed this as not planned Won't fix, can't repro, duplicate, stale Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
missing details Can't move forward without more details from the reporter realm deals with local realm database
Projects
None yet
Development

No branches or pull requests

2 participants