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

×
high rated
I've put together Wine wrappers for Crysis and Crysis Warhead, allowing them to be played on Linux almost like native games & with no Wine knowledge required (note that these games only support DX9 mode at present and are both 64-bit only).

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/crysis and ~/.local/share/crysiswarhead

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

crysis_wine.tar.xz
(35.4 kB, SHA256: 22c2e41b780ef4894627d91f4ef5e12faf4d85d79097f3efcc132c02fc99bfb0)

crysis_warhead_wine.tar.xz
(41.9 kB, SHA256: f9296f9c31224a044b95a9350a8acbd5b2c751ed49dd8ceddb3afb99e62e1abd)

Updated 2019/09/14: Updated winewrap.shlib. Updated DXVK to 1.3.4.

The wrappers use Wine 4.0 and DXVK 1.3.4. Wine and Winetricks will be downloaded automatically if not present; to avoid redownloading for other scripts the downloaded Wine package will be stored in ~/.cache/winewrap

It is crucial to have updated graphics drivers for this if you want to use the DX10 renderer. For the open drivers, make sure to have a recent kernel and Mesa 18.3 or newer. For Nvidia GPUs, driver version 415.x or newer is required. You may also need to enable DRI3 support if it has not already been enabled on your system. Check the terminal output first if there are any problems.

I haven't done a full playthrough of either yet but both seem to run great so far. If anyone runs into any 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.

Multiplayer has not been tested and may or may not work.

I strongly recommend checking out the tweak guides for these games:

Crysis
Crysis Warhead

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


Additional notes:


-You can enable DXVK's framerate display by setting the environment variable: DXVK_HUD=fps
If you want to create a shortcut to start the game with this set then use these arguments for the shortcut:

env DXVK_HUD=fps %command% play

- Additional packages may be necessary to enable Vulkan support on your system, e.g.: libvulkan1 and libvulkan1:i386
Users of the open graphics drivers may also need to install mesa-vulkan-drivers and mesa-vulkan-drivers:i386
Post edited 2 days ago by adamhm
Thanks again!
It's good that you can get these games to work but this is the reason I don't use Linux. No way am I going through that when I can just use Windows.
Going through what?

Step 0 [only if you don't already have Wine's dependencies installed already]: Install Wine (or just Wine's dependencies)

Step 1: Put the files in one place
Step 2: Run the build script
Step 3: Move the game dir to where you want it (if it's not there already) and run the start script to play/create shortcuts/etc
avatar
Magmarock: It's good that you can get these games to work but this is the reason I don't use Linux. No way am I going through that when I can just use Windows.
The point with adamhm's wrappers is to make the process very simple, like how GOG does for old games with DOSBox/ScummVM and the settings and such prepared in a script that runs automatically. Of course, to make it EVEN easier, it could check for said dependencies for you.
Do you have an issue with a battery indicator being displayed in the top-right corner? At first I thought it was part of the game UI, but it's on-screen 100% of the time (during cutscenes etc.) and it turns out the game is actually showing a laptop battery indicator. I found a few posts about this on the web, and it's perhaps not directly a Wine problem since the affected people seemed to be using Windows...but I'm on a desktop, and there shouldn't be a reason for it to be there. So it seems like there may be something in Wine causing this. There's evidently a way to turn the battery indicator off, but the one and only actual answer I could find was a link to a Crysis forum that's now dead. (Tried the wayback machine but the forum posts aren't archived.)
That doesn't occur here, and I don't recall seeing a battery indicator when testing on the other systems either (all desktops). You could try looking up the game's config options and/or console commands to see if there's a way to turn it off?
Yeah, already checked that. You can disable the GUI, but the battery indicator stays. There's an IntelLaptopGaming DLL in the Crysis folder, which I'm sure is directly related to it, but removing it just causes an error. Thank you for the reply though...so it's just me (and a few other unlucky people), it seems. ;)
Hi
Awesome script for Crysis!
I am a little worried about future proofing though. I see that the script is pulling in a lot of external dependencies. With that in mind, would you mind documenting the steps you used to get Crysis working?
Thanks again!
avatar
shsorbom: Hi
Awesome script for Crysis!
I am a little worried about future proofing though. I see that the script is pulling in a lot of external dependencies. With that in mind, would you mind documenting the steps you used to get Crysis working?
Thanks again!
https://www.gog.com/forum/general/the_judas_does_this_run_in_wine_thread_v1173/post458

Also all dependencies downloaded by my wrappers are cached in ~/.cache/wine, ~/.cache/winewrap and ~/.cache/winetricks if you want to make backups for future use :)
Thank you!
Hi adamhm.

Can we get an updated to DXVK 1.1 installer for Crysis 1?
avatar
CreepingDeath1907: Hi adamhm.

Can we get an updated to DXVK 1.1 installer for Crysis 1?
Since it depends on a Vulkan extension that requires at least Wine 4.5 and beta graphics drivers (and without them may perform worse than older versions of DXVK) I'm going to hold off on that for now - I'll look into updating all Wine+DXVK wrappers to use Wine 4.10 when that's released, along with whatever the latest version of DXVK is at that time.

In the meantime, you can try it yourself if you want by using the argument "-winever=4.8" to have the build script create the wrapper using Wine 4.8 and then using the start script's advanced options menu to update DXVK (download DXVK from https://github.com/doitsujin/dxvk/releases first, then use the update option & select the downloaded DXVK archive).
Thank you for providing these scripts for Wine and even adding DXVK
Are there any particular overrides you are using in Wine Config?

I just tested the GOG version of FarCry 2 Fortune's Edition and DXVK ran perfectly! I was able to run everything on high and some settings on Very High.

Doesn't FarCry 2 run on the same engine as Crysis and Crysis Warhead?