bm_c1a3a missing sound issue

Black Mesa Archive In-game Issues
#1

What sound exaclty is missing:

Start chapter 5 “We’ve Got Hostiles” (or the map bm_c1a3a), proceed to the scientist who starts saying “open the silo doors” and wait until the guard inside the room gets grabbed by a zombie who pulls him into the vent.
The guard is supposed to make some choking sounds but in my case he doesn’t. In the console I get the following warning/error message:
Failed to load sound “*vo\c1a3a\silodoors\grd_zombiegrabscream.wav”, file probably missing from disk/repository
The actual path to that sound file is vo\c1a3a\grd_wgh_zombiegrabscream01.wav

I’ve removed the entire game, deleted the game directory manually, and re-downloaded the whole game again (“stable” branch, not beta or something else). I have no workshop addons installed, no manual mods or any special custom config file or something like that. The issue persists.
According to a discussion on Steam this issue is supposed to be specific to my system, but is it really?

Something else I want to mention is that the only “zombiegrabscream” file listed inside bm_c1a3a.manifest is the missing file mentioned in the console log.

Well, I know how to add custom stuff to the game’s search path, so I can easily fix that for me, but I still wanted to let you know that. I’d also like to know if I’m really the only person experiencing this tiny bug.

#2

If it is something sticky like Steam Cloud related, you might need to nuke it from orbit.

Check out this dreck I posted on steam that supposedly helped someone

"Verify that the steam cloud is turned off.

Use a file search tool like voidtools.com “everything”, the non installed portable app (zip version) works fine.
Uninstall Black Mesa
Restart your computer
Exit Steam
Search for all the config, autoexec etc files that are related to black mesa and delete them.
Search for the App ID 362890 and delete everything."

https://steamcommunity.com/app/362890/discussions/0/2860219962087801364/

#3

Deactivated Steam cloud in Steam settings. Used “Everything” to search for the app ID and deleted stuff. Made a clean reinstall of Black Mesa. Still doesn’t want to play that sound file, weird.
Here the log:

] map bm_c1a3a Saving D:\SteamLibrary\steamapps\common\Black Mesa\bms\bms_sounds_misc.vpk.sound.cache Dropped djcj from server (Disconnect by user.) Unknown command "sk_plr_crossbow_speed" SV_StartSound: npc/alien_slave/vort_attack_shoot1.wav not precached (0) SV_StartSound: npc/alien_slave/vort_attack_shoot2.wav not precached (0) SV_StartSound: npc/alien_slave/vort_attack_shoot3.wav not precached (0) SV_StartSound: npc/alien_slave/vort_attack_shoot4.wav not precached (0) SV_StartSound: npc/vort/attack_charge.wav not precached (0) SV_StartSound: npc/alien_slave/vort_attack_shoot1.wav not precached (0) SV_StartSound: npc/alien_slave/vort_attack_shoot2.wav not precached (0) SV_StartSound: npc/alien_slave/vort_attack_shoot3.wav not precached (0) SV_StartSound: npc/alien_slave/vort_attack_shoot4.wav not precached (0) SV_StartSound: npc/vort/attack_charge.wav not precached (0) Attempted to create unknown entity type Default! NULL Ent in UTIL_PrecacheOther Compact freed 2506752 bytes Redownloading all lightmaps Failed to load sound "*vo\c1a3a\silodoors\grd_zombiegrabscream.wav", file probably missing from disk/repository

Update:

I think I found the issue:
In the bms_misc VPK file, there’s this entry in scripts/game_sounds_scenes.txt:

[code]“ss_open_silo_doors.ZombieGrabScream”
{
“channel” “CHAN_BODY”
“volume” “VOL_NORM”
“pitch” “PITCH_NORM”
“soundlevel” “SNDLVL_NORM”
“wave” “*vo/c1a3a/SiloDoors/GRD_zombiegrabscream.wav”

}[/code]
That’s the path my game is looking for which doesn’t exist.

Update 2:

Changing the part in scripts/game_sounds_scenes.txt like this fixes the issue:

[code]“ss_open_silo_doors.ZombieGrabScream”
{
“channel” “CHAN_BODY”
“volume” “VOL_NORM”
“pitch” “PITCH_NORM”
“soundlevel” “SNDLVL_NORM”
//“wave” “*vo/c1a3a/SiloDoors/GRD_zombiegrabscream.wav”
“wave” “vo/c1a3a/grd_wgh_zombiegrabscream01.wav”

}[/code]So now I’m 100% sure it’s not an issue with my PC or setup but an issue with the game, as it’s clearly looking for a file that doesn’t exist.

#4

I am at work right now and cant check my own setup. Is there anyone else that sees the missing directory as well?

#5

Hey guys, debeerguy here, and I’ve looked into this on the build sources, and have found out what the deal is:

The sound was originally implemented as a soundevent in the qc file that complies one of the animation models. It refers to the so called soundscript “ss_open_silo_doors.ZombieGrabScream”, originally found in scripts/game_sounds_scenes.txt

Source Code[/size]

  1. “ss_open_silo_doors.ZombieGrabScream”
  2. {
  3. “channel” “CHAN_BODY”
  4. “volume” “VOL_NORM”
  5. “pitch” “PITCH_NORM”
  6. “soundlevel” “SNDLVL_NORM”
  7. “wave” “*vo/c1a3a/SiloDoors/GRD_zombiegrabscream.wav”
  8. }

When I did the whole “vo soundscript conversion initiative” a few years back, I moved and renamed this soundscript to
wgh.grdroom.zombiegrabdeath01 ( game_sounds_scenes_wgh.txt ), to be used in the scene’s .vcd file instead.

(this is the soundscript as now intended)

“wgh.grdroom.zombiegrabdeath01”
{
“channel”“CHAN_VOICE”
“volume”“0.600”
“pitch”“PITCH_NORM”

“soundlevel” “SNDLVL_NORM”

“wave”“vo/c1a3a/grd_wgh_zombiegrabscream01.wav”
}

So basically a new soundscript was made, new name given for the .wav file, and I simplified the wav directory. (vo/c1a3a/SiloDoors/ no longer exists. )

The guard’s screaming sound still plays as intended (now thru the actual .vcd file) but we forgot to remove the original soundevent reference in the animation qc, and that’s part of why the console error exists.

Hope that helps to explain the situation.

I appreciate you guys being that to our attention. While it doesn’t affect the gameplay of that scene, I’ll be sure to get the console error taken care of on our end.

Simple solution to ridding yourself of the console error (assuming it irks you enough lol) is to just delete the entry
“ss_open_silo_doors.ZombieGrabScream” from game_sounds_scenes.txt

#6

Since I don’t get that warning, what should i do. ?(

Reminds me of the pilot who tells the ground crew that Propeller #2 is seeping prop fluid.
They respond that Propeller #2 seepage is normal -

Pilot replies that #1, #3 and #4 propellers lack normal seepage. :smiley:

#7

@RedEye

In this particular case, it’s nothing to worry about :slight_smile:

#8

And that’s weird, cause for me the guard is only screaming when I change the .txt files. Whatever, it’s a very minor thing and I would have never even realized it if I didn’t pay attention to the console log.
Thanks for your replys, devs now know about it, my job is done. :wink:

#9

Someone get this guy a beer :smiley:

Founded in 2004, Leakfree.org became one of the first online communities dedicated to Valve’s Source engine development. It is more famously known for the formation of Black Mesa: Source under the 'Leakfree Modification Team' handle in September 2004.