[Bug 16348] GL_INVALID_OPERATION (0x502) from glUniform4fvARB() @ glsl_shader.c

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=16348


causality <M8R-gepdgu at mailinator.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |M8R-gepdgu at mailinator.com




--- Comment #3 from causality <M8R-gepdgu at 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.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.