FAQ

This will be expanded as time goes on.

I need to use something called Xash3D for this mod. Why won't it work out of the box on Half-Life?
The original Half-Life runs on an engine called GoldSrc. This has some limitations, without which this mod wouldn't be possible. Xash3D is a custom implementation of the GoldSrc engine, with additional features such as high-res texture replacement support. It means this mod will take a few steps to get working, but I am certain you'll think it's worth the effort.

Does this mod work with another version of Xash3D?
This mod comes with and is developed for Xash3D FWGS v0.19.2. The other versions of Xash3D or Xash3D FWGS that I have tried do not have high-res texture support and/or support for Blue Shift and Opposing Force. You can try other versions, but I can't offer any technical support in that case.

Can I play multiplayer Half-Life or Opposing Force?
Yes, you can! It doesn't use Steam, so there are fewer servers than the Steam version of these games.

Can I use this with custom 3D models?
Yes, but you can't use the upscaled model textures then. If you use custom 3D models that this mod doesn't support, just delete the materials/models in your valve, bshift, gearbox folders.

Known issues
While there are minute differences between Half-Life on GoldSrc and Half-Life on Xash3D FWGS, the game is pretty much identical to the original. The only issues I noticed are with Blue Shift and Opposing Force:
  • In Blue Shift and Opposing Force, NPCs on moving trams shudder a lot while the tram moves. This would probably be an issue for Half-Life, if not for the lack of NPCs in moving trams in that game (as far as I know).
  • On my system looking around with the mouse in Opposing Force can sometimes result in involuntary movements. This is related to raw mouse movement. In GoldSrc Opposing Force this was fixable with the checkbox Raw mouse movement. This option does not exist in Xash3D. I've managed to alleviate the issues a bit m_enginemouse "1" and m_filter "1". This is added to the config.cfg, so should be on for new players.




Comments

Unknown said…
I can't properly map out pc controls so my move forward is bot bound to w and me moving my mouse forward. Very odd.
Unknown said…
Trying to move the mouse in Opposing Force is stuttery and horrible, it keeps reseting to the center of the screen. The game is unplayable :(
KrzyKyle said…
This comment has been removed by the author.
KrzyKyle said…
Yep totally cannot play Opposing Force at all. Thought I'd fixed it by getting the newest version of the engine and using the config file recommendations but that didn't help at all. I'm sad :(
Unknown said…
Mouse snapping to center = unplayable
Unknown said…
Can you use this with the VR Mod?

-Alex
CaptRobau said…
@Alex If it runs Xash3D, it might. I haven't tried.
Unknown said…
Is there a way to have my controls set so I can move using WASD?
CaptRobau said…
WASD should be configurable in the regular Half-Life menu. It looks a bit different because it runs on Xash3D but it should work. Alternatively you could change the .cfg in the installation. I believe it's called binds.cfg or something.
Unknown said…
My mouse keeps snapping to the center, and there is no way to fix it. I tried changing m_enginemouse and m_filter to 1. That did not work. It sadly ruins the experience and makes it unplayable.
Terminal Aura said…
I see my saves but they all say "Gold source unsupported." How do I fix this because I don't want to have to start the game over from the beginning.
CaptRobau said…
Sorry for the late response. My blog got a lot of spam bots and I didn't see you were a real comment until now.

GoldSrc save games are not supported by the version of Xash3D needed for this mod. Sorry about that.
Nepon said…
Like others have said. The mouse keeps centering and it really makes this game unplayable. There has to be some way to fix this right?
Stephen said…
Does this work with LambdaVR on Quest2? Its already running on XASH.
Obama said…
Mouse still doesn't work properly, I checked the config file and they weren't even set to what you just said they were set as. So I fixed it to what you were saying, but still didn't work