Doom Pi Project Need Advise

Solid One

@tpo1990 Yes, I understand. And indeed Doom Legacy can render a much smoother splitscreen performance (it was originally developed for MS-DOS about 10~20 years ago). It even has multiplayer bots, and they are very decent for deathmatches.

On a different note, I read you guys are trying to compile Zandronum for RPi, but are having trouble compiling from the latest stable version (3.0), so you can't play online by using Zandronum + Doomseeker, right? Anyway, I think I just found a way of compiling latest stable version from source. Take a look here: https://wiki.zandronum.com/Compiling_Zandronum_on_Linux#Latest_stable_version

Basically, instead of compiling from latest alpha, you type the command below in order to find out which commit was used for compiling 3.0 release binaries:

cd ~/zandronum_build/zandronum &&
if [ "$(hg log -r 'max(tagged())' --template '{rev}\n')" -ge \
"$(hg log -l1 -k 'BUILD_ID_STR to release' --template '{rev}\n')" ]; then
hg identify -r 'max(tagged())'; else u="$(hg log -l1 -k 'BUILD_ID_STR to release' \
--template '{node|short}\n')"; echo "$u $(hg log -r $u --template '{desc}\n' |
sed -n 's/.*changed the version string to \(.*\)/\1/p')"; fi

Here's the result when you run that command after cloning the repository:

dd3c3b57023f ZA_3.0

Then I copied that hash above and searched for any commits containing it, and I found this commit:
https://bitbucket.org/ptitSeb/zandronum/commits/dd3c3b57023f64cda84f09ed13e4c03a4ad2b920

- changed the version string to 3.0
- changed BUILD_ID/BUILD_ID_STR to release

In other words, compiling Zandronum from that commit will give you the binaries for zandronum client 3.0.

And that's it. Try checking out all the instructions from the link above, and maybe you can finish the dependencies to get Zandronum working on RPi. And even play online through Doomseeker, which has hundreds of servers running Doom in a lot of different ways.

tpo1990

@Solid-One I'm quite sure that i already tried it but failed to get it to build to ver. 3.0. It would just build the alpha version instead. I might try it again. Thank you for your input.

Solid One

@tpo1990 If it fails to build, then I think I know the reason:
https://bitbucket.org/ptitSeb/zandronum/commits/121db9d6e8ec8bfa35672f8b1a63cf1d7e71289e

Fixed a compile problem on Raspbian Stretch.

The commit above is 10 commits after the one tagged as ZA_3.0 (the same from the link on my previous post), and was pulled in the same month as the 3.0 release. This commit basically change the file src/p_spec.cpp in order to change the type of a constant from char to SBYTE.

Assuming that was preventing Zandronum 3.0 stable to build, maybe this can work. However, it won't work if you simply clone the repository from that commit, since it'll change version from stable to alpha again, and then won't work for playing online.

tpo1990

@Solid-One So it has to be changed to specific use that commit when trying to compile Zandronum and the solution to the Raspbian Stretch might just work. Let me give it a try and see what i can come up with.