Necro Patch Follow Up

We’re investigating why some antivirus software and Windows Defender pick up the game or one of the tools as malicious. We’ve had tools flagged by different antivirus programs in the past, but never the .exe of the game itself. Needless to say, there are NO viruses within Black Mesa. We’re a little worried that this false positive is due to new detection methods beyond our control, but as we said, we keep looking into the issue!

(As of writing this we may have a lead as to what is tripping antivirus. We may have a workaround to fix it)

We apologize if this spooked anyone. The last thing you want to see after buying a game is that type of alert.


We updated the launch options to default to the game running in DirectX 9 and the UI running in DirectX 11. This helps ensure maximum compatibility across various target hardware.

There is still the option to run the game using Vulkan DXVK. If your computer is having trouble running the game in certain spots, this is a good option to try. It does have drawbacks: it does not like alt-tabbing from the game, and it cannot do borderless fullscreen correctly (the game will run fine, but it will act like regular fullscreen).

Finally, there is the DirectX 9 fallback, which runs both the game and UI on DirectX 9, in case your hardware setup requires it.

So now when launching the game you will see:
-Play Default
-Play Performance Option (DXVK)
-Play DirectX 9 (Legacy)

If you have already set the launch option and want to change, simply right-click the game, go to properties, General, and click the drop-down under “Launch Options”.


Soon, we will release a patch with the following fixes:

[h2]Steam Input[/h2]

• Upgrading Black Mesa to use Steamwork V1.52 for better input implementation
  
• [TO CONFIRM]: Fixed custom controller bindings not persisting
  
• Fixed an issue that prevented some users from climbing ladders and using trams on Steam Deck
  
• Lowering controller deadzone for better feel
  
• [NOTE]: A helpful guide on controller troubleshooting with Steam can be found here

[h2]Video Settings Crash[/h2]
We are aware that if you change certain video settings WHILE in game, it can crash the game to the main menu and not let you resume the autosave it just created.

We are looking into this.

[h2]Dedicated Server[/h2]

• Fixed build process for dedicated servers (a compile switch was missing)
  
• This should resolve some crashing issues with dedicated servers

[h2]Auto-Aim[/h2]
As mentioned in the patch notes, we completely overhauled the auto-aim feature within the game. This can be configured by changing console settings in the game. Details here.

If you would like to change the settings for the auto-aim permanently, all you have to do is go to Black Mesa\bms\cfg\skill.cfg and edit the numbers at the bottom of the text file.


We are interested to hear what people think of the auto-aim (most of us are terrible at playing the game with controllers). We may be increasing these values to be more magnetic with the upcoming patch.


A lot of community members have asked about Steam Deck verification. We don’t think we’ll be able to meet the requirements to get officially verified. We’re very happy with the progress that we have made, but full verification was never our goal (the main blockers being true full controller support, and performance in our more demanding levels).

For now, using Proton’s latest version or latest beta is the best way to run the game on Steam Deck. Proton has solved a number of issues we had in the native Linux version, so give that a try with our newly implemented Steam Input (right after we put out the ladder fix above)

If you get any drifting using gyro aiming, try calibrating the Steam Deck’s gyro. (tom’s guide article on how to do this)

We’ll keep an eye on Steam Deck and see if there is anything we can do to help make it even better going forward.

There are some other issues we'll be follow up with with the community. Thank you, again!