[Bug 31934] New: fglrx returns wrong values for GL_MAX_FRAGMENT_UNIFORM_COMPONENTS_ARB and GL_MAX_TEXTURE_UNIFORM_COMPONENTS_ARB
http://bugs.winehq.org/show_bug.cgi?id=31934
Bug #: 31934 Summary: fglrx returns wrong values for GL_MAX_FRAGMENT_UNIFORM_COMPONENTS_ARB and GL_MAX_TEXTURE_UNIFORM_COMPONENTS_ARB Product: Wine Version: 1.5.14 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: orion@parsed.net Classification: Unclassified
Created attachment 42060 --> http://bugs.winehq.org/attachment.cgi?id=42060 add fglrx quirk
After much digging, I have found what appears to be a long-standing bug with fglrx drivers. Discussion from 2009: http://phoronix.com/forums/showthread.php?15108-Catalyst-9-1-is-out/page11 http://irclogs.ubuntu.com/2012/06/05/%23ubuntu-x.html Upstream: http://ati.cchtml.com/show_bug.cgi?id=528
fglrx reports a value of 1024 for GL_MAX_FRAGMENT_UNIFORM_COMPONENTS_ARB and GL_MAX_TEXTURE_UNIFORM_COMPONENTS_ARB for any application named "wine" but will report the correct value for other applications. (I do not know why)
As a result, certain graphical applications (e.g. Guild Wars 2) report "The hardware does not support enough uniform components to run this shader, it may not render correctly." and then run at a reduced framerate.
The attached patch adds a WINED3D_QUIRK to set the correct value on certain families of Radeon HD video cards.
My research has found that the corrected value of 16384 should be correct on any Radeon dx10 cards from HD2xxx through HD6xxx. (With HD7xxx being a redesigned card, it actually only reports 1024 via glxinfo, and should not need this)
Results: Higher framerates, ability to use more advanced GPU features in game options, and lower GPU temperatures (!). (Tested with a Radeon HD 6950, linux 3.2.0-31, fglrx 8.980, wine 1.5.14)
http://bugs.winehq.org/show_bug.cgi?id=31934
--- Comment #1 from Henri Verbeet hverbeet@gmail.com 2012-10-10 05:22:08 CDT --- This is supposedly fixed in the latest beta drivers. Realistically though, you're probably better of running the Mesa drivers for anything except Southern Islands cards at the moment.
http://bugs.winehq.org/show_bug.cgi?id=31934
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |UPSTREAM
--- Comment #2 from Austin English austinenglish@gmail.com 2012-10-10 12:56:06 CDT --- (In reply to comment #1)
This is supposedly fixed in the latest beta drivers. Realistically though, you're probably better of running the Mesa drivers for anything except Southern Islands cards at the moment.
UPSTREAM then, if we're not going to work around it.
http://bugs.winehq.org/show_bug.cgi?id=31934
--- Comment #3 from aaron orion@parsed.net 2012-10-12 12:24:00 CDT --- (In reply to comment #1)
This is supposedly fixed in the latest beta drivers.
Confirming this is fixed upstream with drivers 12.9beta.
Realistically though, you're probably better of running the Mesa drivers for anything except Southern Islands cards at the moment.
Comparing my usual usages, I still get much better results with fglrx, even with this bug present.
http://bugs.winehq.org/show_bug.cgi?id=31934
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #4 from Austin English austinenglish@gmail.com 2012-10-15 18:17:08 CDT --- (In reply to comment #3)
(In reply to comment #1)
This is supposedly fixed in the latest beta drivers.
Confirming this is fixed upstream with drivers 12.9beta.
Closing then, thanks.
-
wine-bugs＠winehq.org