[Wine] Gaming support with different hardware vendors (esp. ATI)
M.Kiesel
wine-devel at continuity.cjb.net
Sun Dec 7 19:03:33 CST 2008
On Sun, 7 Dec 2008, Stefan Dösinger wrote:
>> 1. How much of the ATI trouble can be attributed to Wine, how much to
>> the fglrx driver? ...
> Probably 50-50.
...
Thanks for the detailed information! Will try to summarize that for the
FAQ.
ATI trying to fix fglrx for Wine sounds very good.
Concerning the bugs I observed (with Radeon HD 3850 and fglrx 8.11):
1. Prince of Persia SoT run with WINEDEBUG=+warn and minimum graphics
settings gives
[---]
fixme:d3d9:Direct3DShaderValidatorCreate9 stub
fixme:d3d_shader:print_glsl_info_log Error received from GLSL shader #31:
"Fragment shader was successfully compiled to run on hardware.\nWARNING:
0:2: extension 'GL_ARB_draw_buffers' is not supporte"
fixme:d3d_shader:print_glsl_info_log Error received from GLSL shader #29:
"Fragment shader(s) linked, vertex shader(s) linked. \nWARNING: 0:2:
extension 'GL_ARB_draw_buffers' is not supported "
[---]
. The graphics error is difficult to describe; many misplaced
offscreen vertices is the best description I can come up with (can take
screenshots/video though if it helps).
In the meantime I also found http://bugs.winehq.org/show_bug.cgi?id=7411
which looks like pretty much the same issue (see comment #8).
2. Supreme Commander supports shader model 2.0. Don't know if it uses 3.0
features if present. Everything's fine until ingame; then, the engine
seems to switch between the loading screen and a black screen. Same fixme
messages as in PoP.
Can I help in some way? Trying patches, running other tests or games
(e.g., Bioshock as a shader 3.0 game)? Is there some git branch worth
trying out?
Regards
More information about the wine-users
mailing list