Troubleshooting and fixing your game!

Greetings scientists!

This guide regroups issues and possible fixes that are known by the community.

If your issue is not there or the fix does not work, please make sure you take a peek at this thread.

1. It is updated to the latest version of the game.
   
2. You unsubscribe from all mods, delete their respective files*, and verify the integrity of games files

Alternatively, use the game launch command +workshop_disable 1 to quickly disable every and all Workshop mods for Black Mesa.

Finally, please move out or remove your "custom" folder (if any) in Common/Black Mesa/bms to completely prevent any custom content from loading. Verify the integrity of game files before launching the game again.

For gamepad related issues and questions, see this guide below.

https://steamcommunity.com/sharedfiles/filedetails/?id=2610891144

Any time a virus protection tool picks up a threat, people panic, usually fairly so. There are times, however, where false positives happen. This is the case with Black Mesa. There is absolutely no reason for the developers to push updates that contain malware given their respectable reputation.

If you get a threat alert from your virus protection tool, be sure to report it to the developers on the forums or on Discord, so that they can work this out with the companies than run those software.

• Wait until this issue is fixed, if you so much as do not trust the file to be safe.
  
• Whitelist the files that are considered to be false positives.

1. Search for "Event Viewer" in your Windows search bar.
   
2. In the side navigation bar, go to Windows Logs > Application Logs.
   
3. Find the error caused by bms.exe. It should be a red circle with an exclamation mark and be the most recent if you just tested trying to open bms.exe and failed.
   
4. Check the text box labeled general to see if the log is about bms.exe.
   
5. When you find the correct log, copy the general text box and paste it into the ticket.

Credits to Just Chill for providing all the following information. See the original discussion here.

Originally posted by Just Chill:

If you play the beta or you got suddenly surprised by the official Definitive Edition update, you will have issues with your save game after every update.
That was like that, when I joined the beta for Xen and it will be like that in any other update either, which contains map changes.
Simply because your save game contains data that isn't relevant anymore and rather is outdated.
The Source engine detects that and will prompt you an error.

There is a post from 2013 about Half-Life 2 having an update, which made saves invalid:
https://github.com/ValveSoftware/Source-1-Games/issues/722

Crowbar Collective uses the Source engine too and they cannot rewrite its core.

So yeah, it's annoying but that's how Valve's engine works obviously.

If you want to continue

testing / playing the game from a specific point nearby your last save game, you simply may use the "map" command in console, with the respective map name. Example:

map bm_c4a4a

Which will load up the Nihilanth boss fight. Earth-bound levels:

Originally posted by SourceRuns.org/Wiki:

Black Mesa Inbound

bm_c0a0a
bm_c0a0b
bm_c0a0c

Anomalous Materials

bm_c1a0a
bm_c1a0b

Unforeseen Consequences

bm_c1a1a
bm_c1a1b
bm_c1a1c
bm_c1a1d
bm_c1a1e

Office Complex

bm_c1a2a
bm_c1a2b
bm_c1a2c

We've Got Hostiles

bm_c1a3a
bm_c1a3b
bm_c1a3c

Blast Pit

bm_c1a4a
bm_c1a4b
bm_c1a4c
bm_c1a4d
bm_c1a4e

Power Up

bm_c2a1a
bm_c2a1b

On a Rail

bm_c2a2a
bm_c2a2b
bm_c2a2c

Apprehension

bm_c2a3a
bm_c2a3b

Residue Processing

bm_c2a4a
bm_c2a4b
bm_c2a4c
bm_c2a4d

Questionable Ethics

bm_c2a4e
bm_c2a4f
bm_c2a4g
bm_c2a4h

Surface Tension

bm_c2a5a
bm_c2a4b
bm_c2a5c
bm_c2a5d
bm_c2a5e
bm_c2a5f
bm_c2a5g

Forget About Freeman

bm_c3a1a
bm_c3a1b

Lambda Core

bm_c3a2a
bm_c3a2b
bm_c3a2c
bm_c3a2d
bm_c3a2e
bm_c3a2f
bm_c3a2g
bm_c3a2h

Borderworld levels, collected by myself:

Lambda Core - Teleporter

bm_c3a2i

Xen

Arrival:
bm_c4a1a

Grotto before laboratory:
bm_c4a1a1

Laboratory before explosive plant section:
bm_c4a1b

Shortly before the big tree area, where 3 rooms have to be solved to open up the path:
bm_c4a1b1

Open alley before jumping down a big hole and encountering ground barnacles for the first time:
bm_c4a1c

The houndeye bridge:
bm_c4a1c1

Gonarch

Arrival:
bm_c4a2a

Area after following Gonarch and jumping down (area where you need to blow the wall with a detonator):
bm_c4a2b

Area where Gonarch destroys a wall with her green goo attack (I got stuck there once in beta ^^):
bm_c4a2c

Interloper

Arrival:
bm_c4a3a

After first controller fight, in the canyon:
bm_c4a3a1

When encountering the grates that need to get molten by green acid:
bm_c4a3b

Another cave with green acid riddles:
bm_c4a3b1

Shortly before arriving at the factory entrance, where the first jumping Alien Grunts spawn:
bm_c4a3b2

Before starting the assembly line riddle:
bm_c4a3c

Assembly line riddle, before controller ambush:
bm_c4a3c1

Assembly line riddle, before going up the flesh trampolines:
bm_c4a3c2

Second waste disposal area, shortly before starting the elevator section:
bm_c4a3d

At the end of the elevator sequence shortly before teleporter to Nihilanth:
bm_c4a3d1

Nihilanth

Arrival:
bm_c4a4a

End Game

Kaboooooooooooooooooooooooom:
bm_c4a5a

Credits

credits

In addition:

Oh, thanks for pinning. :)

In addition to the "map"-command, there are either some things that might be worth mentioning, about having a "naked" Gordon, after using the map command to load a specific map:

Originally posted by Just Chill:

Ah, I feared that this might happen.
You need to get the HEV suit and probably even the longjump module + weapons.

To do so, you have to type these things after you loaded the map:

sv_cheats 1

give item_suit

give item_longjump

(use longjump cheat only for Lambda Core - Teleporter and Xen)

impulse 101

give item_suitcharger

Just to be sure: If you play earthbound before the Xen teleporter, do NOT use the long jump cheat. As you are not supposed to have that module before you enter the Lambda Core teleporter room.

You surely can use it in earthbound levels too, but be sure that any issue you'll encounter by using the long jump module in such a level is redundant.
As you are naturally not able to use that module in that level. ;)

If you want go further, you can also spawn the unique items for the achievements again:

Originally posted by BMS DIGITAL SPORTS:

You can use a console command to spawn the hat. Start Surface Tension from the "New Game" setting, and then type the following into the console:

prop_physics_create props_junk/tomabasarab_quaff.mdl

This will spawn the hat in front of you. Then, aim your crosshair at the hat, open the console, and type the following:

ent_setname quaff

This will make the hat be treated as THE ONE TRUE GOD the purple hat. You can now continue on your merry way. Sorry for the inconvenience.

For the Pizza:

prop_physics_create props_canteen\pizza_box.mdl

Aim on the spawned pizza and then use

ent_setname drhornspizza

For the gas cannister:

Originally posted by mp_Shell:

Looks like I've found the answer:

prop_physics_create props_questionableethics\qe_gas_cylinder.mdl

ent_setname gas

https://steamcommunity.com/app/362890/discussions/0/2577697550649066266/#c2577697550649844298

Not sure if it works though, that needs to be checked.

Originally posted by mp_Shell:

Checked that and can confirm that it works. However teleport will not recognize the item if you spawn it directly on the teleport. Spawn the item aside with that commands, then grab and drop on the teleport, and it will be accepted. Now you can proceed to the secret tunnel.

In the event that it doesn't work, install .net repair tool from here: https://www.microsoft.com/en-us/download/details.aspx?id=30135

In the event that doesn't work either, try launching your game with -oldgameui to see if it helps.

An additional fix is to delete d3dx9_24.dll and d3dx9_42.dll from System32 and SysWOW64 folders respectively, then re-install those files using DirectX End-User Runtime Web Installer from here: https://www.microsoft.com/en-us/download/details.aspx?id=35

If that still doesn't work, you are welcome to make a support ticket at Crowbar Collective's Discord Server, where we can assist you further.

1. Try changing your audio settings in-game to 4 Speakers (or 5.1, or 7.1).
   It would seem that playing the game set to Stereo/Headphones was causing completely random frame rate drops of 10-40 FPS across a 2-3 second period.

   As stated before, check to make sure you have the latest audio/sound card drivers installed.
   Check with Windows updates if any audio drivers are available. Please check with the manufacturer of your sound card, like Realtek, if any updates are available that Windows did not download and install.

   Crowbar collective have said that they have stressed the Source Engine's audio engine to the absolute limit.

2. Make sure to have Motion Blur set to 'On'.
   It should help eliminate frame-rate stutter.

3. Use Xbox Game Bar's Frame Rate Counter.
   Whilst in the game, press 'Windows Key + G' to bring up the Game Bar. Then open the performance widget. Untick all other performance metrics, so that the FPS counter is the only one selected. Close the graph and then click the pin to have the overlay stay on permanently. This trick stops FPS drops of 5-10 FPS from occurring and smooths out the frame-rate significantly.

4. Before you start Black Mesa, add the following to the game launch options:
   
   +fps_max 75
   Different areas within Black Mesa can have your frame-rate go from over 200 FPS and then suddenly drop to 90 FPS or less. This stresses the GPU and causes timing related issues with the CPU. By limiting the engine frame rate to 75, while having a monitor with a refresh rate of 60, helps the GPU stay steady and more easily stay in sync with the CPU. Which in turn, helps smooth out the frame-rates.

5. Try lowering the following in-game video settings to help reduce the amount of CPU and VRAM usage:
   - Water Reflections setting.
   For example, lowering from 'Ultra' to 'High'.
   (This SIGNIFICANTLY reduces CPU and VRAM usage. This actually has very little change on the visual quality of the water, but improves system performance drastically!).

   - Dynamic Lights setting.
   For example, lowering from 'Ultra' to 'High'.

   - God Rays setting.
   For example, lowering from 'High' to 'Low'. Or even turning them off completely.
   (There's very little difference in picture quality between High and Low. Also, some people have had success with fixing crashes by turning this setting off completely).

   Stutter may be the result of going over your Video RAM (VRAM) budget, or pushing your GPU over it's maximum threshold. Crowbar Collective haven't added any hard limits based on individual hardware within their implementation of Dynamic Lighting and Shadows, like other game engines do.

   The in-game settings have a handy information guide when you mouse over them, showing you the cost of each setting associated with GPU, CPU and VRAM.

6. Try resetting the game settings to factory default.
   This may clear up any issues that were caused by any number of unknown reasons. To do this, add the following to the game launch options:
   
   -dev -novid -autoconfig -autoexec

• mat_dxlevel 95
  
• mat_hdr_level 2
  
• mat_tonemapping_occlusion_use_stencil 1

• mat_monitorgamma_tv_enabled 1

We are sorry for the inconvenience, but this is the nature of the Source engine, and it would require more work than it is worth to fix this, if possible at all. While the developers understand the frustration, they cannot be held responsible.

Saves break because maps are recompiled when major updates are rolled out. Trying to load a save from an older build will attempt to load an older version of the map which causes old kinds of issues.

Black Mesa offers you the option to revert back to an older build. To do so, right click on "Black Mesa" in your Steam library, hit properties, go to the "Betas" tab and choose the beta you would like to opt in. For example, if your saves were made when playing version 1.0., then select "black-mesa-1-0."

Note: Please note that if you were opted in the public_beta branch, we expect everyone to understand what that means and that you are subject to more updates that may break your saves frequently. If you do not want this, make sure you are opted out of any beta testing by selecting "NONE - Opt out of all beta programs."

You will need to load a new game from the chapter you were on. Alternatively, you can manually load the map you were on. Check here for a full list. If you happened to be doing the hat achievement, rest assured, you can use console commands to resume the achievement quickly. See here for the hat achievement.

We apologize for the inconvenience. The issue will be with the engine itself at the end of the day because of various factors, including but not limited to CPU limited engine and DirectX 9.

You can, however, aid in getting better performance by using the following launch options:
-mat_antialias 0 -mat_aaquality 0 -oldgameui +cl_csm_Enabled 0 +nr_shadow_active 0 +nr_shadow_quality 0 +np_active 0 +np_quality 0

• Turn off anti-aliasing
  
• Revert to the old menu UI
  
• Disable dynamic shadows cast from the outside world and reduces then number of active shadows and quality
  
• Disable post processing

= 'Game Launch Options'
Is a way to add commands via Steam to launch a game with different fixes. To get to the option to add the launch commands I reference below; Right-click Black Mesa in your Steam games list, click Properties, then under the General tab add the commands to the Set Launch Options box.

Make sure each command starts with either the 'minus' - or 'plus' + character indicated in the FAQ below; and has a space after each command.
The 'minus' - refers to an engine command and the 'plus' + refers to the developer console commands. (Example: -dev +fps_max 75)

= 'Developer Console'
Is an overlay that will drop down from the top of screen over the game that allows you to input commands to enable or disable different settings not present within the settings UI. To access this; within the game, on your keyboard press the 'tilde' ~ key and the Developer Console should appear.

If the Developer Console does not appear, you will need to enable it. Go to the in-game Options menu, then select Game, then change the developer console option to 'yes'.

Please note that adding Console Commands to the 'autoexec.cfg' is no longer necessary as you can simply add the console commands to the Steam 'Game Launch Options' field instead, by adding a 'plus' + to the console command instead of a 'minus' - (For example +fps_max 75)