Half-Life

Half-Life

Modding Nightmare with Linux
I have an issue where I have multiple mods and while most can run in one version, there's usually an outlier that doesn't like the beta branch, legacy branch, or proton. If I use the beta branch, Half-Life: Extended doesn't load since it's lacking a '.so' file in the dll folder.

So here's what I thought would solve this: If I could make a version of Extended act as Legacy Proton, I could run it from a different or even the same folder, but then I tripped the DRM since Linux HL is on Beta. So whether it's setting a different executable from the command line in the same folder, it trips DRM because the limiting factor is probably like versions from HL. If Extended runs as Legacy Proton, and it's expecting Linux Beta, it will throw up and authorization error.

How should I go about this?

On another note, I noticed that if I set the game as Proton Legacy, everything will work, but Half-Life Insecure will show garbled UI elements if you force a map start since it expects Linux Beta.
< >
Showing 1-2 of 2 comments
Did you rule out the issues?

So far, the only way to run HL1 mods for me was:
1. Use Steam Half-life 1
2. Launch HL1 using Proton at least once
3. Create Steam launch option for the mod in question
4. Use the freshest ProtonGE 10. DISABLE Wayland window support(PROTON_ENABLE_WAYLAND=0), if you're on a Wayland.

Then, any mod would work.
If you don't disable the Wayland support, the game would show weird alpha channel artifacts, and would stay at ~20 fps. Which is a sin for a game this old.

I don't want to use Xwayland, because it is proven to introduce the most input lag.
It's been almost a year. I can't recall everything involved, but from what I can remember, it's a conflict of the Beta update branch and the Legacy update branch. Most of everything is happy with the Beta branch except for Half Life: Extended.
< >
Showing 1-2 of 2 comments
Per page: 1530 50