wine users - Mar 2009 - L4D crashes reaching in-game, d3d_shader bug maybe?

Hi there, I'm running Ubuntu 8.04, 32-bit.
Now using Wine 1.1.17
Using Ati binary driver 9.2 for x1600 series

I'm experiencing problems with Left 4 Dead. Basically I have sound, and I
can get to the main menu no problem using this command (which I found on
http://www.youtube.com/watch?v=far0jjAlg24).

Code:
env WINEPREFIX="/home/xxxx/.wine" wine "C:\Program
Files\Steam\steam.exe" -applaunch 500 +mat_hdr_level 0 -novid -height 900
-width 1440 -windowed



The first time I ran that code from the terminal I was using Wine 1.0, and I
could get to the main menu but there was no sound and it would crash immediately
if I tried to go in game be it multiplayer (online) or single player. I tried a
second time with Wine 1.0 and using Ati's binary drivers this time, sound
worked but I lost all image (just a black screen) so I decided to upgrade to
wine 1.1.17

The third time I ran that code was with wine 1.1.17, I reached the main menu
with crisp sound ( a very happy moment indeed) but the main problem persisted,
although it actually made it for a second or so in-game this time, it would
crash in game.

I know posting all the output from the terminal would be useless so I tried to
narrow it down to the very last moments before it crashed and this is what the
terminal reported:

Code:
fixme:d3d_shader:print_glsl_info_log Error received from GLSL shader #93:
"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 #90:
"Fragment shader(s) linked, vertex shader(s) linked. \nWARNING: 0:2:
extension 'GL_ARB_draw_buffers' is not supportedWARNING: built-in
varying gl_TexCoord [1] has mismatched access semantics between the vertex and
fragment shader\nWARNING: built-in varying gl_TexCoord [3] has mismatched access
semanti"...



I originally posted in Ubuntu forums so I wouldn't bother others here, but
they referred me to these forums since it seems to be explicitly a Wine related
problem.

I am using an original version of Left 4 Dead and Steam runs fine.
I also tried running HL2 Deathmatch with this version of Wine and it actually
runs compared to v1.0 (in my experience) but the characters are deformed
(polygons stretched beyond the map), maybe this co relates to L4D above?

I only mentioned HL2's problem as it may provide a solution someone already
knows to the problem I'm having with Left 4 Dead.

Any possible help is appreciated, and yes I have referenced the AppDB and quite
a few have gotten the game running (especially with Wine 1.1.17).

On Sun, Mar 22, 2009 at 2:29 AM, myromance123 <wineforum-user at
winehq.org> wrote:
> Hi there, I'm running Ubuntu 8.04, 32-bit.
> Now using Wine 1.1.17
> Using Ati binary driver 9.2 for x1600 series
>
> I'm experiencing problems with Left 4 Dead. Basically I have sound, and
I can get to the main menu no problem using this command (which I found on
http://www.youtube.com/watch?v=far0jjAlg24).
>
> Code:
> env WINEPREFIX="/home/xxxx/.wine" wine "C:\Program
Files\Steam\steam.exe" -applaunch 500 +mat_hdr_level 0 -novid -height 900
-width 1440 -windowed
>
>
>
> The first time I ran that code from the terminal I was using Wine 1.0, and
I could get to the main menu but there was no sound and it would crash
immediately if I tried to go in game be it multiplayer (online) or single
player. I tried a second time with Wine 1.0 and using Ati's binary drivers
this time, sound worked but I lost all image (just a black screen) so I decided
to upgrade to wine 1.1.17
>
> The third time I ran that code was with wine 1.1.17, I reached the main
menu with crisp sound ( a very happy moment indeed) but the main problem
persisted, although it actually made it for a second or so in-game this time, it
would crash in game.
>
> I know posting all the output from the terminal would be useless so I tried
to narrow it down to the very last moments before it crashed and this is what
the terminal reported:
>
> Code:
> fixme:d3d_shader:print_glsl_info_log Error received from GLSL shader #93:
"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 #90:
"Fragment shader(s) linked, vertex shader(s) linked. \nWARNING: 0:2:
extension 'GL_ARB_draw_buffers' is not supportedWARNING: built-in
varying gl_TexCoord [1] has mismatched access semantics between the vertex and
fragment shader\nWARNING: built-in varying gl_TexCoord [3] has mismatched access
semanti"...
Your graphics card/drivers don't support all needed features.


-- 
-Austin

What exactly is missing/ not meeting the requirements?

 I played Left 4 Dead using this exact card with Windows XP and there was no
problem.
I was able to run the game with medium graphics.

The card supports shader model 3.0 and everything else the game requires to run
smoothly.
 
 Is this for certain not something amiss with Wine 1.1.17?
I am using ATI Radeon Gecube x1650 ( a mid-range card ).

Steam is complaining my graphics driver is outdated (it always did), although I
have upgraded it to the latest provided by Ati themselves on their site.

Thanks for the fast reply, I hope you or anyone else can answer my question or
provide a solution to this.

Really?!?

 Oh man, this means Ati sucks big time.
For them to provide drivers which don't even support the main functions of
that card the driver is meant for is shocking to me, I thought they were
professionals.
This is probably why all the L4D players on ubuntu I see use Nvidia, must truly
have better support...o dang it ( smash smash smash )

Just to be sure, where can I find information on what the Ati Drivers actually
do support?
You seem very knowledgeable in the matter, please provide me with some
references :)

I don't believe the ati website has the information ( or at least I
can't find/locate it, I've searched for quite some time)

Plus: does this mean there is no workaround for Ati cards for L4D? ( in terms of
whats missing in the driver )

I have also run Wine on fglrx drivers and seen your error message before. It was
some time ago and my memory is struggling but I think the game managed to carry
on despite that. It crashed later though.

I cannot check that now because I have changed to the radeon driver as ATI are
now supporting that development for machines as old as mine!.

When investigating the crash, I concluded that Wine did not correctly translate
the version number of the fglrx driver. I think the idea was to convert the ATI
Linux driver version string to something more like a Windows driver version
string, but (I suspect) ATI had changed the Linux version format themselves and
Wine no longer parsed it correctly. Therefore, the string it passed to the game
(if the game asked) was gibberish. That could confuse the game properly. This
was a few versions ago and may have been fixed, it may not be important, but it
was a wine problem, not an ATI one.

Austin will say I should have raised a bug report but I did not reach the level
of confidence in my work to do so.

So why raise it now - mostly because I get annoyed by some wine enthusiasts
hatred of everything ATI. I am not associated with ATI (except by owning an ATI
card) but I think this idea that ATI is wrong and Wine is right is mostly pure
bias - perhaps based on long gone history.

Please do not be put off; ATI cards can work quite nicely, as can Wine. Try the
open source drivers - they are getting pretty good, try digging around in Wine -
you may do better than I did and find your solution and be confident enough to
raise that bug report.