I'm gonna keep posting the actual explanation for this until it sticks... :( What is no longer necessary with the recent driver versions is nHancer's overriding of Nvidia's predefined "Enhance" flag for AA in FSX. This is purely about HOW AA is getting applied in FS - with the override method, the FS engine is setting no AA on its own, the video card is being instructed by the driver to antialias at whatever setting you specify. With the in-game box checked, FSX by default uses what I believe to 4X multisample AA. ******* found the cfg settings that actually control what it does by default. That's not of any consequence really though, since the "Enhance" option in the Nvidia driver now works - this tells the card to take whatever the game engine is ordering up and then enhance it to whatever level you've specified. You're going to get the same AA level you got with the override method, but it's now being done the way ACES intended it through the engine itself and not forced on. I don't know what if any performance optimizations are present when doing it this way, but it's quite possible there are some. (ie, the engine-AA is more selective in how it applies the effect vs. just brute forcing it onto the entire scene)nHancer itself is fine, it allows you to set some AA modes (like the combined supersample+multisample ones such as 8XS) that are hidden in the normal driver control panel. You do not need to uninstall nHancer or stop using it. I personally think it's a much better UI for editing the game-specific profiles than the Nvidia driver is. They're both doing the exact same thing (editing a file called nvapps.xml that contains the driver's game-specific profiles), it's just different interfaces for it. All you need to do is reset the FSX profile in nHancer by right clicking it and hitting "Delete/Reset Profile". Then, make your selections again, but don't uncheck "Enhance in-game AA setting" option since this now works fine in FSX like it does in other games.The options I have for my profile now in nHancer are:AA:8xS(Enhance), Power:Max, Perf:HiQual, NegLOD:Clamp Check the AA box and set the filtering dropdown to anisotropic and you're good to go. Looks as good as the old forced method ever did and I'm not dropping below 40FPS using RejectThreshold=102400.

Thanks for the info, Ryan. Any particular reason why I should set AA ingame as well as nhancer? I have been using anistrophic in game as well as through nhancer and things look really good. Will aa set the same look better? I use mipbias=6 in fsx.cfg, should I get rid of that?Also, how are you seeing 40FPS or above? You have sliders mostly to the right? And detailed scenery? In the virtual cockpit of a great PMDG airplane? (hopefully the 737NG :) )I have an i7 950 running at 3.2ghz, with 6gb ram, win7 64bit. and I am happy to get 20fps. Things are smooth, but most my sliders are to the right. I see higher fps in less populated areas, but around big cities and addon scenery, forget it. This is with zero Ai too. Is my computer not setup correctly?

Thanks for the info, Ryan. Any particular reason why I should set AA ingame as well as nhancer? I have been using anistrophic in game as well as through nhancer and things look really good. Will aa set the same look better? I use mipbias=6 in fsx.cfg, should I get rid of that?Also, how are you seeing 40FPS or above? You have sliders mostly to the right? And detailed scenery? In the virtual cockpit of a great PMDG airplane? (hopefully the 737NG :) )I have an i7 950 running at 3.2ghz, with 6gb ram, win7 64bit. and I am happy to get 20fps. Things are smooth, but most my sliders are to the right. I see higher fps in less populated areas, but around big cities and addon scenery, forget it. This is with zero Ai too. Is my computer not setup correctly?

The obvious problem I see is your CPU clock speed...3.2GHz just won't carry the mail with FSX + a big load of autogen, add-on scenery, and traffic. At that clock speed you need major compromises, not sliders to the right (mostly).CheersBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

I followed a few guides and can't get windows stable with 4ghz. I must be setting voltage wrong or something, but windows boots up, and a test program like prime95 quits after 30 seconds with an error message and check the log.

I followed a few guides and can't get windows stable with 4ghz. I must be setting voltage wrong or something, but windows boots up, and a test program like prime95 quits after 30 seconds with an error message and check the log.

Cooling?

I followed a few guides and can't get windows stable with 4ghz. I must be setting voltage wrong or something, but windows boots up, and a test program like prime95 quits after 30 seconds with an error message and check the log.

I don't want to drag this thread off topic, but I will post my ASUS P6T bios settings tomorrow in the hardware section. My i7 920 D0 passes 2 hours of OCCT Linpack and is running @ 4.2Ghz with a Venomous X/Ultra Kaze 3000rpm combination. One quick thing, make sure that the drivers are up to date for EVERY component inside of and attached to your computer, and make sure your bios is up to date as well.

i7 950 D0gigabyte GA-EX58-UD3R moboCorsair TR3X6G1600C8D Dominator 6 GB 3 x 2 GB PC3-12800 1600MHz 240-Pin DDR3 ramCoolmaster Real Power 850w power supplyCoolermaster 212 air cooledEither I get a blue screen on boot, or when running Prime95 it errors out quickly. No cooling issues right now I run max 60 deg Celsius when Prime95 is testing 100% on all 4 cores

Any particular reason why I should set AA ingame as well as nhancer?

It's all about the Enhance option, which works now with FSX as it should, as Ryan said in the post you yourself quoted :( :

the "Enhance" option in the Nvidia driver now works - this tells the card to take whatever the game engine is ordering up and then enhance it to whatever level you've specified. You're going to get the same AA level you got with the override method, but it's now being done the way ACES intended it through the engine itself and not forced on. I don't know what if any performance optimizations are present when doing it this way, but it's quite possible there are some. (ie, the engine-AA is more selective in how it applies the effect vs. just brute forcing it onto the entire scene)

So:- if you only enable FSAA in FSX, FSX will tell the GPU what to 'FSAA' but with a rather low quality level of FSAA;- if you only enable FSAA in nHancer the whole scene will be forced to use the higher quality FSAA you chose (a rather brute way)- if you enable FSAA in FSX and nHancer and enable the Enhance option, FSX will tell the GPU what to 'FSAA' and use the higher quality FSAA of your choice (it will enhance the FSX FSAA to the drivers FSAA)

ALLOW_SHADER_30 simply allows FSX to make use of SM3.0 for Water Effects, because they are the only shaders compiled using SM3.0 everything else is either 2.0 or 1.1 This was a 'compatibility' or design decision I suppose. so, DONT USE if you have old hardware. SM3.0 is DX9c only.AffinityMask=12 yes, reduces thread collisions and FSX scales well up to 3 CPU. after that, you are wasting CPU cycles. There is no performance impact here, so don't worry. And remember, even though affinity mask=12 only makes two cores active (core2 and core3) you'll STILL have activity in CORE0 because the fiber system is NOT bound to the Affinity mask vale, so, even AffinityMask=12 will make use of 3 CORES's for FSXIn the 'BufferPools' section, I included ALL values for all situations, so the ONLY value you want to change there is UsePools (which is an ON/OFF switch)so, that way, you have the choice to either run with no BufferPools OR run with BufferPools, but using the most efficient way of doing so.As for what is RejectThrelshold, you'll need to search the forum for that to see my previous posts. Think of it as the 'Alternative' Holy Grail to BP=0UsePools=0 will IGNORE PoolSize and RejectThresholdUsePools=1 will use a BufferPool with the size you specify in PoolSize

Been trying to find the thread that discusses RejectThreshold. Can anybody provide the link?Thanks

Been trying to find the thread that discusses RejectThreshold. Can anybody provide the link?Thanks

Did you try a search?

Did you try a search?

There are about five threads concerning the new tweaks that you have introduced. I would like to suggest that they now be summerized into the sticky at the top.

I tried the BP=0 tweak with succes (been using it for quite some time now) but I decided to see what happened if I simply copied bojote's cfg from A to Z and then change the ingame settings to my preference: I didn't expect much of it but it works like a charm. FSX seems even smoother and more stable than before (with the BP=0 tweak but not all other tweaks). Don't know exactly what helped getting this results (there are a LOT of tweaks in that cfg) but on my i7 [email protected] and GTX285 it even improved things more (specially stability and smoothness when looking around with the TrackIR). I never was a fan of copying entire cfg's (specially when it contains stuff and links to stuff I don't even have), but well... it worked out fine here. Use at your own risk, though, and YMMV!

When you posted this, I tried it out as well. Great results, and a similar experience to yours. For a file that is supposed to be "personalized" to each computer, I'm quite shocked. Then again, i'm not shocked at this awesome community for uncovering these new tweaks. :(

There are about five threads concerning the new tweaks that you have introduced. I would like to suggest that they now be summerized into the sticky at the top.

I'll be contacting David so he can also add links to them from the pinned one. I'll do it later, kind of busy now with some stuff.

I followed a few guides and can't get windows stable with 4ghz. I must be setting voltage wrong or something, but windows boots up, and a test program like prime95 quits after 30 seconds with an error message and check the log.

I made that post with my bios settings in the hardware section that I said I would do.

Thanks Shane, somebody responded to my post in another forum and I have tweaked it a little, so far I am running 4ghz now, stable. Will go up to 4.2 eventually. I'll try your settings because previously I was unable to go above 4 without prime95 crashing quickly

Thanks Shane, somebody responded to my post in another forum and I have tweaked it a little, so far I am running 4ghz now, stable. Will go up to 4.2 eventually. I'll try your settings because previously I was unable to go above 4 without prime95 crashing quickly

My i7 920 D0 took pretty high voltage to get stable, so you may be able to get away with a lower core and QPI voltage than me.