Return to Castle Wolfenstein - IORTCW source port

tpo1990

@Quackwalks Then i have no idea what to use for make it able to mute the music when starting rtcw at the moment. But maybe @cyperghost 's approach could work.

Turrican2k

Error message when I try to create a server (local or online, it doesn't matter):
Unpure Client Detected Invalid PK3 Files!

What can i do?

ExarKunIv

@tpo1990 when i ran the update script for Retropie i get a error for rtcw.
so when i uninstalled it and tryed to reinstall it. it now fails.

just letting you know.

quicksilver

@Turrican2k "For Multiplayer. Add all the multiplayer pak files: mp_bin.pk3, mp_pak0.pk3, mp_pak1.pk3, mp_pak2.pk3, mp_pak3.pk3, mp_pak4.pk3, mp_pak5.pk3, mp_pakmaps0.pk3, mp_pakmaps1.pk3, mp_pakmaps2.pk3, mp_pakmaps3.pk3, mp_pakmaps4.pk3, mp_pakmaps5.pk3, mp_pakmaps6.pk3 from your RTCW installation to /home/pi/RetroPie/roms/ports/rtcw."

Turrican2k

@quicksilver I did it completely according to the description! A total of 19 files that I have transferred from the Platinum Edition. The single player works anyway, multiplayer has the said error message ...

quicksilver

@Turrican2k I'll see if I can replicate your issue

mitu

@Turrican2k Set sv_pure 0 in the .cfg file - or toggle the console (via ~) and write sv_pure 0.

Turrican2k

@mitu Thank you very much, that helped!

However, you have to enter in the * .cfg seta sv_pure "0".

tpo1990

@ExarKunIv What RPI model did you ran the update script on?

@Turrican2k You can also disable the "Pure server" option in the multiplayer server options. It should be there when choosing multiplayer map. This is easier that editing the .cfg file or changing it in the console.

Evert

Hi all, I've just tried installing this, but I get the following error:

Could not successfully install RTCW - IORTCW source port of Return to Castle Wolfenstein.
(/home/pi/RetroPie-Setup/tmp/build.rtcw/SP/build/release-Linux-arm/iowolfsp.arm not found).

I'm on a Pi 3B running the latest Buster build.
To install I ran

wget https://raw.githubusercontent.com/tpo1990/RTCW-RPI/master/rtcw.sh -P $HOME/RetroPie-Setup/scriptmodules/ports/

and then I installed from source in the RPsetup menu. Anyone know what's going on?

Also, when I do manage to install this, do I need to have all the single player pak files (pak0.pk3, sp_pak1.pk3, sp_pak2.pk3, sp_pak3.pk3 and sp_pak4.pk3) to run this? My version of RTCW only has pak0.pk3 and sp_pak.pk3

Thanks

mitu

@Evert said in Return to Castle Wolfenstein - IORTCW source port:

and then I installed from source in the RPsetup menu. Anyone know what's going on?

There's an error during installation from source - look in the logs sub-folder and you'll find the detailed error in the latest log file. My guess it's missing a package dependency and compilation fails.

Evert

Hi mate, this is the last section from the log:

In file included from code/renderer/qgl.h:38,
                 from code/renderer/tr_local.h:37,
                 from code/renderer/tr_altivec.c:29:
/usr/include/SDL2/SDL_opengles.h:33:10: fatal error: GLES/gl.h: No such file or directory
 #include <GLES/gl.h>
          ^~~~~~~~~~~
compilation terminated.
make[2]: *** [Makefile:2617: build/release-linux-arm/renderer/tr_altivec.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/home/pi/RetroPie-Setup/tmp/build/rtcw/MP'
make[1]: *** [Makefile:1383: targets] Error 2
make[1]: Leaving directory '/home/pi/RetroPie-Setup/tmp/build/rtcw/MP'
make: *** [Makefile:1301: release] Error 2
/home/pi
/home/pi/RetroPie-Setup/tmp/build/rtcw /home/pi

Don't really know what to do with this do. Do you need to full log or is the GLES file the only issue?

mitu

@Evert That's because there's no GLES1 dev package available for that Debian version - it used to be https://packages.debian.org/stretch/libgles1-mesa-dev, but in Buster that package is not available anymore - https://packages.debian.org/search?keywords=libgles1-mesa-dev.

Evert

@mitu ok, so does that mean that IORTCW won't work on the new buster image? Is there a work around or does the port require to be updated for buster?

mitu

@Evert said in Return to Castle Wolfenstein - IORTCW source port:

@mitu ok, so does that mean that IORTCW won't work on the new buster image? Is there a work around or does the port require to be updated for buster?

Can't say if/when it will work, but at the moment it's not building for Buster in the current form.
Anyway, since the Buster image is still a work in progress, you'll have to wait until it's actually released. Otherwise, use the current stable image and it might work.

Evert

no worries, thanks for your help mate. I will patiently wait. Plenty of other games to play ;)

ExarKunIv

@tpo1990 dont need to give you that :P @Evert posted all the info i was going to.
guess going to have to wait or down grade back to stock Pie.

testing what other Ports are not working

Evert

@mitu Do you know if this problem would be the same for the quake 3 port or does that use a different driver and therefore compile properly on Buster?

tpo1990

@Evert It will only be a problem for the ports/games that use GLES. At the moment Raspbian Buster is not supported for this port until it gets properly released.

You might be able to fix it by manually searching for how to install GLES on a Raspberry Pi. However take notice that this can be quite difficult if you haven't done that before since you might need to compile it. Since IORTCW uses the same engine as Quake 3, it might also not work for that game as well. I haven't tried Raspbian Buster yet.

I work only on the latest stable release from RetroPie. That is my primary priority, so that most users on RetroPie will successfully be able to install the port and play it.

@ExarKunIv No problem then :-P Didn't know that it will not be able to compile and install on Raspbian Buster. But now that I have that confirmed. Thanks. :-)

mitu

@tpo1990 It's only the GLES1 headers that have been removed from MESA - but I think they're also shipped in the librasperrypi-dev package (in /opt/vc/lib and /opt/vc/include). It might be just a matter of adjusting the compile flags, but it's better to just wait for a Buster release for things to settle.