[Bug 23386] TF2 throws pixel shader 1.1 error when started with -dxlevel 9
wine-bugs at winehq.org
wine-bugs at winehq.org
Fri Jul 9 14:05:47 CDT 2010
http://bugs.winehq.org/show_bug.cgi?id=23386
Jeff Cook <cookiecaper at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
--- Comment #6 from Jeff Cook <cookiecaper at 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.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
More information about the wine-bugs
mailing list