Yesterday and today I went into venturing to see what differences Anisotropic filtering in FSX and in Nvidia Inspector brings. I was, simply said, astonished by some results. I honestly hope the test I did reflects reality, as I was flying around, and noticed certain problems when I came over water.
It all started with AVSIM’s user Rockliffe, who once said that he noticed small stutters with AF set to 16x in NI. So I took it couple of steps further, wanted to know what graphical differences both bring, and what, if any, performance differences.
100fps+ vs 31fps, in the external view, is something that made me look really awkward. Even NickN suggests using AF 16x in NI, and yet, I stumbled across this. Also, I would be very grateful if someone would attempt replicating these results. These were taken flying south, HDG 180, straight out of Gatwick, FTX UK installed, in a default 737. Also my textures are from REX, sparkling water, 2048 clouds, etc… nothing special, your every day settings.
Here are some shots I’d like to present, so you can see for yourself what I found out:
All I did between sessions was change the Aniso in FSX to trilinear and enable Aniso 16x in Nvidia Inspector.
Graphical differences are small – with internal Aniso, runway and taxiway textures are calmer, less shimmery, but water shimmers more, and with Nvidia Inspector Aniso 16, water shimmers much less, becomes very calm looking, except the animation which of course are present, while runway and taxiway textures shimmer more. Ground textures are pretty much the same. Other settings are all according to my FSX Guide blog.
I know I’ll be keeping the internal FSX Aniso on from now on, and as I said, I’d be glad if someone would repeat this test – maybe it’s something else causing this, maybe not, but if others don’t have such issues, I might start looking into other causes of this problem!