L4D crashes reaching in-game, d3d_shader bug maybe?

[myromance123]

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: Select all

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: Select all

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).

[austin987]

On Sun, Mar 22, 2009 at 2:29 AM, myromance123 <[email protected]> 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

[myromance123]

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.

[austin987]

On Sun, Mar 22, 2009 at 8:42 PM, myromance123 <[email protected]> wrote:

What exactly is missing/ not meeting the requirements?

WARNING: 0:2: extension 'GL_ARB_draw_buffers' is not supporte"

 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.

Windows drivers != Linux drivers.

ATI is known for making crappy drivers for Linux, since it's not as
popular platform, the drivers aren't given much effort.

--
-Austin

[myromance123]

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 )

[Usurp]

Windows drivers != Linux drivers.

Agreed on that.

ATI is known for making crappy drivers for Linux, since it's not as
popular platform, the drivers aren't given much effort.

--
-Austin

It is not true anymore, a bunch of work is done on the free radeonhd driver since January.
Check the radeonhd commits if you don't believe an ATI user

[vitamin]

Check the radeonhd commits if you don't believe an ATI user

So judging by number of commits Wine should be way ahead of windows by now and should run all the windows software flawlessly. Is that what you implying?

[Daemon]

Check the radeonhd commits if you don't believe an ATI user

So judging by number of commits Wine should be way ahead of windows by now and should run all the windows software flawlessly. Is that what you implying?

I believe he's referring to the Xorg RadeonHD drivers.http://cgit.freedesktop.org/xorg/driver ... -radeonhd/

[Daemon]

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

glxinfo or fglrxinfo will give you all the supported Opengl extensions,etc.

[myromance123]

Thank you daemon.

I typed in glxinfo and it gave me exactly what I wanted to check

austin987, it says GL_ARB_draw_buffers not supported but under the glxinfo list I can clearly see GL_ARB_draw_buffers listed

Doesn't that mean I have whats required?
Would you like me to post the whole list? (slightly long but not crazy long)

If it is supported but the game is complaining its not, where could the problem lie for the game to not realize whats actually there?

Thanks for all the fast replies, I see there are other things wrong but lets see if the GL_ARB_draw_buffers problem can be fixed first and continue from there (if possible)

[vitamin]

austin987, it says GL_ARB_draw_buffers not supported but under the glxinfo list I can clearly see GL_ARB_draw_buffers listed

Doesn't that mean I have whats required?

That means your driver is lying about what it supports. Because that warning came from the driver itself while compiling shaders.

Do not waste time on wine with any newish game - they won't work. Especially if you own anything other then nvidia card. Chances for any newish game to work are not good.

[Daemon]

Thanks for all the fast replies, I see there are other things wrong but lets see if the GL_ARB_draw_buffers problem can be fixed first and continue from there (if possible)

Similar problem here -> http://bugs.winehq.org/show_bug.cgi?id=15644#c48

[myromance123]

Thank you once again Daemon, you must be a specialist

Just to check, I read it through (that comment) and it "seems" as though he said that different problems occur with different drivers, so it most likely means the driver I have is the problemed one, Although I'm pretty sure there's a solution to the compiler error there, I fail to understand what they are talking about when he gets deeply technical so I can't seem to understand/comprehend the solution to the compiler error I'm experiencing, because comment #48 from Tobias Jakobi near its end says that he indeed solves the compiler error but nonetheless with flickering in certain parts still apparent.

I do not know how to solve it, who/where should I ask for help regarding this (its not in these forums right?)?
Or could it be they are the ones fixing the issue?

Also, with regards to what vitamin said, in that comment it does not say/indicate anywhere that the driver is lying/falsely indicating about supporting GL_ARB_draw_buffers. Could vitamin be wrong?
Or is the comment meaning that, and I just dont get it?

I'm pretty sure its the first, but I ask for reassurance. I do not mean to be rude, I want to understand the problem better and I'm sorry if I'm mistaken.

Thanks for all the speedy replies so far.

[vitamin]

I do not know how to solve it, who/where should I ask for help regarding this (its not in these forums right?)?

Take your card back and exchange it for any nvidia card.

Also, with regards to what vitamin said, in that comment it does not say/indicate anywhere that the driver is lying/falsely indicating about supporting GL_ARB_draw_buffers. Could vitamin be wrong?
Or is the comment meaning that, and I just dont get it?

This message came directly from the video driver (well actually libgl which is part of the driver).

Code: Select all

"Fragment shader was successfully compiled to run on hardware.\nWARNING: 0:2: extension 'GL_ARB_draw_buffers' is not supporte"

What it's talking about? I don't know. If you say that extension is listed in gxlinfo output then your driver is lying somewhere. Either the warning message is not correct and it refers to something else (most likely), or your card/driver really doesn't support this extension.

[myromance123]

Take your card back and exchange it for any nvidia card.

Indeed I wish I could do that, sadly customer support over here is next to nil so theres no chance of exchanging it lol (or refund or warranty or anything else).

Basically I was asking about the comment Daemon referred and where can I follow up with those people or others who know bout it.

What it's talking about? I don't know. If you say that extension is listed in gxlinfo output then your driver is lying somewhere. Either the warning message is not correct and it refers to something else (most likely), or your card/driver really doesn't support this extension.

Mmm I wonder if it's the driver lying or whether when the game runs under Wine, somewhere along its execution Wine isn't picking up what the driver has or isn't getting the required feedback from the driver. Thanks for your reply dood, well if anyone else may have found a solution or fix to this I'm all ears.

For now it looks as if no L4D for me (what a bummer..).

[jeffz]

Take your card back and exchange it for any nvidia card.

Indeed I wish I could do that, sadly customer support over here is next to nil so theres no chance of exchanging it lol (or refund or warranty or anything else).

Basically I was asking about the comment Daemon referred and where can I follow up with those people or others who know bout it.

What it's talking about? I don't know. If you say that extension is listed in gxlinfo output then your driver is lying somewhere. Either the warning message is not correct and it refers to something else (most likely), or your card/driver really doesn't support this extension.

Mmm I wonder if it's the driver lying or whether when the game runs under Wine, somewhere along its execution Wine isn't picking up what the driver has or isn't getting the required feedback from the driver. Thanks for your reply dood, well if anyone else may have found a solution or fix to this I'm all ears.

For now it looks as if no L4D for me (what a bummer..).

looks like it's reported here too http://ati.cchtml.com/show_bug.cgi?id=1211

[myromance123]

Hey thanks Jeffz, I found out about the bugzilla but didn't know how to work my way around.

Thanks for pointing me to that
I've voted for it, thanks again~

[guanxiaof]

The error string is generated after compiling shader and is returned by the driver. However, this extension has been supported by the Catalyst driver already for a long time. Although it throw out a error, it could not bother WINE.

[myromance123]

guanxiaof, what do you mean "it could not bother WINE"?

Are you trying to say that the error being output isn't the main problem( or a problem at all)?
If that is what you're saying, what is the problem then?

Sorry if I'm misunderstanding you ( I read your reply several times ).

I have read elsewhere that this problem is already covered by Catalyst 8.1 and above but those were from various forums, so I wasn't sure.

[Thunderbird]

The GL_ARB_draw_buffers message is just printed by the ati drivers and can be ignored. There are certainly some bugs left in the Ati drivers but some future Wine work might improve performance in source games a lot (I believe Stefan discovered one major cause of slowness and is looking at that now).

[Buck Golemon]

vitamin <wineforum-user <at> winehq.org> writes:

myromance123 wrote:

I do not know how to solve it, who/where should I ask for help regarding

this (its not in these forums right?)?

Take your card back and exchange it for any nvidia card.

I have an nvidia card, using the binary drivers, but Left4Dead won't even
display a splash screen. Can anyone help me debug? I don't know the proper
procedure...

I've been able to reduce the amount of debug output to 114 lines by upgrading
wine and my drivers, but still it crashes.

Using wine-1.1.18.

All the discussion on WineHQ seems to be about performance, not crashes.

I've posted the console output here:
http://pastebin.com/m6c0a7c0a

[austin987]

On Sun, Apr 12, 2009 at 2:33 AM, Buck Golemon <[email protected]> wrote:

vitamin <wineforum-user <at> winehq.org> writes:

myromance123 wrote:

I do not know how to solve it, who/where should I ask for help regarding

this (its not in these forums right?)?

Take your card back and exchange it for any nvidia card.

I have an nvidia card, using the binary drivers, but Left4Dead won't even
display a splash screen. Can anyone help me debug? I don't know the proper
procedure...

I've been able to reduce the amount of debug output to 114 lines by upgrading
wine and my drivers, but still it crashes.

Using wine-1.1.18.

All the discussion on WineHQ seems to be about performance, not crashes.

I've posted the console output here:
http://pastebin.com/m6c0a7c0a

First, fix your xorg.conf:

err:x11settings:X11DRV_ChangeDisplaySettingsEx No matching mode found 640x480x32 @60! (XRandR)

--
-Austin

[English_Mohican]

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.

[austin987]

On Mon, Apr 13, 2009 at 5:27 PM, English_Mohican
<[email protected]> wrote:

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.

Of course . Bugs can't be fixed if they aren't known.

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.

It's not that we hate ATI. It's that there are plenty of bugs in
applications on Wine that ATI hasn't fixed, but work fine in
Nvidia/Intel. Stefand put a lot of work into making testcases, and
filed bugs with ATI about them, but they are reluctant to fix them
unless they affect 'a large number of popular applications'.

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.

The open source drivers are getting better, sure. But 3d support still
isn't too great, and most users don't want something that will work in
a few years, they want what works now, which is Nvidia.

It's not the best choice, and coming from a student of economics, not
the most optimal market solution, but it's the one that Linux users
currently are stuck with. Of course, you're free to make up your own
mind, but having seen many users/reports/test results, I can say that
Nvidia is currently the best choice for Windows games under Wine.

--
-Austin

[Buck Golemon]

vitamin <wineforum-user <at> winehq.org> writes:

myromance123 wrote:

I do not know how to solve it, who/where should I ask for help regarding

this (its not in these forums right?)?

Take your card back and exchange it for any nvidia card.

I'm using an nvidia card and the binary drivers, but I can't get l4d to even
start. This is surprising to me since all the discussion on WineHQ is about
performance and nobody mentions problems with starting it.

Can someone take a look at my console output and see if there's anything I can
do? I've pasted it here: http://pastebin.com/m6c0a7c0a

If there's some more useful output I can give, please let me know.

--Buck