Did anyone manage to run Risen in Wine successfully? I'd buy it if it works.

Yup, get the wrapper from The Porting Teams site, only thing with it is you need to install
it into WIndows first, them copy it across into the wrapper.

http://portingteam.com/files/file/7201-risen/

Game running issue is that all ingame txt has no spaces, but it has speech so not so bad.

Other than that it runs great under 10.6.8

Why do you need it installing into Windows first?

Also, how is this wrapper project different from regular Wine? Do they have their own patches? I'm using Wine on Linux (from PlayOnLinux builds).

It is a WIne wrapper put together by somebody who knows what they are doing with wrappers unlike me.

Your best bet is to follow my link, register with the site then you can ask all your questions there regarding WIn e wrappers etc.

You asked if it worked under WIne, it does.

I have no idea about Linux, I have never used it, sorry.

Some games just do not install into wrappers, and you have to do the install under windows then copy the folder into the wrapper, this is not the first game to work like this, there are quite few you have to do this with. Running games in wrappers is not always straight forward as you would like it to be.

I got it and installed in PlayOnLinux. First of all it complained that it couldn't find sbdinst.exe during installation. Then it started with black screen.

All in all, experience is garbage (unplayable). May be there are workarounds, I'll do more tests.

Hello together!

Risen is working flawless in WINE 1.7.5 and above. Really important is the prefix and its preinstalled packages. So when using PlayOnLinux you are askes about the WINE-version to be used. Therefore you must download the correct version before installing. Within the next step PlayOnLinux asks for the name and then the packages to be installed. My bet personal for my installation:

armstream
d3d9-libs (all of them)
devenum
directx9
gdiplus
quartz
vcrun2005
vcrun2008
vcrun2010
xact

This should help for the first time running. But when there are additional errors or the black screen don't go away activate logging for your shortcut within the prefix. There you can have a closer look on the errors WINE gives you and what is missing.

I only installed d3dx9_36 and no other additional stuff, and the game worked! (Using it with Wine 1.7.16 in PlayOnLinux).

I have played Risen on Wine 1.7.x on Linux (Steam version) from start to finish, worked flawlessly without any issues. Didn't need to install any DX stuff, although Steam pulled some something in - I've no idea if the game would have worked without that.

Risen requires PhysX; if the GOG installer doesn't install it correctly under Wine you could use the latest NVIDIA PhysX System Software.

Current GOG setup tested on Wine 1.6.2 and the game worked after winetricks d3dx9_43 d3dcompiler_43

It actually didn't work for me with d3dx9_43 for some reason, but worked with d3dx9_36 (may be because I didn't install d3dcompiler_43).

The game is affected by the mouse turning bug, at least with some window managers (but not with others). I made a Wine AppDB entry here: http://appdb.winehq.org/objectManager.php?sClass=version&iId=30146

Steam version can't be compared to GOG version, since it can install different stuff indeed as well as contain different patches or whatever. So it should be considered a separate use case.

You're right, d3dx9_36 is correct for Risen 1. I was referring to Risen 2 without mentioning it, sorry.

I'm not using PlayOnLinux at all, but winehq git head from April 5 works fine for me on the GOG version of Risen, *as long as* I "winetricks d3dx9_36". So that's somewhere between wine 1.7.16 and 1.7.17, closer to the former, plus several DX DLLs from Microsoft instead of winehq.

Without d3dx9_36, it prints (to the terminal you start wine from) a ton of messages about not being able to compile a shader program to whichever target Risen is trying to use, and displays only a black screen instead of the main menu.

Do note, as well, that you have to launch it from the bin/ subdirectory (the one the executable is installed into); if you launch it from the base install directory, it'll exit with no explanation. Or at least that's what I'm seeing.

(And now, off to play it more. Just got out of Harbor Town and need to go clean up more bits of the wilderness, as well as do some prospecting now that I'm allowed...)

Feel free to file a bug to Wine bugtracker, so developers could investigate it (if it's something not reported already).

Not sure if this was intended to double as a Risen 2 wine thread, but the procedure holds so far for it as well. Note: I haven't played more than running around for a minute.

I used PlayOnLinux to install it in its own virtual directory. The only added item was the d3dx9_36 which I installed on the assumption that I wasn't going to be able to work around it.

I settled on using the Wine 1.7.4-CSMT version. Earlier versions weren't rendering the foreground elements, and neither did 1.7.10 CSMT (anyone know how the 1.7.x versions got all off with the lower numbers being the most current? 1.7.18 right now) I wouldn't be surprised if a full dx9 install would fix that issue letting someone use a slightly earlier version, but I see no real reason to do that if it's working well the way it is.

The CSMT version was the clear winner, about doubling my fps to something playable. I would guess I was getting something in the twenties and now think I'm hovering at or just below 50 with somewhat mid range settings.

I would also like to mention it took a large amount of time to launch, and any logo vids at the start were rendering black. Once things got started it worked fine, but I sure thought it was bombing out. I also haven't tried the antiwarp thing, so separate mileage warning on that.

***update after playing awhile***
The 1.7.4-CSMT version started crashing on saved game load for some reason. I stepped it up to 1.7.5 and then back down and it started working again. Weird but I guess it's not perfect. Thank God for POL making such a task super easy.

The mouse warp issue is present and annoying as ever. Hurray for such a long standing, game affecting annoyance. I will say it's not as frustrating as it is on some games, but that is about all the good I can say about the issue.

Launching the game is still taking about 20+ seconds to get started, which sucks. Maybe it's that way on Windows too, but probably not.

On the whole it is an OK wine experience, that is almost a good one. It's probably not the best way to play the game if you have the choice, but if you don't, you can still enjoy it, and to be fair, it's hard to find a perfect Wine experience.