[LINUX] Half-Life 2 crashing when starting a new game

[27LIEF]

I was able to play Half-Life 2 fine some days ago, but the yesterday patch seems to break the game as everytime I start a new game. the game crashes with a Engine Error "Failed to lock index buffer in CMeshDX8: :LockIndexBuffer".

As a temporary fix, switching the game to a previous build works fine

[Jeremy]

I am also getting this same error on Linux

[NoobSolid26]

Looks like the update from the 27th is broken somehing on Linux. Weird stuff.

[Dodger]

I played through hl2 and episod 1 without a problem. But episode 2 was crashing everytime after the intro. The fix for me was to turn on the use off one cpu core only.

[GreenMan]

able to play, but the very first load point where the box puzzle is, crashes my game.

[otkorturson]

this happened to me, was there an update recently?

[Yubaru]

Same thing.
I tried to lower the settings, running the game through wine instead or proton and using a few launch options to squeeze fps, but it still didn't work.
Well, atleast i'm glad i'm not the only one with this problem

[Rumi]

2023 will be the year of linux

[Juneytunes]

Same issue...hope this gets patched soon because it's really annoying

[MEL-1S3]

Found a fix that works for me
If you add -vulkan to the launch options you change the render engine from opengl to vulkan, and for me that fixed if not all but 90% of the crashes

[Yubaru]

using -vulkan makes all of the source games crash for me, unfortunately.

[Sadnehs]

I got past the crash by forcing Proton 9.0-3 (it was set to not force a proton version before)

[76561198067836880]

Originally posted by Sadnehs:

I got past the crash by forcing Proton 9.0-3 (it was set to not force a proton version before)

ur a genius! thanks so much this worked for me too. - after hours uf un and reinstalling!!

[27LIEF]

Forcing Proton is using the Windows version of the game, just like changing the previous build, it's not really a fix, but a workaround

[NoobSolid26]

Are they fixed it? I'm not getting the same error anymore. (Edit: It still gives the same error again)

[GreenMan]

Originally posted by NoobSolid26:

Are they fixed it? I'm not getting the same error anymore.

I just turned on the proton tools and it seemed to fix the issue.