Ok, so it looks like there are more cases where the game may get locked up. But at least the main problem I run into seems to be fixed now.

Have been taking a closer look at the 64-bit version of Crysis Warhead due to the issues with (and subsequent removal of) the 32-bit version. The crash occurs very quickly - just start a new game and start playing through the first level & it'll occur soon enough.

I've tried a number of different versions of Wine and Wine Staging but have had no luck so far (Wine 1.8.5 was more stable but the issue still occurred - it just took a bit longer). Abusing quicksaves also seems to make it happen more quickly.

When it happens the game freezes, with any currently playing sound and music continuing to play. Running the game with Wine debug mode enabled the last line(s) in the log are always something along the lines of:

fixme:faultrep:ReportFault 0x298cfe0 0x0 stub
fixme:faultrep:ReportFault 0x23b250 0x0 stub

What's before the reportfault?

Can you run the thing under gdb? It might catch the segfault if there's one happening. And then you could get a backtrace.

you'll need to post a bit more from the log to get something useful out of it ;). Those two fixmes are already after the crash happened.

some googling turns up this wine bug: (closed as WONTFIX)
https://bugs.winehq.org/show_bug.cgi?id=18799
might be worth to try the patch posted there

it seems PlayOnLinux provides a wine version with this patch already applied
see this guide here: (ignore the part about installing through origin)
http://www.gamersonlinux.com/forum/threads/crysis-warhead-guide.590/

From what I can see, the messages beforehand are little different to the 32-bit version (which doesn't crash and seems to work perfectly, aside from the issues with the not-fully-removed DRM). Lots of these:

fixme:d3d:buffer_internal_preload Too many declaration changes or converting dynamic buffer, stopping converting.
fixme:d3d_draw:draw_primitive_immediate_mode Instancing not implemented.
(tons of the last one)

32-bit also has lots of "fixme:d3d:wined3d_texture_set_lod Waiting for cs." lines while the 64-bit version doesn't


That's for the original Crysis, which does seem to work perfectly with current versions of Wine (both 32 and 64-bit)


I think that patch may have already been added to Wine some time ago. Also the version specified in that guide is 32-bit only - the 32 bit version of Crysis Warhead runs perfectly fine; it's just the 64-bit version that has this problem. Unfortunately the 32-bit version didn't have the DRM fully removed & is no longer available as a result, and there is a lot of uncertainty as to whether a DRM-free 32-bit version will ever be provided.

The appdb entry for Warhead mentions needing the patch as well ...
but you're right, the patch got merged shortly after 1.8. Somehow the bug entry doesn't mention that.

Thanks for the reports. All entries need to be in a separate post. If you could copy/paste this one, thanks.

Game: Deadlock II: Shrine Wars
Installer MD5s: setup_deadlock2_2.0.0.2.exe = 767db22ea4fe45325b12ce43ca7432f9
WineHQ AppDB link: https://appdb.winehq.org/objectManager.php?sClass=application&iId=4833
CodeWeavers link: https://www.codeweavers.com/compatibility/crossover/deadlock-ii-shrine-wars
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, and install directplay (also through winetricks). In winecfg, set the Windows version to Windows 95. Out of the box, the game will not work unless the WINE/Windows 8 patch hosted at GalliusIV.com is applied: http://forum.galliusiv.com/viewtopic.php?f=4&t=357

If the patch is not applied, the intro cutscene does work, but as soon as the mouse cursor is moved, the menu screen immediately turns black.

The aforementioned patch basically downgrades the game from 1.2 to the original 1.00, and there is no access to the map editor.

How Well Does It Run: The game runs fine (so far) with saving/loading working fine. Music and in-game sounds also work. The game is unfortunately hard locked at 800 x 600 (unlike Deadlock 1), so resolution switching isn't supported.

I haven't encountered any other UI or black screen issues so far, but I will update this entry if anything comes up.

Game: Medal of Honor: Allied Assault Warchest
Installer MD5s:
setup_medal_of_honor_2.0.0.21.exe = 2f5dd640b3994d67fc71995b743cb22c
setup_medal_of_honor_2.0.0.21-1.bin = 3030b7213476b14fe52719083792d6ff
setup_medal_of_honor_2.0.0.21-2.bin = a5538ad0837208b065cd8b10229ba717
WineHQ AppDB link: https://appdb.winehq.org/objectManager.php?sClass=application&iId=662
CodeWeavers link: https://www.codeweavers.com/compatibility/crossover/medal-of-honor-allied-assault
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.21

Install notes: No winetricks, or adjustments in winecfg/regedit are necessary -- it just works, as expected for most games based on the Quake 3 engine (and from its own AppDB entry).

How Well Does It Run: Perfectly, even on an archaic 32-bit Core Duo Mac with the notorious GMA 950, with the proper settings (and the player's expectations) adjusted accordingly. For widescreen resolutions, edit the unnamedsoldier.cfg and newconfig.cfg files, as per the instructions here: [url=http://pcgamingwiki.com/wiki/Medal_of_Honor:_Allied_Assault]http://pcgamingwiki.com/wiki/Medal_of_Honor:_Allied_Assault[/url]

Game: Medal of Honor: Pacific Assault
Installer MD5s:
setup_medal_of_honor_-_pacific_assault_1.2_(gog-3)_[7140].exe = 5ea964dbd15436e2248a74c4f77f6e7b
setup_medal_of_honor_-_pacific_assault_1.2_(gog-3)_[7140]-1.bin = b54d183a2e480fbf685619d0d2a40e51
WineHQ AppDB link:
https://appdb.winehq.org/objectManager.php?sClass=application&iId=5257
CodeWeavers link: https://www.codeweavers.com/compatibility/crossover/medal-of-honor-pacific-assault
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 via Wineskin

Install notes: No winetricks or edits in regedit/winecfg were necessary.

How well does it run: Not quite perfectly, when tested with the Native Mac Driver enabled (GLSL was disabled to deal with error messages in the wine log). CSMT does work in-game, but yields some glitches during the loading screens. Overall performance is quite good with no significant glitches, though I am currently on the starting level. For reasons unknown to me at the moment, turning the model detail to anything above "low" in the setup .exe leads to a black screen after the EA logo movie. I'm betting it's due more to issues with my graphics hardware.

The game also seems to flood the wine log with a veritable tsunami of profanity. For example: Some kind of strange anti-piracy measure left over from when this game had DRM? I honestly have no clue (but I am greatly amused).

What version(s) of WINE did you test? Did installing any winetricks somehow help?

If I seem aggressive, it's only because I really want to play this game.

How many of those have you tried in chat (assuming it has in-game chat)?
I was wondering about this game. Looks like I will hold off on this for now.

Game: Oddworld: Abe's Oddysee
Installer MD5: c22a44d208e524dc2760ea6ce57829d5 setup_abes_oddysee_2.0.0.4.exe
WineHQ AppDB link: https://appdb.winehq.org/objectManager.php?sClass=application&iId=234
CodeWeavers link: https://www.codeweavers.com/compatibility/crossover/oddworld-abes-oddysee

Distro: Linux Mint 18 Cinnamon 64-bit
Kernel version: 4.4.0-45
Graphics card: Nvidia GeForce GTX 750Ti
Graphics driver & version: Proprietary 370.28
Wine version(s) tested: Wine Staging 1.9.22 via PlayOnLinux, CrossOver 15.3.1

Install notes: Install & play.
If using PlayOnLinux, run the game from/create a shortcut for "AbeWin.exe"
How well does it run: Perfect
Details: Have only played for a short time but all seems to work fine. Tested with virtual desktop enabled.