http://bugs.winehq.org/show_bug.cgi?id=23386
Summary: TF2 throws pixel shader 1.1 error when started with -dxlevel 9 Product: Wine Version: 1.2-rc4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: cookiecaper@gmail.com
If I start TF2 with the option -dxlevel 9, the splash screen renders, and then the game closes and an error message that says something like "Your graphics hardware must support pixel shader 1.1 to play this game!" occurs.
It works completely fine with -dxlevel 81.
I've had this error for years, but I've been hearing more and more people talk about playing with dxlevel 9 recently, claiming it runs great or even better than dxlevel 81.
I have tried a new prefix, a new Steam directory, running inside and outside my 32-bit chroot, and none of these things have changed anything.
I am running ArchLinux with kernel 2.6.34, nvidia 256.35, GeForce GTX 285, but as I said, I've had this trouble for years, even when using different nvidia cards (previously had a 7900GTO). Through all the WINE updates, everything, this has stayed constant. I'm currently running a version from git compiled yesterday.
I'll attach a couple of snippets from a Steam run for your examination. Thanks for looking, and thanks to everyone in IRC who helped, especially kevlarman.
http://bugs.winehq.org/show_bug.cgi?id=23386
--- Comment #1 from Jeff Cook cookiecaper@gmail.com 2010-06-26 01:27:16 --- Created an attachment (id=29146) --> (http://bugs.winehq.org/attachment.cgi?id=29146) glxinfo-like output from start of Steam with WINEDEBUG=+wgl
http://bugs.winehq.org/show_bug.cgi?id=23386
--- Comment #2 from Jeff Cook cookiecaper@gmail.com 2010-06-26 01:28:57 --- Created an attachment (id=29147) --> (http://bugs.winehq.org/attachment.cgi?id=29147) A briefish snippet of console output with WINEDEBUG=+wgl
This is a snippet that occurs when TF2 is launched from WINE with the -dxlevel 9 parameter added. This is not the whole thing because the thing was giant and wouldn't fit in a pastebin, so just grabbed a section; these attachments are pastebins from IRC. I can run again if the whole output or some other section of the output is necessary.
http://bugs.winehq.org/show_bug.cgi?id=23386
--- Comment #3 from Jeff Cook cookiecaper@gmail.com 2010-07-04 17:05:41 --- Created an attachment (id=29353) --> (http://bugs.winehq.org/attachment.cgi?id=29353) Full console output with WINEDEBUG=+d3d
Full console output, started with the line WINEDEBUG=+d3d wine /mnt/tb/apps/Steam/Steam.exe -applaunch 440 -dxlevel 9. gzipped because I don't have a stable host elsewhere to put this.
http://bugs.winehq.org/show_bug.cgi?id=23386
--- Comment #4 from Jeff Cook cookiecaper@gmail.com 2010-07-04 18:23:11 --- Just tried on another computer and I get the same thing; -dxlevel 9 gives me the pixel shader 1.1 error. :( Attaching a snippet from WINEDEBUG=+wgl.
http://bugs.winehq.org/show_bug.cgi?id=23386
--- Comment #5 from Jeff Cook cookiecaper@gmail.com 2010-07-04 18:24:05 --- Created an attachment (id=29356) --> (http://bugs.winehq.org/attachment.cgi?id=29356) WINEDEBUG=+wgl startup info on different computer, GeForce 6150 SE
http://bugs.winehq.org/show_bug.cgi?id=23386
Jeff Cook cookiecaper@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #6 from Jeff Cook cookiecaper@gmail.com 2010-07-09 14:05:47 --- The main problem here is that apparently -dxlevel 9 is the WRONG parameter to give Source games to indicate the dxlevel. It must be -dxlevel 90. When I do that, everything works. If anyone comes across this bug with the same problem, make sure you are passing -dxlevel 90 or -dxlevel 95, as these are the accepted parameters for setting DirectX level in TF2. The game starts fine with one of these parameters given.
That said, the game _does_ do something different with -dxlevel 9 because it doesn't start up when I send that. Adding the outstanding remainder of the "3DMark patch", which is setting MaxPointSize = 64.0f in directx.c gets around the error on startup about the pixel shader, but the game continues to render in DX8 mode anyway. I don't know what -dxlevel 9 is supposed to do, probably just a leftover, but it breaks things and Valve should remove it.
I am closing this bug as invalid because -dxlevel 9 is an undocumented parameter, nobody knows what it is supposed to do, and I don't feel like testing this one on Windows to see if it gives the same behavior or not. If someone else decides it's a real issue, please reopen.
http://bugs.winehq.org/show_bug.cgi?id=23386
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED Component|directx-d3d |-unknown
--- Comment #7 from Vitaliy Margolen vitaliy@kievinfo.com 2010-07-09 14:38:10 --- Closing invalid.