--- Comment #7 from i...@yahoo.com ---
It's not driver specific bug.
I should have followed the hint that there is a registry entry to workaround
this problem with wined3d. It turns out that this registry entry is
specifically for this bug. The analysis and possible solutions could be found
Also, this bug is also tracked at:
You are receiving this mail because:
You are the assignee for the bug.
dri-devel mailing list