[Bug 13101] GLXBadDrawable when antialias ON (Nvidia driver bug?)

wine-bugs at winehq.org wine-bugs at winehq.org
Fri Jun 20 00:11:40 CDT 2008


http://bugs.winehq.org/show_bug.cgi?id=13101





--- Comment #56 from Roderick Colenbrander <thunderbird2k at gmx.net>  2008-06-19 04:02:35 ---
Just to point out setting the Direct3D\Multisampling registry key to enabled
allows you to use multisampling (if a game offers it) and this will re-enable
the nvidia driver bug.


--- Comment #57 from Robert M. Muncrief <rmuncrief at comcast.net>  2008-06-20 00:11:40 ---
(In reply to comment #56)
> Just to point out setting the Direct3D\Multisampling registry key to enabled
> allows you to use multisampling (if a game offers it) and this will re-enable
> the nvidia driver bug.
> 

Actually, I have this is not true. If you set Direct3D\AllowMultisampling some
games will think AA is on, but it's not. The games will show no AA smoothing.

For example, FlatOut 2 doesn't think AA is on no matter what the
AllowMultisampling setting. All the Half-Life games I have think AA is on when
AllowMultisampling is enabled, but they run with no AA affects. And Far Cry 2
thinks AA is on, but if you try to set it to anything other than off the game
just crashes.

But for some reason the Wine developers refuse to fix this massive breakdown in
game play, choosing to blame it on Nvidia drivers without evidence. They are
blaming every release after 100.14.19 for all of Wines problems with AA.

So I'm trying to figure out what went wrong on my own, but it's already been
four days and I still have no good bisect. There are 10  wine versions, and 5
driver versions, to test which doesn't make my job easy. I sure wish a
developer who understood Wines AA and interaction with Nvidia drivers would
work on it instead of the whole lot simply refusing to fix it.

Finally, if you have an Nvidia card and want to use wine to play games you will
most likely have to use Wine 1.0-rc3 and Nvidia driver 100.14.19. Anything
beyond rc3 has the AllowMultisampling setting that doesn't work, and any later
driver will give you the GLXBadDrawable error.

And if you run Ubuntu, Hardy will not allow you to play Far Cry 2, while an
identical installation on Gutsy allows you to play Far Cry 2, with the
intermittent start up crash. Just keep system monitor handy and you can kill
all the hung Wine processes by passing your mouse over all tasks and killing
everything that starts with a DOS drive (C:, D:, etc.).


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