Installing, copy protection, gameplay, cutscenes
What does not
What was not tested
Game was tested on a fresh wineprefix. In winecfg, under Libraries, disable d3dx11_42. No dll overrides are required. You don't need a crack. If the DVD drive is added in winecfg as a windows drive, the game should work (The DVD drive is autodetected, so you shouldn't need any changes). The game still exhibits flickering black grass on Full Dynamic Lighting setting and above. This is quite an old issue with S.T.A.L.K.E.R. games. The rating is Gold because a change in winecfg is still required (all other testers marking this Platinum aren't using the rating system correctly). Test system: CPU: AMD FX-8350 GPU: AMD HD 5670 (Catalyst 13.11 beta drivers) RAM: 8 Gb RAM
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Ubuntu 15.10 "Wily" amd64 (+ variants like Kubuntu)||May 08 2016||1.9.9||Yes||Yes||Gold||Jonathan Geddes|
|Show||Mac OS X 10.9 "Mavericks"||Oct 19 2015||1.7.53||Yes||Yes||Gold||Sam|
|Show||Ubuntu 14.04 "Trusty" amd64 (+ variants like Kubuntu)||Oct 21 2015||1.7.52-staging||Yes||Yes||Gold||Josep|
|Show||Ubuntu 14.04 "Trusty" amd64 (+ variants like Kubuntu)||Dec 08 2014||1.7.31||Yes||Yes||Gold||an anonymous user|
|Current||Arch Linux x86_64||Nov 01 2013||1.7.5||Yes||Yes||Gold||Alexander Borysov|
|Bug #||Description||Status||Resolution||Other apps affected|
|6971||Mouse "escapes" window or is confined to an area in the full screen program||CLOSED||FIXED||View|
|16580||S.T.A.L.K.E.R: sky not redrawn correctly with dynamic lighting||CLOSED||FIXED||View|
|23089||Grass rendering bug in S.T.A.L.K.E.R clear sky/call of pripyat||CLOSED||FIXED||View|
|29744||STALKER-SoC/CoP hangs at splash screen due to OpenAL32||CLOSED||INVALID||View|
Note that users running this game in older WINE versions have experienced mouse issues among other problems. It is strongly advised that you use either the latest stable version of WINE (Currently 1.4.0) or the latest development release.
Also note that to running the game must be done in the following fashion:
The game will fail to launch if you use WINE to run executable from within the bin folder.
Getting WINE ready:
Just install WINE from your distribution's package manager, be it apt-get, yum, pacman or something else. The newer the WINE version, the better.
Winetricks is another immensely helpful tool when working with wineprefixes, if your distribution doesn't package it, you can get it here.
Once that's out of the way, continue on to installing the game.
Installation: Steam Version
Right now, you don't need any dll overrides, just run:
winetricks --no-isolate steam
and after updating Steam, you can install Call of Pripyat just fine. If you're using a wineprefix other than the default "~/.wine", then you need to add your wineprefix to the command:
WINEPREFIX=~/.path/to/wineprefix winetricks --no-isolate steam
Installation: Retail/Physical Version
Set up a fresh wineprefix and run the DVD installer. Right now, it is unknown exactly which dll overrides are needed (if any) due to lack of recent test data. If you are having trouble, use winetricks to install d3dx9 and ffdshow.
If your game is crashing on startup, disable the d3dx11 dlls. Change directory to your 'windows/system32' folder within your wine prefix and run:
mv -v d3d11.dll d3d11.dll.DISABLED
mv -v d3dx11_42.dll d3dx11_42.dll.DISABLED
Running the Game
Launch the game (NOT from the bin folder, run command one level above).