I've put together Wine wrappers for the Risen games, allowing them to be played on Linux almost like native games & with no Wine knowledge required. (Please note that the Risen 2 & 3 wrappers require the gold/complete editions)

Simply run the build script to create the wrapper. If the installer files are not alongside the wrapper build files then the path to them will need to be specified either by passing it as an argument to the build script with -respath="<path>" or by setting an environment variable named WINEWRAP_RESPATH containing it. You can change the path to build the wrapper in and the name of the wrapper directory with the -buildpath= and -dirname= arguments. The build path can also be set with the WINEWRAP_BUILDPATH environment variable.

The output will be a directory containing the game set up within a preconfigured Wine prefix, along with its own copy of Wine, extracted game icons, documentation, and start script(s). From there simply run the start script to play. The start script also includes options for creating a shortcut, configuring the wrapper etc.

(to uninstall simply delete the game directory and any shortcuts you created, and the game's user data directory in ~/.local/share if you don't want to keep your saves & settings)

User data is stored under ~/.local/share/risen, ~/.local/share/risen2, ~/.local/share/risen3

Full details are in the readme.txt and release notes. Here are the download links:

risen_wine.tar.xz
(38.5 kB, SHA256: 7d6af50d035e781a43503449b32250f6c96b22d936b34d56fe820817728d7ec2)

risen2_wine.tar.xz
(38.1 kB, SHA256: ec883ce5feea2da66e00e91ef4db1f8bfc0d87b3c0b250bf2f81d5fa9f0b81ae)

risen3_wine.tar.xz
(44.2 kB, SHA256: a2c6dedbd50e927d3f58ac1034e05a067164abb7b3139dc7744e266a59cc4552)

Last updated 2021/07/11

The wrappers use Wine 6.0. Wine, Winetricks and a redistributable for PhysX will be downloaded automatically if not present; to avoid redownloading for other scripts the downloaded Wine package will be stored in ~/.cache/winewrap and the PhysX redistributable will be stored in ~/.cache/winetricks/physx

I've only played the beginning of the games (except Risen 2, which I've fully played through) but they seem to run well so far. The only issues I've encountered are the logo videos at the start not playing properly and in Risen 2 shadows are somewhat buggy, most notably in indoor areas. Also in Risen 2 the player character's eye and the gnomes' faces are rendered completely black.

Risen 3 likes to crash every so often (apparently at random) so save often & read the release notes first!

Unfortunately none of these games run well on Intel integrated graphics, if at all

If anyone encounters any other problems then post in this thread, Adamhm's Linux Wine Wrappers - News, FAQ &amp; Discussion and/or The "Judas&trade; does this run in Wine" thread v1.173.

For more of my Linux Wine wrappers check out post 3 in this thread: Adamhm's Linux Wine Wrappers - News, FAQ &amp; Discussion

Wow, thank you for this, adamhm. I picked up Risen on sale fairly recently and was thinking I might have to run it via Window box (VM). This is great news! :)

Thanks for your work. To use it for the German edition of Risen 1 I had to edit risen_wine.sh by exchanging file names and checksums in WRAP_FILES.

WRAP_FILES=( "27ac83e1261ea180f6e35b3a27e1074e0018040d2d69dcea0c5d708a4b53baf1" "risen_res.tar.xz"
"6672e85fdc7acdab0edb880f3c50eabdde8d35e83869025fd29e4d355e95e8d1" "setup_risen_german_1.0_(18662)-1.bin"
"afef395f3d731b6937f4f953056143c92ea16e272b665c486902c160207df000" "setup_risen_german_1.0_(18662).exe"

Additionally, the path for the .exe was hardwired in another place in the .sh, so I had to change the file name there also.

echo "Extracting $WRAP_NAME..."
if (! "$INNOCMD" "$WINEWRAP_RESPATH/setup_risen_german_1.0_(18662).exe" -g -d "$TEMP") ; then
echo "ERROR: innoextract failed."
exit 15
fi

Now Risen 1 starts without crash and seems to run smoothly. Seems, so far. *g*

You may be interested in modifying risen_wine.sh to include the German edition. A better way, IMHO, would have been to contact you per E-Mail. Alas, I could not find your address.

See post above mine.

The problem is the installers are not consistently packaged so just using the different installer files with the same scripts will not necessarily work properly, if at all - e.g. with GOG's newer installers there's usually an app/ directory that's mostly empty, with most of the game files and directories beside it along with the installer's own tmp/ directory etc.

Even between updates the installer layouts can change & make things more difficult e.g. the first version might have a clean data_dir/ to simply be moved into app/ directory, while an updated version might split data_dir/ so you have both app/data_dir/ and data_dir/ that then need to be merged.

This means a substantially higher workload for creating and maintaining the wrappers: for each installer I first need to run it in a fresh prefix to have a reference to compare against (and to get the registry entries), then I need to unpack the installer and compare the unpacked files to the installed files to work out what needs to be moved where in order to put everything in the right place (this can be a huge pain when there are a lot of files spread out over many directories - Dragon Age: Origins was particularly bad for this). Then I need to create & test the script.

Also there's the issue of available disk space vs downloading & storing the installers for each language.

I do support multi-language installers that include a language switcher tool though, and I plan to look into adding a language select setting for the other multi-language installers :)

No Problems with Risen 2 in German. Installing Risen 3 worked perfectly. Unfortunately, running it crashed after the intro. Same crash with a normal install in a fresh wine without using risen3_wine.tar.xz.

I am using wine-4.5.

Looks like it started needing native d3dx9_43 at some point for the intro scene to work. It can be installed via Advanced options --> Winetricks --> d3dx9_43

I've also updated the wrapper to include this fix :)

Recently I tried to play my installed Risen 1. It failed. Also Risen 2 failed. And Risen 3, well, that was never running. Time to look what is going wrong now. My system has changed over the time, also my wine. I'm not sure if the latter matters because the script downloaded a version of wine from PlayOn Linux.

But you never know until you examine seriously. Better, to assume nothing.

So, normally I'm using at the moment wine-vanilla-4.17 from Gentoo. Some versions ago I found that I had to enable the useflag vulkan. Two possibilities for problems with Risen.

So I installed wine-vanilla-4.01 with no additional useflags. Essentially a pure normal wine. No luck either. After playing around with some possibilities I deleted all occurrences of Risen 1 and started afresh. With a current version of Risen from Gog and a current version of risen_wine.tar.xz from this site.

I have provided as much info as can think of in www.triffids.de/pub/spiele/risen_1/error/.
install_log.txt shows the execution of risen-wine.sh. play_log.txt shows what happens after start.sh play. ris1_err.png shows the error window within the execution of start.sh play. winewrap.txt shows the content of .cache/winewrap. risen/ is .local/share/risen/. Dumps etc.

Well. Something missing? Any advice? :)

Hm. Trying to post I got "You cannot post any links at the moment". So I deleted the http and the :// before the www and now I will try again.

That's very strange... it looks like the build script didn't encounter any issues creating the wrapper, however when trying to run the game it's failing with a ton of "Excluding module:" messages that I've never encountered before. Make sure that you have all of Wine's dependencies installed, and that your graphics drivers are as up to date as possible.

What messages do you get if you try running the game like this:

WINEDEBUG="" ./start.sh play

?

WINEDEBUG="" ./start.sh play 2>&1 | tee debug_play_log.txt
locate winemenubuilder.exe > winemenubuilder.txt

Regarding dependencies. On Gentoo you build your own wine, so the build dependencies are surely satisfied. Regarding run dependencies, Gentoo should take care of that.

I have no problems running Gothic or Oblivion on wine-vanilla-2.17.

But it is more than possible that Risen uses the downloaded version of wine from PlayOnLinux. There may indeed be some run dependencies which are missing on my current Gentoo.

There were complaints about not finding libncurses.so.5 before I installed ncurses-compat which provided that additional to the libncurses.so.6 which came from the package ncurses. Not that the missing .5 mattered previously in running Risen. ;)

The error message regarding winemenubuilder.exe is nothing to worry about - my wrappers disable it so it doesn't make a mess of your system's menus.

My wrappers are packaged in a similar manner to what you'd get if they'd been wine-wrapped officially, and as such use their own Wine builds; in the case of Risen this is using the Wine 4.0 build from PlayOnLinux.

Hm. Trying to reply, removing quotes but one, ended in an endless loop displaying "Please wait. Processing...". I have copied the text into a new window for "new post", will then kill the old reply window and try to send this one. Hopefully killing the reply window works as intended.

I can not find the required run dependencies on the playonlinux site. But I can ask my Gentoo what is required to install and run playonlinux.

emerge -pv playonlinux > deps_playonlinux.txt

Some of them will only be required to build playonlinux. Some will be required to run it. As you can see, there are a lot to consider. Well, the obvious next step is to install the packages required by playonlinux and look what happens.

I will be back when I know more. May be some time.

PlayOnLinux's dependencies are not required; only PlayOnLinux's Wine builds are used, not PlayOnLinux itself.

One thing you could try is running it through the Steam Runtime - this is effectively just a collection of Ubuntu libraries with a script for running stuff using them.

If you have Steam installed on your system then you should be able to find the version provided with that under ~/.steam/ubuntu12_32/steam-runtime

Otherwise you can either build it yourself from the github link above or download it from here:

http://repo.steampowered.com/steamrt-images-scout/snapshots/0.20190711.3/steam-runtime.tar.xz
http://repo.steampowered.com/steamrt-images-scout/snapshots/0.20190711.3/steam-runtime.tar.xz.checksum

To use it to run my wrappers, simply do:

"<path to steam runtime>/run.sh" ./start.sh play

There seems to be no steam in Gentoo. I have downloaded steam-runtime.tar.xz and tried your advice. No success. Then I noticed the setup.sh and tried that first. No success.

Trying to build the dependencies of PlayOn Linux is difficult.

* Messages for package x11-libs/wxGTK-3.0.4-r2:
* Header files have changed between ABIs.
[...]
* ERROR: x11-libs/wxGTK-3.0.4-r2::gentoo failed (install phase):
* Header checksum mismatch, aborting.

| PlayOnLinux's dependencies are not required; only PlayOnLinux's Wine builds are used,

OK. But when playonlinux is installed on Gentoo then it should run the Wine builds. *g*

Now I have to see what the setup sh of steam-runtime has done to my Gentoo. Of course I did not run it as root.

At the moment playonlinx cannot be installed on Gentoo because one of the required dependencies has a bug. I have succeeded in installing all required packages where some are too modern, though. Didn't help with Risen 1.

There gas to be another reason as the dependencies. The lots of "Excluding modules:". Why? I will now stop, scratch my head and wait for some time.