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

Missing hitsounds in Editor in some 300BPM beatmaps #26366

Closed
FukutoTojido opened this issue Jan 3, 2024 · 3 comments
Closed

Missing hitsounds in Editor in some 300BPM beatmaps #26366

FukutoTojido opened this issue Jan 3, 2024 · 3 comments
Labels
area:editor priority:1 Very important. Feels bad without fix. Affects the majority of users.

Comments

@FukutoTojido
Copy link

Type

Game behaviour

Bug description

I noticed that hitsounds in some 300BPM beatmaps will not play normally. Some will play, some will not.

Screenshots or videos

bug2.mp4

Beatmap used in video: VINXIS - Sidetracked Day GAMMA [300]

2024-01-03.21-14-15.mp4

Beatmap used in video Noah - Deadly force - Put an end [The end.]

2024-01-03.21-17-07.mp4

Beatmap used in video: Camellia - Flamewall [ETERNAL SACRED FIRE]

Version

2023.1231.0-lazer

Logs

compressed-logs.zip

@peppy
Copy link
Member

peppy commented Jan 3, 2024

Age old issue of editor not running in a frame stable mode.

@peppy peppy added area:editor priority:1 Very important. Feels bad without fix. Affects the majority of users. labels Jan 3, 2024
@peppy
Copy link
Member

peppy commented Jan 4, 2024

So, a few things:

Yes, this is fixed by frame stability, but only because frame stability allows replay frames to exist in a non-linear time scale. As in there are frames in the past, and frame stability will rewind to handle them correctly.

The base issue is that hitobjects are closer than 50 ms in these beatmaps, but auto generator adds a 50 ms minimum window for key-down-to-key-up:

double hEndTime = h.GetEndTime() + KEY_UP_DELAY;

I'd argue that this should be solved by fixing the auto generator to infer the next object and not hold for as long, or just reducing the key down period altogether to a value which will not cause issues like this.

Side note that DelayedMovements in autogenerator is currently never used and a dead code path...

This is a duplicate of #22353.

@peppy
Copy link
Member

peppy commented Jan 4, 2024

As this is a duplicate (and side effect of the larger issue), I'll close this in favour of #22353.

@peppy peppy closed this as not planned Won't fix, can't repro, duplicate, stale Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:editor priority:1 Very important. Feels bad without fix. Affects the majority of users.
Projects
None yet
Development

No branches or pull requests

2 participants