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

Pausing gameplay can cause phantom misses #26442

Closed
Locas1000 opened this issue Jan 9, 2024 · 4 comments · Fixed by #26605
Closed

Pausing gameplay can cause phantom misses #26442

Locas1000 opened this issue Jan 9, 2024 · 4 comments · Fixed by #26605
Labels
area:gameplay priority:1 Very important. Feels bad without fix. Affects the majority of users.

Comments

@Locas1000
Copy link

Type

Crash to desktop

Bug description

I paused on top of a slider and when I unpaused it counted as a miss but the combo score didn't change. The replay shows a miss but the end screen says the total combo

Screenshots or videos

https://clipchamp.com/watch/IOwL5sv38f7

Version

2023.1231.0-lazer

Logs

compressed-logs.zip

@peppy
Copy link
Member

peppy commented Jan 15, 2024

This is going to be due to the rewind happening when pausing/unpausing. We might just want to completely disable that (and the frequency ramp which is the reason for it existing) until things are in a better place.

@frenzibyte
Copy link
Member

I cannot seem to reproduce this one at all, not sure what I'm missing.

@peppy
Copy link
Member

peppy commented Jan 15, 2024

Try adjusting platform offset to something very high (and also not zero, which is what you have due to macOS). It will be related. I think universal offset may also work.

If that still doesn't work, try increasing the ramp time

this.TransformBindableTo(GameplayClock.ExternalPauseFrequencyAdjust, 0, 200, Easing.Out).OnComplete(_ =>
to absurd levels. It should cause gameplay to skip back on resume.

@frenzibyte
Copy link
Member

I still cannot reproduce. I also noticed the following code snippet in OffsetCreationClock:

private void updateOffset()
{
// changing this during the pause transform effect will cause a potentially large offset to be suddenly applied as we approach zero rate.
if (pauseRateAdjust.Value == 1)
{
// we always want to apply the same real-time offset, so it should be adjusted by the difference in playback rate (from realtime) to achieve this.
base.Offset = Offset * Rate;
}
}

Suggesting that the pause frequency adjustment should not affect clock time (when using offset != 0).

@peppy peppy changed the title after pausing automatic miss that did not count Pausing gameplay can cause phantom misses Jan 17, 2024
@peppy peppy added the priority:1 Very important. Feels bad without fix. Affects the majority of users. label Jan 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:gameplay priority:1 Very important. Feels bad without fix. Affects the majority of users.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants