Combo, score and rank inconsistent between score screens

[QmelZ]

Type

Game behaviour

Bug description

In a replay of me playing this map, the statistics seem to change randomly depending on when the score screen is shown.

Screenshots or videos

first screenshot after the actual play (my perspective), 1 miss and 295 combo:

screenshot from friend's perspective, before watching replay (A rank):

screenshot after the replay is watched (both perspectives), 0 misses and 483 combo:

screenshot from the score page:

replay

Version

2022.1228.0

Logs

runtime.log
network.log
performance.log
input.log
database.log

[peppy]

@smoogipoo is this one similar to the other recent issues that you may have already fixed / visited?

[skybldev]

i am the friend, and fyi resolution change was just so i can take area screenshot (GNOME unfocuses fullscreen applications when taking area screenshot)

[QmelZ]

it happened again
here's the replay
here's the map

and here's the images:

after i finished the map:

after i finished watching the replay:

and the logs:
runtime.log
network.log
database.log
performance.log
input.log

[nuenweh]

I'm also experiencing this issue, it's really annoying.

[Polyva]

This issue is also present for me in osu!catch with basically every replay. None of them match with my actual score after watching them.

Example:

images and replay

after setting the score

after watching the replay

Replay:
LazerUtaReplay.zip

logs

runtime.log
updater.log
network.log
performance.log
performance-audio.log
performance-draw.log
performance-input.log
input.log
legacy-ipc.log
database.log
performance-update.log

[VictorDelattre]

I got an issue similar to this one but with a 5x score gap between my old score and my new one (even though my new one is better).
I don't know if it's exactly the same issue but I am posting it here so you can judge by yourselves.

images and replays

Scores before watching the replay:

New score

Previous score

Both scores

Scores after watching the replay:

New score

Previous score

Replays

replays.zip

logs

performance-audio.log

performance-draw.log

performance-input.log

performance-update.log

runtime.log

updater.log

database.log

network.log

performance.log

[peppy]

This thread has changed from being about users seeing different things in multiplayer to being about replay playback accuracy. I'm not sure what to do here to be honest.

[smoogipoo]

@VictorDelattre What you're seeing is the effect of lazer's new scoring, which you can find info on in the lazer updates video: https://www.youtube.com/watch?v=iV6IdUcwHLY

The conversion of old lazer scores to the new scoring is not going to be supported.

[skybldev]

I want to make it clear that this was never about multiplayer, it was always about score accuracy (nd really what is the right score anyway?). To clarify, the original post contains OP's perspective before and after a local play, and my perspective after he sent me the replay for it. Jun 6, 2023 01:29:17 Dean Herbert ***@***.***>:

…

This thread has changed from being about users seeing different things in multiplayer to being about replay playback accuracy. I'm not sure what to do here to be honest. — Reply to this email directly, view it on GitHub[#22267 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AHGKLWLJT5IASC6B34ANY3TXJ252TANCNFSM6AAAAAAT6MQQCY]. You are receiving this because you commented.[Tracking image][https://github.com/notifications/beacon/AHGKLWMIBBVSJF74ZJCGRXLXJ252TA5CNFSM6AAAAAAT6MQQC2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS6BVMEG.gif]

[VictorDelattre]

@smoogipoo Thank you for sharing this information, I wasn't aware of this update.

While reflecting on my previous post, the section discussing the large gap between my scores is no longer relevant due to the update you mentioned. However, it is worth noting that I am still encountering the issue mentioned in the original post, as evidenced by the slight difference in my "new" local score compared to the score after the replay.

[monochrome22]

The issue in the original post looks like another case of playback not working correctly.
There's multiple issues of the same thing:
#19738
#19766
#21659
#23709

Are they all caused by different things?