Return to Castle Wolfenstein - IORTCW source port

tpo1990

@mitu Thanks for pointing it out. I thought I was home safe. I should probably reinstall my test environment to make sure it is fully updated to Raspbian Buster on my RPI 3B. I will need some more time to be able to continue investigating the issue.

@Cesarpuig If that is the case on Stretch that it needs the libgles1-mesa-dev dependency, then we must think of another way to get it to work otherwise the game will only compile and install on Raspbian Buster.

Zering

@Cesarpuig I have followed your instructions to the letter and still no luck. I am booted back to ES after a few seconds of black screen. The only difference is now I can see the mouse cursor in the upper right corner of the screen for a split second, so it seems the game does launch in some capacity.

I've also noticed that I do not have the .wolf file. Is this a file that is generated when the game is first started? If not could that be part of the issue?

At this point, I'm concluding that the game has become self-aware and outright refuses to let me play it. ^^

Cesarpuig

@Zering post your log

Zering

@Cesarpuig That would be in dev/shm right? There's nothing there. Is it possible that it doesn't produce a log?

Cesarpuig

@tpo1990 Hi.

I have updated my script:

function depends_rtcw() {
	local depends=(cmake libsdl2-dev libsdl2-net-dev libsdl2-mixer-dev libsdl2-image-dev timidity freepats)

	if compareVersions "$__os_debian_ver" lt 10; then
        depends+=(libgles1-mesa-dev)
    fi
	
	getDepends "${depends[@]}"
}

Now do not try to install the libgles1-mesa-dev dependency on Raspbian based on Debian 10 Buster.

I tried it on:

RPI3 Raspbian 9 stretch Retropie 4.6- Ok

RPI4 Raspbian 10 buster Retropie 4.5.20- Ok

I updated the link where I share my script in a previous post

@Zering Yesterday I lost my internet connection and today I will no longer be on my computer, we take up the subject again tomorrow, :).

/home/pi/.wolf is not a directory it is a symbolic link and is created during port installation.

tpo1990

@Cesarpuig Hi. Great to see some progress. I will try it out tomorrow and see if I can get it to work so that we can come to a solution that works for Stretch and Buster.

The reason why /home/pi/.wolf is a symbolic link, is that it needs to point to the rtcw port configs folder the same way that other ports does when they get installed from RetroPie-Setup. This is also true for the main folder the game loads the .pk3files from which is a symbolic link that points to the roms -> ports folder where a user will copy the .pk3files to.

Cesarpuig

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

The reason why /home/pi/.wolf is a symbolic link, is that it needs to point to the rtcw port configs folder the same way that other ports does when they get installed from RetroPie-Setup. This is also true for the main folder the game loads the .pk3files from which is a symbolic link that points to the roms -> ports folder where a user will copy the .pk3files to.

yes, I know the reason, it's just that @Zering it says that directory does not appear after installing the port, it was a comment to a previous post of yours

Zering

Well I am thoroughly confused lol

So is the missing /home/pi/.wolf the reason my install won't run?

Cesarpuig

@Zering Hi.

Well I am thoroughly confused lol
So is the missing /home/pi/.wolf the reason my install won't run?

Of course it can be, the problem is that the installation script does not create the symbolic link for you, and later when we run iortcw it does not create the home/pi/.wolf folder, which I think should.

You might have a permission problem

1º Update the installation script to the latest one in the source I shared.

2º Assuming that you have not changed the user name and from the console, execute the following lines

sudo chown -Rh pi:pi /home/pi
sudo chown -Rh pi:pi /opt/retropie/configs

If you have changed the username you have to know it

4º Reboot system

5º Run the installation script from the Retropie setup menu and uninstall the rtcw port

6º Reboot system

7º Run the installation script from the Retropie setup menu and install the rtcw port

8º Retropie will create a log of the installation at this address, /home/pi/RetroPie-Setup/logs, save it.

9º Install the necessary data to run the game on /home/pi/RetroPie/roms/ports/rtcw

10º Try to run.

11º Comment. If the result was not satisfactory, retropie would have created another log in /dev/shm, post
both of them logs

Zering

@Cesarpuig Still no luck. I followed the instructions to the letter although I'm not sure what the sudo chown commands did or how they were supposed to work.

Here is the installation log :

link text

Here is the /dev/shm log :

link text

Cesarpuig

@Zering

Your problem occurs during the installation process, I do not think it is very difficult to solve it

mv: failed to preserve ownership for '/opt/retropie/ports/rtcw/main/cgame.mp.armv7l.so': Operation not permitted
mv: failed to preserve ownership for '/opt/retropie/ports/rtcw/main/cgame.sp.armv7l.so': Operation not permitted
mv: failed to preserve ownership for '/opt/retropie/ports/rtcw/main/qagame.mp.armv7l.so': Operation not permitted
mv: failed to preserve ownership for '/opt/retropie/ports/rtcw/main/qagame.sp.armv7l.so': Operation not permitted
mv: failed to preserve ownership for '/opt/retropie/ports/rtcw/main/ui.mp.armv7l.so': Operation not permitted
mv: failed to preserve ownership for '/opt/retropie/ports/rtcw/main/ui.sp.armv7l.so': Operation not permitted
mv: failed to preserve ownership for '/opt/retropie/ports/rtcw/main/vm/cgame.mp.qvm': Operation not permitted
mv: failed to preserve ownership for '/opt/retropie/ports/rtcw/main/vm/qagame.mp.qvm': Operation not permitted
mv: failed to preserve ownership for '/opt/retropie/ports/rtcw/main/vm/ui.mp.qvm': Operation not permitted
mv: failed to preserve ownership for '/opt/retropie/ports/rtcw/main/vm': Operation not permitted

I do not understand why you have this problem in Retropie and I do not, in two different RPIs that I am testing

Give me 10 minutes to see if I optimize the script to solve your problem and share it

Cesarpuig

@Zering
I have updated the script, download it, replace it with the previous one, install, and even if it works, share your logs with me, before installing it delete from the console the directory that does not let you move, sudo rm -R opt/retropie/ports/rtcw/main

A Former User

I had to make some modifications for this to work in Ubuntu x86_64

You can find my changes at:
https://raw.githubusercontent.com/gderber/RetroPie-Setup/develop/scriptmodules/ports/rtcw.sh

Note:
While I did my best to preserve the original code required for RPi, I do not have an RPi setup to test on.

tpo1990

Okay so I made some progress to make the script work both for RetroPie Stretch and Buster with the help from Cesarpuig and added an optimized config file for multiplayer so that the game plays in full screen. I have uploaded the changes to my github repository.

While doing this it made me think of why someone would still use RetroPie Stretch instead of just using a fresh install of the latest RetroPie with Buster.

Could someone test it by using the download link and reply back with a status?

ExarKunIv

@tpo1990 i downloaded the new.Sh from your github, and tryed it on my build which is still Stretch.

this time it does go through and install everything (before i was getting a error so i gave up)

but my game will not start

iortcw 1.51d-SP_GIT_6938a2d-2019-05-06 linux-arm Jun 14 2019
----- FS_Startup -----
Current search path:
/home/pi/.wolf/main
/opt/retropie/ports/rtcw/main/sp_pak4.pk3 (21 files)
/opt/retropie/ports/rtcw/main/sp_pak3.pk3 (14 files)
/opt/retropie/ports/rtcw/main/sp_pak2.pk3 (232 files)
/opt/retropie/ports/rtcw/main/sp_pak1.pk3 (1342 files)
/opt/retropie/ports/rtcw/main

----------------------
1609 files in pk3 files


"pak0.pk3" is missing. Please copy it
from your legitimate RTCW CDROM.

Also check that your iortcw executable is in
the correct place and that every file
in the "main" directory is present and readable.

the funny thing is i have my pak0.pk3 in with all the rest of them. so im reinstalling the game on my pc and ill let you know what i get

UPDATE
ok so if i just run the install and not copy your .cfg files you have on your github the game launches

tpo1990

@ExarKunIv Good to hear that you finally got it to install on your build of Stretch. I am using the GOG version of Return to Castle Wolfenstein and that version works perfectly. I cannot say about any other version if it works or not. The most important thing is that the game will need all the relevant .pk3 files to be able to launch.

Thanks for trying it out. I installed it recently on my Pi4 with latest RetroPie Buster and it works fine.

A Former User

@tpo1990 I added your recent changes to my script. A quick note, my RetroPie user is not 'pi' so I had to modify the function remove_rtcw from:

function remove_rtcw () {
  rm /home/pi/.wolf
  rm /home/pi/RetroPie/roms/ports/rtcw/*.so
  rm -R /home/pi/RetroPie/roms/ports/vm
}

to:

function remove_rtcw() {
  rm ${HOME}/.wolf
  rm ${HOME}/RetroPie/roms/ports/rtcw/*.so
  rm -R ${HOME}/RetroPie/roms/ports/vm
}

for the function to work for me.

Thank you for the good work with this!

tpo1990

@gderber Thank you for the compliment. If the `${HOME} variable works with any user I might just change that into the script so it accounts for all users.

A Former User

@tpo1990 ${HOME} is the same as $HOME, and looking at at least the rtcw.sh file you created, the same as $home. I haven't dug into the RetroPie code too deeply yet, I'm guessing somewhere in the code there is a home=$HOME statement for your code to work.

$HOME will always work. I add typically add the {} around all my variables when bash scripting because I have found I make fewer mistakes that way, especially when I have to concatenate multiple variables right next to each other.

mitu

@gderber $home is the recommended variable to use to refer to the installation user's homedir, because usually the setup scripts are run with sudo, so $HOME might be not be correctly set.