-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
improperly initialised realm after resetting storage to default location #26027
Comments
Another thing, if the default storage path already exists and contains a valid database, clicking the reset button here will create a new database and start from fresh. I think osu! should at least try to find and use an existing database if it exists |
Your logs don't seem to have anything about the error you encountered. I'd expect to see at least: Lines 115 to 116 in df5b389
They are also missing log headers. If possible could you please provide the full logs?
Could you please list other things?
It shouldn't, there's no logic to do that.. |
Tried again looks like logs end up in two places:
logs_custom_location.zip 2024-01-16_08-59-45.mp4.reenc.mp4
Yes, well
I'm not sure what led me to this conclusion, but I'm unable to reproduce this anymore. What I do remember is that at some point, my main installation's client.realm (at default storage location) was gone and I could not find any recent backup realm file |
Easiest solution is likely to restart the game. Probably dependent on #26558. |
Type
Game behaviour
Bug description
If osu!'s storage is set to a non-default location and that location either becomes inaccessible or gets deleted, the user is prompted with a dialog to reset to the default storage location. When the user presses the reset button, osu!'s storage is reset to its default location but legacy rulesets among other things are missing in the new realm.
Everything works again after a game restart.
Screenshots or videos
2023-12-21_23-19-05.mp4.reenc.mp4
Version
2023.1222.0
Logs
compressed-logs.zip
The text was updated successfully, but these errors were encountered: