There is a similar thread going on in the tech support forum:
http://bbs.hitechcreations.com/smf/index.php/topic,234795.0.htmlThere, Chalenge is suggesting not running AA above 4X because "you won't be able to see dots as well." Maybe that's NHawk's rationale as well? Personally, when I tried bouncing between 16X and 4X I can't say I really notice that much difference. This kind of goes to the motivation for creating this thread to begin with as I have changed so many settings so many times that I have just gotten lost in the details.
Just some random comments...
It seems I recall Skuzzy saying that AH doesn't use Anisotropic Filter so if that's true, I guess it doesn't matter what you do with that. (I wish I could find the thread where he talked about that but my search skills are failing me.) I have played with several settings and haven't noticed any big differences.
Frame rates are not a problem for me at all with AH. Running VidSync is the only way to go (IMHO) and the larger monitors (e.g. 24" widescreen) seem to all run at 60Hz so limiting the frame rate to 60 in game seems logical. With that said, I have read that more than a few people say you should set FR to "unlimited" in Flight Sim X (the other game I'm trying to tune) because you'll get better performance than when you limit it to your VidSync. I don't really understand that but it does appear to be the case. Perhaps the same is true with AH but because my FR doesn't drop below 60 very much in AH, I'm not sure I'd see the difference anyway. Things are VERY different with FSX where my FRs are in the 30s and drop down in the low 20s and even high teens occasionally. FSX is a real beast!
One minor anomaly I've been trying to improve is sort of a "tingle" or "sparkling" of the terrain. Have you ever seen one of those shows on Discovery Channel where they show you the world through some kind of "enhanced video" where you see germs on everything and there is this kind of "tingle" effect on objects? Well, this is a bit like what I'm trying to describe though not nearly that pronounced. I'm going to try setting "Texture Filtering - Negative LOD bias" to "Allow" (as NHawk does) rather than "Clamped." I haven't tried that yet I don't think. I set it to Clamped because others have said (in a FSX forum) that was better.
One of the reasons this has been so difficult for me as I am trying to deal with FSX and AH at the same time. The graphics of FSX is considerably better than AH but the performance demands of FSX over AH are significant. This has been very challenging to say the least.
I appreciate everybody's responses. I'm convinced that if we keep hammering this out, we can come up with a good "basic settings" for those of us with similar hardware. That's really all I'm after here.
Keep it coming!
-hb