[Bug 91786] setting texture filtering to nearest has no effect when anisotropy is greater than 1

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Apr 17 00:10:57 UTC 2016


rain.backnet+bugzilla_freedesktop at gmail.com changed:

           What    |Removed                     |Added
            Version|10.6                        |11.1

--- Comment #3 from rain.backnet+bugzilla_freedesktop at gmail.com ---
This is still present in 11.1.2, in i965-va-driver.  Some example screenshots
and code below:

Nearest neighbour, no anisotropy settings specified:
https://i.imgur.com/LadPw7T.png - note the clearly defined windows in the
foreground, but the banding in the building on the right.

As above but with anisotropy set to 16.0: https://i.imgur.com/9YiQi2S.png -
note that the banding on the right is gone, but the nearest neighbour effect on
the nearby windows now looks like linear filtering.

Finally, with anisotropy explicitly set to 1.0: https://i.imgur.com/7ZckqqN.png
- this is indistinguishable from the screenshot with no anisotropy set at all.

Other drivers (on Windows, OS X etc) render this scene correctly with
anisotropic filtering removing the banding while still showing nearest
neighbour filtering in the foreground, I can provide comparable screenshots if
that would be useful.

Relevant parameters to reproduce: 
  // anything other than 1.0f below disables the nearest neighbour filtering

You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20160417/00faaab7/attachment.html>

More information about the intel-3d-bugs mailing list