We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Danser thought I failed in the replay but when I use osu! to view the replay it's a pass.
Files replay output
Logs danser.log
Computer configuration: Operating System: EndeavourOS x86_64 (kernel: 5.19.12-arch1-1) CPU: Intel(R) Core(TM) i5-4210U GPU: Mesa Intel(R) HD Graphics 4400 (HSW GT2) Sound Card: I'm not sure
The text was updated successfully, but these errors were encountered:
I don't think I can fix that one. After analyzing replay data it should be a fail, even in osu.
If we look at this screenshot:
in osu, actually you get hit50:
But for some reason osu! decides to change it to hit300 because that bar disappears almost instantly.
Sorry, something went wrong.
Left was an osu! replay bug that seems to be fixed in newest cuttingedge, but it turned out issue also lies on danser's side.
It's not yet pushed to dev branch but it appears to be fixed:
Successfully merging a pull request may close this issue.
Describe the bug
Danser thought I failed in the replay but when I use osu! to view the replay it's a pass.
Files
replay
output
Logs
danser.log
Computer configuration:
Operating System: EndeavourOS x86_64 (kernel: 5.19.12-arch1-1)
CPU: Intel(R) Core(TM) i5-4210U
GPU: Mesa Intel(R) HD Graphics 4400 (HSW GT2)
Sound Card: I'm not sure
The text was updated successfully, but these errors were encountered: