Unfortunately we can only use the *data* from that installer. We can't use any of the program code. Instead the code we are using (to build on FreeBSD) is actually compiled from Valve's official Half-Life SDK. They basically open-sourced the game code (not the engine).I would really like to play Counterstrike as well.
I had never heard of that expansion! I am very interested in trying it out. All the links I find for it lead to a blank page, though.My personal want though is getting the Half-Life Decay (semi-official) going for a polished coop experience. Hosted here: http://half-lifecreations.com/
Yeah its pretty cool. Possibly one of my favorites because of a slightly shorter Xen section! You play as one of the soldiers. What that mostly means during gameplay is that your hands look different and some security guards are fatI had never heard of that expansion! I am very interested in trying it out. All the links I find for it lead to a blank page, though.
Thank you! But running the script again over an already existing installation does not work. I guess you would first need to remove everything first, fetch everything again, then edit the script and afterwards run it, because:Then the only thing you need to do is instruct the build script to extract the opposing force data from the SteamDRM gcf file. This is done on line 94 of the build.sh, so just uncomment it.
cd openhl/
$ sh build.sh
mkdir: /usr/home/werner/openhl/export: File exists
If you are a fan of Half-Life, you can now easily play this on FreeBSD. I have forked a number of projects in an attempt to make things easier to get up and running without relying on a port (which due to licensing is unlikely to be an option for binary distribution).
Yep, thats true. Though I have been very careful to ensure everything is put in that export directory. So you can just delete that.running the script again over an already existing installation does not work
sh build.sh
. Yep, as you mentioned a package is a no go. I also need to push a few changes to enable saving of config files in $HOME rather than export/share.Ugh, the worst place to be!Gnaa. I'm stuck in XEN.
sv_cheats 1
/noclip
should work.Well it is great to hear that the Xen map designer's efforts are appreciated by some!And XEN is a fun place, imho
What about hl2? Is it possible to run it on freebsd?
If you are a fan of Half-Life
# pkg install controllermap
and when I run controllermap
from a terminal, all 16/12 buttons and the 2 analog thumb joysticks are functional and can be mapped. However, my KDE Plasma does not show any gamepad/joystick in its settings GUI for input devices, Plasma only sees the keyboard and the mouse.# dmesg | grep uhid
uhid0 on uhub4
uhid0: <THRUSTMASTER FireStorm Dual Power 2, class 0/0, rev 1.10/1.00, addr 9> on usbus0
ls -l /dev/uhid0
crw-rw---- 1 root operator 0xf3 Jan 28 03:09 /dev/uhid0
groups
aaaa wheel operator video vboxusers
Yes, it is an engine called "Flying with Gauss" (formerly xash). I believe it has slightly dubious origin with some leaked code but I could be wrong. When going through the code, it just looks like a typical open-source project.Installed, and it works great. My understanding is this HL runs on a different and open source engine, which makes it all even more amazing.
Hmm, actually I am not sure. The upstream developers have a heavy focus on Android (which is why I forked the project because Android support is a messy dead end time suck . It could well be that gamepad support is not in there unless it comes for free (i.e with SDL). I will check the code when I get back.Does the OpenHL has gamepad support?
controllermap
into the system variable then start the openhl in the same line, with &&
and it didn't work, something like this:$ export SDL_GAMECONTROLLERCONFIG="030000008f0e00000300000010010000,GreenAsia Inc. USB Joystick ,platform:Linux,x:b3,a:b2,b:b1,y:b0,back:b8,start:b9,dpleft:h0.8,dpdown:h0.0,dpdown:h0.4,dpright:h0.0,dpright:h0.2,dpup:h0.0,dpup:h0.1,leftshoulder:h0.0,leftshoulder:b6,lefttrigger:b4,rightshoulder:b7,righttrigger:b5,leftstick:b10,rightstick:b11,leftx:a0,lefty:a1,rightx:a3,righty:a2," && hl
OK sure. Yes I was thinking the same. It isn't like Doom, Duke3D or Blood where you are effectively playing on a 2D plane even though it looks 3D. Awkward with gamepad.Please don't spend time looking for gamepad support in sources, I've tried on an WinXP32 laptop with the original HL game and the same gamepad. It's impossible to aim properly with my gamepad.
sudo apt install xorg git libfreetype-dev libfontconfig1-dev libsdl2-dev mono-complete cmake pkgconf
# - in Debian, csc is known as mono-csc, a symlink to /usr/bin/msc
# the 'csc' name might conflict with another package, 'chicken-bin'
# usually, 'chicken-bin' is not preinstalled
# - create a 'csc' symlink to the '/usr/bin/msc', so to keep the same build.sh
cd /usr/bin
sudo cp -s /usr/bin/mcs csc
cd ~
git clone https://github.com/osen/openhl.git
cd openhl
PYTHON=python3 sh build.sh
# if the compilation fails, fix the errors, delete the 'export' directory
# then run only this line again. Do not start anew and do not git clone again,
# because that is not necessary and the repository is very big (~300MB)
# for Linux, the .so names has to be changed from libclient/libserver to client/hl
sed -i 's/libclient\.so/client\.so/' export/bin/hl
sed -i 's/libserver\.so/hl\.so/' export/bin/hl
sed -i 's/libclient\.so/client64\.so/' export/bin/opfor
sed -i 's/libserver\.so/hl64\.so/' export/bin/opfor
# to run the Half-Life game
export/bin/hl
# to run Half-Life: Opposing Force
export/bin/opfor
export/bin/opfor
I see the same game as when I run export/bin/hl
, and the saves I see inside opfor
are the ones I've made while playing hl
. This happens in FreeBSD (and in Linux, too). hl
and opfor
games have different maps and different story. Apparently, export/bin/opfor
starts the same Half-Life, so how do I start Opposing Force (asking for the FreeBSD version, of course)?Opposing Force uses the same Half-Life engine. Support is there in the code and it works fairly well, you just need to extract the files from the Steam pre-cache installer into the correct place. The script doesn't do this by default (they are commented out) and I haven't uploaded that installer to GitHub (to avoid long download times during a clone).My understanding is that both games are there, and thathl
andopfor
games have different maps and different story. Apparently,export/bin/opfor
starts the same Half-Life, so how do I start Opposing Force (asking for the FreeBSD version, of course)?
It should be here in the code (FS_WriteGameInfo):As I assume you had quite a deeper look at the code: where does it try to write stuff, can you think of a way to teach it to use something below $HOME instead?
exec
in your scripts... )