You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, there are two empty sounds in OpenSFX: osfx_34.wav (SND_22_CAR_HORN) and osfx_50.wav (SND_32_POP_2).
Those sounds are not used in OpenTTD so far (1.10.0), according to looking at the source code. (Here's an overview btw: https://wiki.openttd.org/en/Development/SoundIDs). So it is currently perfectly OK that both sounds are empty.
But would it make sense to create sound files for those two, just in case that support for OpenTTD is added later? It seems like the first one is meant for a car horn, and the second one is meant for an 'alternative' bubble pop sound for the Toyland bubble generator.
You're sidestepping the issue. This is not about neccessarily inventing new sounds. It's about sound IDs that are OFFICIALLY defined in OpenTTD, but are currently unused for some reason. I also still have not gotten an answer on the other issue whether these sounds are really meant to be unused or if it's a bug/oversignt.
If these sound IDs are intentionally unused, then this issue is moot, and can be closed.
But if these sound IDs were meant to be actually used officially, just haven't been implemented for some reason, then I think this issue is valid.
Currently, there are two empty sounds in OpenSFX:
osfx_34.wav
(SND_22_CAR_HORN
) andosfx_50.wav
(SND_32_POP_2
).Those sounds are not used in OpenTTD so far (1.10.0), according to looking at the source code. (Here's an overview btw: https://wiki.openttd.org/en/Development/SoundIDs). So it is currently perfectly OK that both sounds are empty.
But would it make sense to create sound files for those two, just in case that support for OpenTTD is added later? It seems like the first one is meant for a car horn, and the second one is meant for an 'alternative' bubble pop sound for the Toyland bubble generator.
See also: OpenTTD/OpenTTD#8619
The text was updated successfully, but these errors were encountered: