http://bugs.winehq.org/show_bug.cgi?id=60406 Bug ID: 60406 Summary: FEAR 2 has severe color corruption and very dark rendering with WineD3D/OpenGL on new WoW64 and proprietary NVIDIA Product: Wine Version: 10.18 Hardware: x86-64 URL: https://www.moddb.com/games/fear-2/downloads/f-e-a-r-2 -project-origin-demo OS: Linux Status: NEW Keywords: download, regression, wow64 Severity: normal Priority: P2 Component: opengl Assignee: wine-bugs@list.winehq.org Reporter: gyebro69@gmail.com CC: jacek@codeweavers.com Target Milestone: --- Regression SHA1: a2906847c0c94c119b74c94f0fc606ca9e9f140d Distribution: ArchLinux Created attachment 82207 --> http://bugs.winehq.org/attachment.cgi?id=82207 corrupted screen F.E.A.R. 2: Project Origin, a 32-bit Direct3D 9 game, has severe rendering corruption when using WineD3D's OpenGL renderer in the new WoW64 mode with the proprietary NVIDIA driver. The image has heavily distorted, bright colors. After switching away from the game with Alt-Tab and returning to it, the bright color distortion disappears, but the image remains much too dark. Loading another level brings the color distortion back.The graphical corruption in the game may change between runs rather than remaining constant: orange hues dominate in some instances, and blue in others. Changing graphical settings between low and maximum has no effect on the graphical corruption. The problem is reproducible with the new WOW64 mode with multiple proprietary NVIDIA driver versions, including 595.x and 615.71.09. It does not occur with Nouveau/Mesa 26.2.3. in WOW64 mode. The problem is independent of the window-system and OpenGL platform paths I tested: X11 /XWayland / native Wayland EGL and legacy GLX The results of the tests: Wine 10.17, new WoW64: correct rendering but slow performance Wine 10.18, new WoW64: corrupted rendering, performance is good Old shared-WOW Wine-11.18 build: correct rendering New WoW64 with Nouveau/Mesa: correct rendering New WoW64 with proprietary NVIDIA and DXVK's d3d9.dll: correct rendering New WoW64 with proprietary NVIDIA and WineD3D/OpenGL: corrupted rendering Setting strict_shader_math=0x1 does not change the problem. I bisected the regression. The first bad commit is: a2906847c0c94c119b74c94f0fc606ca9e9f140d opengl32: Support wow64 buffer storage and persistent memory mapping using Vulkan. With the parent commit, the game is very slow, but the image is rendered correctly. With a2906847c0c94c119b74c94f0fc606ca9e9f140d, the performance is good and the rendering corruption appears. The regression commit is also the commit that was intended to address the general new-WoW64 OpenGL performance problem from bug #55981. I also reported a separate proprietary-NVIDIA/new-WoW64 performance problem as bug #60354. However, this report concerns a reproducible rendering-correctness regression rather than reduced performance. I also tested the following later commit: b22af9f012e973c34aed781bdcf81d03d408de03 opengl32: Use Vulkan-backed buffer storage only when GL_MAP_PERSISTENT_BIT is specified. The rendering corruption is still present with that commit. This suggests that the affected path uses persistent mapped buffers and that limiting the Vulkan-backed implementation to GL_MAP_PERSISTENT_BIT does not resolve the problem. fear2demo.zip (1.76 GiB) md5: 4a527bdf4e8b3cc6f95cf34e9cd47838 wine-11.18-287-gabc6aebd55b NVIDIA GeForce GTX 1660 SUPER with driver 615.71.09 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.