Anisotropic filtering: driver setting doesn't matter...?

[Guest]

I got the problem solved by re-installing nHancer and settings AF in the FSX-profile. Suddenly everything worked again. Don't exactly know what went wrong... I do know however that nHancer Profile AF-setting overrides any other setting, but that this is the contrary for FSAA... Well, in m case anyway. Want to know more about it, read it all here:http://forums.avsim.net/dcboard.php?az=sho...id=430970&page=

[Guest firehawk44]

"I got the problem solved by re-installing nHancer and settings AF in the FSX-profile. Suddenly everything worked again. Don't exactly know what went wrong... I do know however that nHancer Profile AF-setting overrides any other setting, but that this is the contrary for FSAA... Well, in m case anyway."JvanE: Glad to hear you finally got your problem(s) fixed! Maybe it will work for others too. BTW, everything I have read since FSX was released is that it's CPU, not GPU, intensive so I have been centering my "fixes" around the CPU since I have more than enough power/memory/etc., in my 8800GTX GPU's (in SLI mode) for graphics (with FSX sliders set nearly to the default settings). My "fixes" are simply keeping the display sliders within FSX moderately set and not to the max, lowering traffic settings, and modestly overclocking my CPU from 2.93 GHz to 3.47GHz (per manufacturers recommendations). Best regards,Jim