It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Has anyone installed Alan Wake on WINE yet? I've heard it works, but thought I'd ask for opinions.
avatar
andrew84uk: Has anyone installed Alan Wake on WINE yet? I've heard it works, but thought I'd ask for opinions.
Trying it now for Linux (no Mac sorry) and having mixed results. I'm having issues getting the mouse and keyboard to work which has been something of a chronic issue since I started using wine 1.4. The game starts and the environments seem to be working. I'm quite shocked how well it looks like it will run if I can get it going. Thought my system wasn't up to snuff but I may been wrong.

The sound also isn't working so far. Not giving up on it yet.

Currently no sound, not keyboard /mouse, but title and intro look good.
Wine 1.4 no tricks or overrides of any kind.

***edit
sounds like getting it to work requires the "raw3.patch" which generally requires rebuilding wine from the source. Once it works it sounds like the in game performance may be lacking, and sound is various shades of iffy. Not sure its viable at this time.
Post edited May 13, 2012 by gooberking
OK here is the deal as of wine 1.5.4 on linux

Installing works fine. Launching the game works fine.

To get the controls to work you must use the raw3.patch which can be done in one of two ways.
You can copy a precompiled version available from the PlayOnLinux guys and overwrite an existing install(I didn't do this.) Or you have to do it the serious way and build wine from the source using the patch.

Which basically boils down to downloading the source, copying the patch into the source directory, apply the patch (patch -p1 < raw3.patch), then build and install wine via the usual build from source routine. After that the controls should work. Note I am currently unsure what effect the patch may have on other games, if any.

After that the game should run HOWEVER, actual game play does suffer some serious performance issues which is strange given that the title, menus, and scenic fly-bys all work fantastically(This may just be because the night time effects are far more demanding). This unfortunately renders the game more or less unplayable at this time.

Also the sound seems to go in and out between sections. So you will have sound for a while, then it goes out for awhile. Sound is quite important for the game if you have never played it, so even if there is a way to fix the performance issue(which I thought might have been the motion blur effect but using -noblur does not help) the sound is still a serious hurdle.

Bottom line, if you want to play Alan Wake anytime soon, you better have windows or an Xbox.

***Patch
A patch was release for our version of the game. I have not been able to install this patch via wine to see if any of the new options might improve the situation. The main game installer will probably be updated to reflect the patch, but I am unwilling to redownload the 8gigs worth of installer files in order to see what happens. As it stands it would be good if someone downloading the game after 6-15-2012 could post their A.L. wine experience as mine may not reflect the current situation.
Post edited June 15, 2012 by gooberking
avatar
gooberking: OK here is the deal as of wine 1.5.4 on linux

Installing works fine. Launching the game works fine.

To get the controls to work you must use the raw3.patch which can be done in one of two ways.
You can copy a precompiled version available from the PlayOnLinux guys and overwrite an existing install(I didn't do this.) Or you have to do it the serious way and build wine from the source using the patch.

Which basically boils down to downloading the source, copying the patch into the source directory, apply the patch (patch -p1 < raw3.patch), then build and install wine via the usual build from source routine. After that the controls should work. Note I am currently unsure what effect the patch may have on other games, if any.

After that the game should run HOWEVER, actual game play does suffer some serious performance issues which is strange given that the title, menus, and scenic fly-bys all work fantastically(This may just be because the night time effects are far more demanding). This unfortunately renders the game more or less unplayable at this time.

Also the sound seems to go in and out between sections. So you will have sound for a while, then it goes out for awhile. Sound is quite important for the game if you have never played it, so even if there is a way to fix the performance issue(which I thought might have been the motion blur effect but using -noblur does not help) the sound is still a serious hurdle.

Bottom line, if you want to play Alan Wake anytime soon, you better have windows or an Xbox.
Thanks for your response, sounds like it's best to use Bootcamp for the meantime at least :)
Someone made mention that American Nightmare seems to run significant;y better than the original game does(here in the forums somewhere.) This makes me quite curious if American Nightmare might preform better using wine than the original game. I'm not currently interested in buying two games I can't play, but I would love to hear any feedback from anyone able to confirm the speed improvements and find out if anyone has tried American Nightmare using wine.

If there were improvements I would also be curious to know if the shaders used in the game
(/Alan Wake/shaders/build/pc/ ) have been revised (byte count differences.)
Update as of Wine 1.6 (using wine appdb recommended extras like d3d9)
Not much has changed for Alan. One thing that has is now the need to install a patch just to get the controls to work is apparently taken care of. So the game more or less installs, and plays without anything being “technically wrong.” Which isn't to say the game is very playable.

The two big problems are hold overs from earlier wine versions. First is the sound issue. Sound works sometimes and then toggles in and out. The trigger seems to be cut scenes where suddenly the sound is gone after it was working fine. Later another might kick the sound back in, but the bottom line is you have it for awhile then you don't. This is a big, big problem for this game given it's so story driven. Depending on who you are this may be the big deal breaker.

The second issue is the horrible performance. I got an OK rig which is giving me about 15FPS which is kinda playable if one reeeally wanted to suffer that way, but it isn't anywhere near what it should be. It's actually a frustrating problem because the cinematics all run like butter (even on my old card) but as soon as the game goes into play mode something changes and the performance craters.

If someone had a screaming fast video card then it's conceivable that they could get enough FPS to make the game playable, but the sound issue could still ruin the whole thing. For a reference point my card is a Geforce GTX 650 Ti. I'm guessing a card with twice the speed might get things playable, but even then I doubt it's going to run half as good as the console version does. And don't even think of trying it on something less. My last card was giving me about 1-2FPS.

Since this game has gone on sale everywhere lately I think it's safe to say a large percentage of the gaming world has this game somewhere, so it would be great of someone was able to iron out what is weighing the game down. Have to do some more waiting to see if that ever happens.

One last note is that all of this is valid for American Nightmare. I did not see any behavior differences between the two.

****edit. Update as of 5-29-2014****
Tried with some of the newer wine builds, and using CSMT versions. GOG had updated their installer, with a newer version I believe, so I used it.

Performance was tolerable. I'm not sure if it was wine, or the game build, but It didn't seem so bad this time around. I could see it being playable for someone with a high end card, and I probably wouldn't be all out against it as it was if I wasn't such a FPS junkie. That, said because I played further into the game this time, I ran into a flat out wall. Once you get the flashlight, the game is over. The screen ends up with a big white blob and nothing else to see. Total game death on that one. Thinking it's time to give up on ol' Alan for good.
Post edited May 29, 2014 by gooberking