http://bugs.winehq.org/show_bug.cgi?id=31277
Bug #: 31277 Summary: The Witcher 2 (GOG): Blue "Fog" Graphical Bug During Gameplay Product: Wine Version: 1.5.9 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: jedimasterpedro@hotmail.com Classification: Unclassified
Created attachment 41092 --> http://bugs.winehq.org/attachment.cgi?id=41092 In-game screenshot of the bug in question
System Specifications:
OS: Ubuntu Linux 12.04 x86_64 RAM: Corsair Vengeance Blue 8 GB (2X4 GB) PC3-12800 1600MHz DDR3 240-Pin SDRAM CPU: Intel® Core™ i5-2500K CPU @ 3.30GHz × 4 Video: Nvidia GeForce GTX 560 Ti 1GB VRAM @ 822GHz Graphics Driver: Nvidia proprietary binary driver v295.40 for Linux x86_84 Wine Version: 1.5.9, provided by Ubuntu Wine Team PPA
Bug Description:
When attempting to run the full game, The Witcher 2 starts normally, loads into menu screen, and creates a new game without any notable glitches, bugs, or stalls. However, once a new game or tutorial is started, all textures and models in game are surrounded by a blue "fog" that makes the game unplayable. This has been tested on each of the application-provided graphics settings (i.e. Low/Medium/High/Ultra) and using variable permutations of the Nvidia graphics driver settings (e.g. VSync on/off, allow OpenGL flipping, etc.)
A screenshot demonstrating the bug is attached.
How to Reproduce:
1) Download The Witcher 2:Enhanced Edition from GOG (version as of July 21st is 3.2)and install using provided .exe using wine 2) winetricks d3dcompiler_43 (resolved issue with just a black screen on startup) 3) winetricks xact_jun2010 (fixes issue with no keyboard input in game) 4) run bin/Configurator.exe to adjust settings 5) Download/install http://en.thewitcher.com/dotnet/ patch to avoid .NET 4.0 crash 6) run bin/witcher2.exe to start game
The game, configuration, installer, etc. all run fine otherwise.
Notes:
While searching for this bug, I noted that a number of ATI users in Windows were experiencing something like this bug, and the solution for them involved disabling driver settings that override application settings. This was attempted using the Nvidia proprietary driver configuration utility, but the bug remained.
Thank you.