Games compilation howto on the Pinebook-pro (Manjaro Linux and Debian native)

[branon]

Here is the order I followed to get halflife1 running on the pinebook pro.

I tried multiple ways, but this was the most stable.

A tip, do not use the flashlight. (buggie)

You can put the "code-block" below in a file, e.g. create_hl.sh

It will give you halflife (xash3d) in the dir ~ / hl you can then start halflife with "xash3d.sh"

I've had 3 crashes before "the explosion" happened. So be warned

Code:

mkdir ~/hl #COPY your "valve" folder from (windows or linux system steam/cd install) to ~/hl/valve #on steam it is $HOME/.steam/steam/steamapps/common/Half-Life/ # create re-writen hl-engine. git clone --recursive https://github.com/FWGS/xash3d-fwgs.git cd xash3d-fwgs git checkout tags/v0.20 git submodule update ./waf configure -T release --prefix ~/out ./waf build ./waf install cd .. cp ~/out/lib/xash3d/* ~/hl/ # create hl-sdk (improved). git clone https://github.com/FWGS/hlsdk-xash3d.git cd hlsdk-xash3d ./waf configure -T release ./waf build cp build/cl_dll/*.so ~/hl/valve/cl_dlls cp build/dlls/*.so ~/hl/valve/dlls cd ~/hl # get a startup script from a older re-writen engine. (stil works) wget https://raw.githubusercontent.com/FWGS/xash3d/master/scripts/xash3d.sh # make it executable. chmod +x xash3d.sh

Interesting that you had issues with crashing. I am using xash3d-fwgs engine as well.

I followed these two guides: https://astr0baby.wordpress.com/2020/01/...ng-part-3/ && https://www.reddit.com/r/RetroPie/commen...r_goldsrc/

Both are using the 'legacy' engine https://github.com/FWGS/xash3d which I swapped out for the new engine: https://github.com/FWGS/xash3d-fwgs

This has mostly worked, hazard course works, multiplayer works, story mode also works, however during story mode I sometimes get crashes, mostly while loading new areas. If I restart the game and try again, the area will load successfully.
 
Here's a screenshot: https://branon.me/share/OTlmZTR.png

And the output: https://pastebin.com/raw/V8q8esfs (nothing is ever printed after "Stack dump:")

Not sure if I should try to debug this, or compile the legacy engine and see if it goes away