nVidia 8800GT, Windows 7, Anisotropic Filtering

[VW_Factor]

<p>While this isnt performance related. </p><p>Maybe someone else has noticed that when AF is turned on (been using 8x in game for some years now) that depending on some UI elements, AF may or may not be applied to the scene? </p><p>185.81 and 185.85 driver sets both seem to have this issue.</p><p>Ideas?</p>

[TSR-DanielH]

<p>Greetings,</p><p>I haven't noticed this issue myself by my eyes were never that good at discerning that type of thing.  Has this just started happening for you?  What do you have your 'rendering distance' set to in the graphics options?</p>

[VW_Factor]

<p>I began noticeing this after dumping Vista and jumping on the RC Beta Windows 7 bandwagon.  (Which is just plain better than Vista in everyway).</p><p>This is the only game Ive noticed this happen with.  It will do it with SLI enabled, or without, and doesnt seem to matter what settings I play with, it is going to happen.. </p><p>Rendering distance is set to 100% or whatever.  Slid all the way to the right.  I will PM a few screens so you may be able to see what Im talking about.</p>

[TSR-DanielH]

<p>Checking the screenshots, the problem is pretty noticable.  I know that I have not been seeing that same error on my Vista machine, though. </p><p>I just updated my home computer to Vista SP2 last night and apparently it includes some of the features from Win7 as well.  I'm going to check the game again tonite and see if it's happening on my computer now.  If so, we can narrow down the list of possible causes.</p><p>The most likely answer is some kind of incompatibility between the beta operating system and the drivers you are using, but I'm going to see what else I can find out.</p>

[VW_Factor]

<p>Ive still got no progress here.  Ive emailed nVidia driver support and supplied them the screens as well.  Of course, dont expect to hear from them this weekend, but perhaps next week they'll be able to shed some more light on the subject.</p>

[TSR-DanielH]

<p>Sadly, outside of finding one of the guys working on Windows 7, its going to be difficult to diagnose the issue.  I don't think the Win7 graphics drivers have been released yet so you're probably running with Vista drivers.  Considering Win7 is still in beta, that can make things difficult. </p><p>I was not able to reproduce the error when trying several Vista configurations.  I would try Win7 as well, but I just reinstalled Vista after a massive computer upgrade so I don't want to rush into another reinstall.  Maybe I'll get motivated here and set up a dual boot soon that I will be able to help.</p>

[VW_Factor]

<p><cite>TSR-DanielH wrote:</cite></p><blockquote><p>Sadly, outside of finding one of the guys working on Windows 7, its going to be difficult to diagnose the issue.  I don't think the Win7 graphics drivers have been released yet so you're probably running with Vista drivers.  Considering Win7 is still in beta, that can make things difficult. </p><p>I was not able to reproduce the error when trying several Vista configurations.  I would try Win7 as well, but I just reinstalled Vista after a massive computer upgrade so I don't want to rush into another reinstall.  Maybe I'll get motivated here and set up a dual boot soon that I will be able to help.</p></blockquote><p>The latest WHQL driver btw..</p><p>"This driver supports all of the new Windows 7 GPU-accelerated DirectX APIs: DirectX Compute, Direct2D, DirectWrite, and DXVA-HD"</p><p>From nVidias site for the driver.</p>

[VW_Factor]

<p>They have released a new beta driver today.  186.08 and will report my findings.  <img src="/eq2/images/smilies/283a16da79f3aa23fe1025c96295f04f.gif" border="0" /></p><p>Edit : Just fired up a bit for some quickish testing, and it appears to be solved with this driver.</p>

[TSR-DanielH]

<p><cite>VW_Factor wrote:</cite></p><blockquote><p>They have released a new beta driver today.  186.08 and will report my findings.  <img src="/eq2/images/smilies/283a16da79f3aa23fe1025c96295f04f.gif" border="0" /></p><p>Edit : Just fired up a bit for some quickish testing, and it appears to be solved with this driver.</p></blockquote><p>Great, I'm glad to hear the new update resolved the problem.  Those kinds of issues are going to be popping up as they get everything worked out for the new OS, but it seems like they recognized and corrected it pretty fast in this case.  That's certainly encouraging.</p>