Good news, the long standing Witcher bug is fixed now: https://bugs.winehq.org/show_bug.cgi?id=34052

Wasn't that fix actually commited back in Wine 1.9.5?
I thought it was considered fixed with the registry switch?

I assumed it's no longer needed as the release notes don't mention it & only say that it was fixed (plus the registry key was introduced with Wine 1.9.5)... and also because I noticed that Saints Row 3 no longer requires it to be set either (I was able to get SR3 running before by enabling both StrictDrawOrdering and CheckFloatConstants but performance was terrible and it still had rendering issues; as of Wine 1.9.10 neither registry keys are required but performance is still worse than the official VP port & the player character still doesn't render properly). I guess I'll have to test it to make sure.

I just reinstalled & retested it with Wine 1.9.11, you were right. It seems odd not to mention such an important detail though (and to not mention it in the notes for the patch when it was actually implemented)... oh well. Anyway, I've played it for a little while & updated the report (using 1.9.10-staging as 1.9.11-staging isn't available yet).

Game: FEAR 2: Project Origin + Reborn
Installer MD5s:
99e9a4e44d869ecb522523c4b461ad5d setup_fear2_ultimate_2.0.0.3-1.bin
ddca2ae75004bafc4eaab78e72372c30 setup_fear2_ultimate_2.0.0.3-2.bin
18e9c0436b01998eaf1de189ed9ae04a setup_fear2_ultimate_2.0.0.3-3.bin
6dffe2911cbfb238e5016b98bcf6dd3e setup_fear2_ultimate_2.0.0.3-4.bin
72107a1df22f5a5414e59e4b813c9633 setup_fear2_ultimate_2.0.0.3.exe
WineHQ AppDB link: https://appdb.winehq.org/objectManager.php?sClass=application&iId=9086
CodeWeavers link: https://www.codeweavers.com/compatibility/crossover/fear-2-project-origin

Distro: Linux Mint 17.3 Cinnamon 64bit
Kernel version: 3.19.0-58
Graphics card: Nvidia GeForce GTX 750Ti
Graphics driver & version: Proprietary 364.19
Wine version(s) tested: Wine Staging 1.9.10 via PlayOnLinux, CrossOver 15.1.0

Install notes: Requires d3dx9_36 and xact (Install DirectX 9 Modern in CrossOver)
If using PlayOnLinux, run the game from/create a shortcut for "FEAR2.exe"
How well does it run: Almost perfect aside from some sound issues
Details: The only issue I've encountered so far is that sounds occurring directly in front of or directly behind the player are almost silent, otherwise the game appears to run perfectly. Tested with virtual desktop and CSMT enabled.

I've tested some different Wine versions and the sound issue started occurring from Wine Staging 1.7.40 (or 1.7.44 for regular Wine) as it does not occur with Wine 1.7.43 / Wine Staging 1.7.39 and earlier, however the game has some rendering issues with those older versions of Wine.

The code blocks from the initial commit adding the fix haven't changed. Unless some other commits fixed this as a side effect which would be unlikely from what I understand of the bug. Thanks for confirming you do need the registry switch.

I certainly would think they should mention the CheckFloatConstants registry key. It hasn't even been added yet to the Useful Registry Keys page.

I've found it. :)

Looks like the GOG version is a bit different. It has separate programs (and no tabs) to set the language (SBLang.exe) and the renderer. The program to configure the renderer is hidden under data (data/HWDialog.exe). I don't know why this has been separated and moved into the data folder. Also the button to start the game directly from HWDialog.exe is grayed out and does not work.

But the video driver already had been set to "Software", so no change there, the game still stops at the title screen. I also have tried the DirectX 6 and 7 modes, always the same behavior.

So I'll wait for wine 1.9.10. ;)

As a matter of fact, I do own another gamepad: an old Netway PS3 clone. But I don't really know whether it supports DirectInput or Xinput, and its mini-manual doesn't say.

I've tried installing its driver, and even overriding the dinput8, xinput1_3, and xinput9_1_0 libraries with winecfg, to no avail. Unless someone has another idea I think I'll just give up... After all, it's not as if I didn't have an enormous backlog of native Linux games (including some really good platformers in it)! :P

Anyway, thanks again for your help!

I just wanted to add my own comments from my attempts to run this in OS X:

I tested this in 1.9.11; the game runs fine in Software mode, but with graphic acceleration the menubar is visible, and the game window loses mouse focus, even in fullscreen. With the Mac driver enabled, the graphics flicker and the title screen/menu screen is still visible during play.

Just tried The Incredible Adventures of Van Helsing: Final Cut. I started the game with a hunter and seems to work. I installed the game on a (naturally) 32-bit clean prefix. Selected Windows version is XP.
The installer took some time and there were the usual failure messages at the end, but game's installation was successful.

The game does not launch with the version of Visual C++ installed by the GOG installer. It needs to force install vcrun2010 (as it appears installed already)
winetricks --force -q vcrun2010

For me it started without sound. To fix the problem install directx from the game's InstallUtils folder:
~/.wine/drive_c/GOG Games/The Incredible Adventures of Van Helsing - Final Cut/InstallUtils/DirectX/DXSETUP.exe
(First I tried through winetricks, but the problem persisted).

I haven't installed the high textures pack.

EDIT: Conforms to preferred post format! :-)

I played yesterday for an hour and the game runs fine.
I had an overheating VGA issue (the laptop turned off), but it has to do with my hardware and OS.
On FreeBSD my card is about 5 degrees (Celsius) hotter than on Linux when idle. It's not a problem in general, but in games things must be getting really hot!

Thanks for the report. Could you add your GPU & OpenGL info to your post? See here for the preferred post format. 2nd post updated.

Game: The Incredible Adventures of Van Helsing: Final Cut
Installer MD5s:
7ca973cd729b14374c1b850ca2f9daed setup_van_helsing_final_cut_2.0.0.5-1.bin
06fdbebee3bb0c2b25641a5c8413d9af setup_van_helsing_final_cut_2.0.0.5-2.bin
160967217ba0e1adc2a5864d3686c891 setup_van_helsing_final_cut_2.0.0.5-3.bin
eaa65b2aef558d97e9c36ae07c1fc615 setup_van_helsing_final_cut_2.0.0.5-4.bin
1bebc99131392f818b4c776f4ca920a7 setup_van_helsing_final_cut_2.0.0.5-5.bin
00c2d12a35211d7261ef64463a19b29b setup_van_helsing_final_cut_2.0.0.5.exe
WineHQ AppDB link: (none yet)
CodeWeavers link: https://www.codeweavers.com/compatibility/crossover/the-incredible-adventures-of-van-helsing-final-cut

Distro: Linux Mint 17.3 Cinnamon 64bit
Kernel version: 3.19.0-58
Graphics card: Nvidia GeForce GTX 750Ti
Graphics driver & version: Proprietary 364.19
Wine version(s) tested: Wine Staging 1.9.10 via PlayOnLinux, CrossOver 15.1.0

Install notes: Requires xact (install DirectX 9 Modern in CrossOver)
If using PlayOnLinux, run the game from/create a shortcut for "VanHelsing.exe"
How well does it run: Perfect
Details: All seems to run perfectly but I have only played the game for a short while so far, using the OpenGL renderer and max settings (but did not test the textures DLC - haven't downloaded that yet). Tested with virtual desktop and CSMT enabled (not that CSMT will make much difference using OpenGL).

Looks like it will happen.

Game: Homeworld Remastered Collection
Installer MD5s:
92075cc44693fd89cbed74bbb09b61f8 setup_homeworld_remastered_2.0.0.15-1.bin
0bcb74c6dcc6c83571bb27b00454d6b8 setup_homeworld_remastered_2.0.0.15-2.bin
be5fa788f67690383c74972776f7b950 setup_homeworld_remastered_2.0.0.15.exe
WineHQ AppDB link: https://appdb.winehq.org/objectManager.php?sClass=application&iId=16784
CodeWeavers link: https://www.codeweavers.com/compatibility/crossover/homeworld-remastered

Distro: Linux Mint 17.3 Cinnamon 64bit
Kernel version: 3.19.0-58
Graphics card: Nvidia GeForce GTX 750Ti
Graphics driver & version: Proprietary 364.19
Wine version(s) tested: Wine Staging 1.9.10 via PlayOnLinux, CrossOver 15.1.0

Install notes: Requires dotnet40 (install Microsoft .NET Framework 4.0 in CrossOver)
If using PlayOnLinux, run the game from/create a shortcut for "Launcher.exe"
How well does it run: Perfect (remastered versions only)
Details: Have only played through the tutorials and starting new game but it seems to work perfectly so far.

The classic versions of Homeworld and Homeworld 2 both seem to work ok too, but I had to start Homeworld.exe directly with the command line parameter /noglddraw otherwise it would fail to launch with the error: "couldn't initialize default rendering system". Homeworld Classic also seems to hang on exit if CSMT is enabled.

Tested with virtual desktop enabled.