Well the console doesn't work :( It opens, but it's black, no text in it, nothing will appear when I type, and any attempts at blindly entering commands (under the hope that it's just the display that is messed up) were in vain.

EDIT: d3dcompiler_43 fixes water and console, also statistics are now visible in gpu benchmark

I have a problem with the mouse in Crysis. Sometimes the mouse seems to be locked and I can turn the sight only a specific angle, not 360 degrees, sometimes it works. I tried to solve that problem by enabeling the function, tying the mouse to the game window, but it didn't help.

Open Winecfg and try enabling the "Automatically capture the mouse in full screen windows" option under the Graphics tab. Might also need to enable the virtual desktop if you haven't already (I haven't tested the game without it).

Can you get the 64-bit binary to run?

wine Bin64/Crysis.exe greets me with a message box saying "Could not launch main application!"

This is in a 64-bit prefix.

I haven't got around to that yet, but try launching the game with "CrysisLauncher.exe" (or "CrysisLauncher.exe -dx9" - this doesn't seem to be necessary though)

Edit: Seems to run at least as well with 64-bit Wine as with 32-bit - start the game from CrysisLauncher.exe as usual and it should work. It's probably best to use 64-bit Wine for this game.

Since fixing the water glitches I've noticed another couple of issues - flickering plants/vegetation (fixed by setting UseGLSL to disabled) and shadows don't appear to work (fixed by setting certain values for r_ShadowTexMap as suggested in this report: https://appdb.winehq.org/objectManager.php?sClass=version&iId=29144 - I set the variable via system.cfg as I already set some other tweaks from the tweak guide).

The launcher does indeed give me the 64-bit binary. Bizarre..

Weird, I haven't seen flickering plants. The lack of shadows went unnoticed as well but that's probably because I had them on Low anyway, as these can drag the framerate down quite a bit.

What I did see though was flickering grass on Windows, when running in DX10 mode. Switching to dx9 fixed that. On Wine I get DX9 automatically.

Probably related to graphics settings - I'm running with everything on high (except motion blur, which is disabled) and the tweaks suggested by the tweak guide for "'Very High' On The Cheap", plus a few other tweaks to stop some pop-in. The leaves on some of the trees and larger bushes have a weird flickering effect without UseGLSL disabled.

Game: Crysis
Installer MD5s:
7836fbf965984c6a6a2b2d9536fc041a setup_crysis_2.0.0.7-1.bin
11eff98e6d9a43ae80a38051a76d5764 setup_crysis_2.0.0.7-2.bin
cb9771a799c476a0bb534cd76e3ccebd setup_crysis_2.0.0.7.exe
WineHQ AppDB link: https://appdb.winehq.org/objectManager.php?sClass=version&iId=10107
CodeWeavers link: https://www.codeweavers.com/compatibility/crossover/crysis

Distro: Linux Mint 18.3 Cinnamon 64-bit
Kernel version: 4.13.0-32
Graphics card: AMD RX 480 8GB
Graphics driver & version: Open source, with Mesa 17.3.2 from Padoka's stable Mesa PPA
Wine version(s) tested: Wine 3.0 64-bit (with CSMT and virtual desktop enabled)

Install notes: Requires d3dcompiler_43 and d3d10 set to "disabled".
If you're using an Nvidia GPU set UseGLSL=disabled or some vegetation will have a flickering effect
For shadows to work, create a file called "system.cfg" in the game's root directory (you'll need to create this file anyway if you plan on doing any manual tweaking) and put this line in it:

r_ShadowTexFormat=1

Start the game from/create shortcut for "Bin64/Crysis.exe"
How well does it run: Almost perfect (DX9 only - DX10 doesn't work)
Details: Looks like this runs more or less perfectly with the Wine settings and tweaks detailed above, however I've only played for about an hour or two so far. If running the game with virtual desktop enabled, you must also set "Automatically capture the mouse in full-screen windows".

I strongly recommend checking out the tweak guide, as Crysis is a game that benefits greatly from manual tweaking of various settings (this is especially true if you have a weaker system & want to get the best graphics quality possible while still maintaining good performance): http://www.tweakguides.com/Crysis_1.html

If you experience certain glitches like water flickering or looking dull at higher settings, missing effects at the water edges etc., try deleting the shader cache (found in "C:\users\$USER\My Documents\My Games\Crysis\Shaders\"). Also do this if you ran the game before installing d3dcompiler_43.

Wine wrapper
I have put together a Linux Wine wrapper for this game. For more information, see the release thread in the game's forum: https://www.gog.com/forum/crysis_series/crysis_and_crysis_warhead_for_linux

Edit: The 64-bit version stopped crashing as of Wine Staging 2.10; new report posted here: https://www.gog.com/forum/general/the_judas_does_this_run_in_wine_thread_v1173/post1173
----
Never mind - Crysis Warhead can no longer be considered playable, as the 32-bit version was removed due to the DRM still being partially intact (and it's looking unlikely that a fixed version will be made available) and the 64-bit version still crashes regularly in Wine. I'll keep re-testing with each new Wine release and will post a new report if/when either the 64-bit version of Wine is fixed or a working 32-bit version is made available.

Dropping by to say thanks to everyone in this thread. I re bought Crysis today to replace the DRM-ed Retail Editions and boy am I impressed with how well the games run with Wine and the performance is pretty good compared to some Windows benchmarks I'm checking.

Game: Painkller: Overdose
Installer MD5s: https://appdb.winehq.org/objectManager.php?sClass=application&iId=6005
d347709b6f89f8263b1a1ebbf46e1214 setup_painkiller_overdose_2.0.0.2-1.bin
0ac8e94ceb82bec04ee7a11051911b0b setup_painkiller_overdose_2.0.0.2.exe
WineHQ AppDB link: https://appdb.winehq.org/objectManager.php?sClass=application&iId=6005
CodeWeavers link: https://www.codeweavers.com/compatibility/crossover/painkiller-overdose
Distro: Mac OS X El Capitain 10.11.6
Kernel version: Darwin 15.6.0 (Build 15G1108)
Graphics card: Intel HD Graphics 5000
Graphics driver & version: OS Default
Wine version(s) tested: WINE 1.9.20/1.9.21/staging-1.9.21/staging-1.9.20 via Wineskin
Install notes: Install the following in winetricks: d3dx9_35

How well does it run: Perfectly. CSMT did work in-game, but yielded some graphical glitches in the menu. Otherwise, the game runs very well, even on low-end hardware such as this.

Game: Call to Power 2
Installer MD5s: setup_call_to_power2_2.0.0.13.exe = ac70ea5806826f31552db82360e477bf
WineHQ AppDB link: https://appdb.winehq.org/objectManager.php?sClass=application&iId=4077
CodeWeavers link: https://www.codeweavers.com/compatibility/crossover/civilization-call-to-power-ii
Distro: Mac OS X Snow Leopard 10.6.8
Kernel version: Darwin 10.8.0 (Build 10K549)
Graphics card: Intel GMA 950
Graphics driver & version: OS Default
Wine version(s) tested: WINE 1.9.20/1.9.21
Install notes: Install the following in winetricks: corefonts; to get cutscenes working properly, install msxml3, and wmp9 in winetricks, followed by the Indeo Video 5 codec package available here: http://www.free-codecs.com/indeo_codec_download.htm

When installing Indeo Video 5, use a custom installation and disable the option to install the Web Browser Plugin. The game was also tested with the Native Mac Driver enabled, and the Apolyton CTP2 Edition: Revision 1111 (12-Jun-2011) open source patch. Due to the considerable bug fixes and enhancements to the base game, playing with this patch is recommended.

If the game is laggy, or if cutscenes are not displaying properly (e.g. black screen, with audio), set ddr=gdi in winetricks.

How well does it run: Almost perfectly. The continuing issue with the Apolyton CTP2 patch is that music does not work (the patch assumes CD audio); a workaround would be to play the tracks in the background using your audio player app of choice.

Game: Deadlock: Planetary Conquest
Installer MD5s: setup_deadlock_2.0.0.11.exe = f2ec16165d442e1d940cf752b12913f1
WineHQ AppDB link: https://appdb.winehq.org/objectManager.php?sClass=version&iId=30677
CodeWeavers link: n/a
Distro: Mac OS X Snow Leopard 10.6.8
Kernel version: Darwin 10.8.0 (Build 10K549)
Graphics card: Intel GMA 950
Graphics driver & version: OS Default
Wine version(s) tested: WINE 1.9.20/1.9.21
Install notes: Set ddr=gdi in winetricks. In winecfg, set the Windows version to Windows 95 and disable wail32.dll. Disabling the Native Mac Driver allows the full game window to be rendered on screen (as opposed to being cutoff due to the native Mac OS X menubar taking up more space on screen).

How well does it run: It runs, with some issues. Disabling wail32.dll is what allows the game to be playable, at the expense of music, and ambient sounds. The problem seems to be with wail32.dll and how it calls on the resources used by the game. More information here: http://forum.galliusiv.com/viewtopic.php?f=4&t=317
(n.b. the replacement wail32.dll linked in the OP of that thread did work, but quickly led to random crashes).

Edit: There is an patch to re-enable multiplayer here: http://forum.galliusiv.com/viewtopic.php?f=4&t=351, but I haven't tested it with the game.

Edit 2: I've run into an occasional issue with the game becoming unresponsive to mouse clicks, especially after I've clicked the "End Turn" button. The only workaround is to periodically save the game, then quit and restart the game. It looks to me like it's caused by the same bug reported here: https://www.gog.com/forum/deadlock_series/deadlock_1_game_locks_up_when_deleting_units_from_the_queue_of_a_city_center

Edit 3: One more issue has just cropped up for me -- some (but not all) radio buttons and other options lose their text label with they are clicked on. It's not a game-breaking bug (IMO) but it is cosmetically annoying.

This probably should be "Deadlock: Planetary Conquest".

How long have you played the game? Did you run into this bug? If so, have you found a workaround for it?

As the game also opens two pop-up windows in other situations, which always leads to a lock up, this bug unfortunately makes the game almost unplayable for me.

Edit: Never mind. I've just updated my system. The bug seems to be fixed with Wine 1.9.20. :)

Yeah, oops. I've corrected the title. I've also updated my entry with my own experience with the bug you describe. I played it all day without any issue at all, and it's just now that I've encountered the game becoming unresponsive to mouse input.