http://bugs.winehq.org/show_bug.cgi?id=16348
Summary: GL_INVALID_OPERATION (0x502) from glUniform4fvARB() @ glsl_shader.c Product: Wine Version: CVS/GIT Platform: PC URL: http://pouet.net/prod.php?which=28479 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: t.artem@mailcity.com
Created an attachment (id=17661) --> (http://bugs.winehq.org/attachment.cgi?id=17661) fr-052_platinum.exe
Gazillions of
fixme:d3d_shader:shader_glsl_load_constants >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glUniform4fvARB @ glsl_shader.c / 429 fixme:d3d_shader:shader_glsl_load_constantsF >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glUniform4fvARB() @ glsl_shader.c / 266
errors when running this application (1024x768; no full screen; don't wait for VSync).
At other resolutions or/and parameters it might crash.
http://bugs.winehq.org/show_bug.cgi?id=16348
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #1 from Vitaliy Margolen vitaliy@kievinfo.com 2008-12-05 19:21:58 --- fixmes are not bugs on their own.
http://bugs.winehq.org/show_bug.cgi?id=16348
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #2 from Vitaliy Margolen vitaliy@kievinfo.com 2008-12-05 19:22:06 --- Closing invalid
http://bugs.winehq.org/show_bug.cgi?id=16348
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|directx-d3d |-unknown Version|CVS/GIT |unspecified
http://bugs.winehq.org/show_bug.cgi?id=16348
causality M8R-gepdgu@mailinator.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |M8R-gepdgu@mailinator.com
--- Comment #3 from causality M8R-gepdgu@mailinator.com 2009-11-02 12:58:32 --- Unlike every other "fixme" I have ever seen, this issue really does make it impossible to use any Direct3D applications. When this issue occurs, the WINE application is a solid black window with no graphics and no text at all. You can hear background music and other sounds because the application is otherwise running. The game Bioshock, for example, plays a chime when you navigate the game menu and you can hear this when you press arrow keys, but you cannot see the menu. I have encountered this issue with the games Bioshock and Neverwinter Nights 2 and it makes both games totally unplayable.
On my Gentoo system, this problem happened after a large number of updates performed by the package manager. Most of the updates were to migrate from KDE-3.5 to KDE-4. Prior to this update, all games worked for me perfectly. Immediately after this update, they behaved as described in the paragraph above.
I still don't know exactly what caused this issue. However, I was able to resolve it by means of a workaround. I have an nVidia 8600 GTS graphics card and I use the proprietary drivers as provided by nvidia.com in order to have full 3D acceleration. I had this issue when using older nVidia drivers, version 173.14.20-r1. When I updated to 190.42-r2 (which also included the installation of libvdpau version 0.2 as a dependency) this issue went away entirely and all Windows games using DirectX again worked perfectly for me.
If you are wondering why I was using an older nVidia driver, it's because this Gentoo system uses the Hardened profile, i.e. it includes PaX and Grsecurity among other things. The binary nVidia drivers are known to be problematic for this configuration, so when I find a version that works well and does not cause problems I tend to keep using it until it is necessary to upgrade. In this case, upgrading resolved all issues I was experiencing with WINE and did not cause problems with anything else.
I cannot comment on ATI hardware as I do not own an ATI video card.
So, I don't think this is just a WINE bug, but has to do with the interaction of WINE and the video driver. However, if you perform a Google search for that 0x502 error message, you will find many forum posts describing the problem and you almost certainly will not find anyone with a solution. Therefore, I wanted to share this here hoping that it will save someone the troubleshooting that I had to perform.
http://bugs.winehq.org/show_bug.cgi?id=16348
--- Comment #4 from Artem S. Tashkinov t.artem@mailcity.com 2009-11-02 15:53:47 --- With NVIDIA drivers 190.42 this problem is fixed.
-
wine-bugs＠winehq.org