Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

osu!lazer lack of sound in replay if using a specific audio offset #31340

Closed
supahero1 opened this issue Dec 29, 2024 · 0 comments
Closed

osu!lazer lack of sound in replay if using a specific audio offset #31340

supahero1 opened this issue Dec 29, 2024 · 0 comments

Comments

@supahero1
Copy link

Type

Game behaviour

Bug description

Basically: go in a map with autoplay or a replay so that you can move around the timeline. Then, near the beginning, use arrow left to rewind the playback. When beatmap audio offset is on, you can make lazer not play the beatmap music at all for the entire duration of the replay and afterwards. This is very easy to consistently replicate at higher speeds - that's why in the video I'm adding DT, after which you can see I'm able to invoke this behavior 4 times in a row whereas without DT I could only do it once in like 6 attempts. My global audio offset is 0.

For this map specifically, 7.4-7.5ms offset seems to be the magic offset (I tested these 2 values, something near them probably will work too). I could not replicate this behavior with any other randomly chosen offset with DT, nor any other map, and honestly I don't want to waste too much time trying.

Screenshots or videos

https://streamable.com/3jhx5i

Version

2024.1224.1-lazer

Logs

compressed-logs.zip

@supahero1 supahero1 changed the title osu!lazer lack of sound in replay if using beatmap audio offset osu!lazer lack of sound in replay if using a specific audio offset Dec 29, 2024
@ppy ppy locked and limited conversation to collaborators Dec 30, 2024
@bdach bdach converted this issue into discussion #31343 Dec 30, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant