Existing objects get un-hitsound-able after saving the beatmap

[rvneXe]

Type

Game behaviour

Bug description

Hello. Self-explanatory video:

2024-08-18_22-55-02.mp4

Files:

Screenshots or videos

No response

Version

2024.817.0

Logs

compressed-logs.zip

[rvneXe]

I could do a temporary fix by importing it into stable, and setting all timing points sample on Normal Custom1 (was Normal default)

[kstefanowicz]

See #29028 - PR #29311 is attempting to fix

[bdach]

@kstefanowicz how are you claiming this exactly? The issues don't seem related.

[rvneXe]

@kstefanowicz how are you claiming this exactly? The issues don't seem related.

I feel it does, since both of them fix by switching timing points to Custom via stable editor.

[rvneXe]

But the way that it plays the hitsound for newly placed objects, then it disappears after saving/reloading seems like a seperate thing.

[kstefanowicz]

@bdach the behavior in this issue's video is consistent with the behavior investigated in #29028.

The editor plays the correct custom hitsound after placing the hit object, but when saving/testing the legacy encoder writes the song's timing points to the .osu file with CSS 0. This causes the hit objects to revert back to default/skin's hitsounds.

@aL1NaZ4R you can work around this currently by manually changing the CSS values in the .osu file from 0 to 1:

[rvneXe]

Umm. Looks like you're right. my bad