I'm very grateful to Nick for his NHancer settings for FSX. I use them and they're so easy and great to click on (once you save the settings) especially after changing video drivers or making changes to FSX that don't quite work the way you want them to.But....I have a question!Are these settings still considered to be the ideal settings? I mean with Windows 7, the recent improvements in NVidia drivers, and all the recent scenery addons, FSX has undergone some serious changes.Is it time for Nick to re-examine these settings and check the validity of the choices for FSX or doesn't that really matter? I know, for example that my screens under 2.5.7 version don't exactly match the screens that were first posted at the SimForum site....http://www.simforums.com/forums/forum_posts.asp?TID=29041. I love my settings in FSX, but just wondering if anything recently has resulted in a need to re-examine all the parameters in NHancer.Stan

I'm very grateful to Nick for his NHancer settings for FSX. I use them and they're so easy and great to click on (once you save the settings) especially after changing video drivers or making changes to FSX that don't quite work the way you want them to.But....I have a question!Are these settings still considered to be the ideal settings? I mean with Windows 7, the recent improvements in NVidia drivers, and all the recent scenery addons, FSX has undergone some serious changes.Is it time for Nick to re-examine these settings and check the validity of the choices for FSX or doesn't that really matter? I know, for example that my screens under 2.5.7 version don't exactly match the screens that were first posted at the SimForum site....http://www.simforums.com/forums/forum_posts.asp?TID=29041. I love my settings in FSX, but just wondering if anything recently has resulted in a need to re-examine all the parameters in NHancer.Stan

I believe he is constantly updating as I think he first wrote the article for Vista systems and I now see he has Windows 7 info added. I use his settings as recommendations or suggestions as I don't believe everyone owns an I-7 920, o/c'd to 4.0GHz with a Windows 7 64 bit OS and with 6GB of memory. He does supply a lot of valuable information on various FSX settings that helps provide for a more enjoyable FSX game experience.Best regards,Jim

Stan, in case you hadn't seen them, follow your own link and scroll down to where it says "THESE IMAGES ARE FROM NHANCER 2.5.7", only thing I'm seeing in nHancer that's not on the captures is ambient occlusion, but that is not supported in FSX. And I assume not in FS9, which is what I use. (FS9 or FSX, nHancer settings are identical.)There's also some mention of W7, doesn't seem much different from Vista, concerning these settings.Although new stuff may be available for FSX, unless someone has been hacking away at it, FSX itself does not change... If I were you, I'd be flying, instead of wondering. Certainly with a system like that...:(

Plus (and I will probably get flamed to death for saying this, but I don't care) the crux of Nick's Setup Guide is based...RIGHTFULLY SO...on the basis of establishng a STABLE FSX platform FIRST...and THEN trying out certain FSX "specific" tweaks. I honestly think this fact is lost on many members of the community.As an example (and here is where I am putting on my flame-retardant suit), Nick's guide says the LAST "tweak" anyone should try is changing the FSX Bufferpools value, only AFTER using the rest of the setup guide to establish a STABLE FSX platform to begin with. Why? Simple...any tweak that may result in different results for different users based on their own hardware\software configuration SHOULD only be tried on a individual basis for the individual user. If it then works, fine. If it doesn't work, you should not be changing any OTHER settings that ORIGINALLY made your system stable for FSX to begin with, JUST to get the "new tweak" to work.I'm all for finding new things that may enhance our FSX experience, but it needs to be done with some common sense. There are people in the current Bufferpools thread that had computers that ran FSX outstandingly before the new BP tweak surfaced. They tried it, and it didn't work on THEIR computer. But what are some of them doing now? Changing the settings that made everything work BEFORE...including many of Nick's setup guide settings...in order to try to get the new tweak to work. Seems like that is putting the cart in front of the horse. Heck...some of them are even saying things like, "I finally got it to work, but I don't know how I did it. So I'm turning off my Updates so nothing will get changed in the future and screw it up." That's nice...disable your main OS security updates so you can use a tweak for FSX. Hmmm...Not to mention the ones who are going to trash their current $300 GPU and buy a new $600 one...just to try to get a new tweak to work.Like I said, I'm all for experimenting with new ideas and concepts, and have nothing personally against anybody in that thread. Tweak your hearts out. But it should be done in a manner that makes sense. A tweak that IMPROVES FSX performance should NOT work by forcing you to turn DOWN settings you already have in FSX that worked outstandingly BEFORE you tried the tweak. It should also NOT take a STABLE FSX platform and turn it into an UNSTABLE one. That's a definite violation of the concept of, "If it ain't broke, DON'T fix it!"AIRPLANE MECHANIC: "Hey, Captain! We just "tweaked" your aircraft so it perfoms much better. But it only lasts for 30 minutes, and then all your engines quit."CAPTAIN: "Say WHAT ????" Use Nick's setup guide. It is still very valid for most nVidia GPU users (combined with making sure the rest of your computer is also setup and maintained correctly). Then use any other tweaks with caution. If they turn your stable FSX experience into an unstable one, then the tweak is not necessarily what you want to be doing to your FSX.

Stan, in case you hadn't seen them, follow your own link and scroll down to where it says "THESE IMAGES ARE FROM NHANCER 2.5.7", only thing I'm seeing in nHancer that's not on the captures is ambient occlusion, but that is not supported in FSX. And I assume not in FS9, which is what I use. (FS9 or FSX, nHancer settings are identical.)There's also some mention of W7, doesn't seem much different from Vista, concerning these settings.Although new stuff may be available for FSX, unless someone has been hacking away at it, FSX itself does not change... If I were you, I'd be flying, instead of wondering. Certainly with a system like that...:(

Thank you. I see the settings below. Sorry, I missed those. I did see one change I had to make (Max Performance). Appreciate the input.Stan

No problem. I actually saw one setting I had to change, multi core versus single core. I had been using XP for years, so it has always been on single core. Only switched to W7 at the beginning of this year, but never payed attention to that setting and Nick's suggestion. Will change and maybe notice a difference.:(

No problem. I actually saw one setting I had to change, multi core versus single core. I had been using XP for years, so it has always been on single core. Only switched to W7 at the beginning of this year, but never payed attention to that setting and Nick's suggestion. Will change and maybe notice a difference. :(

I had to change one of his settings too. the LOD Bias (I think it was) set to "clamped". I got horrible texture flickering with that on. I still get occasional flickering, but it's greatly reduced when I disable that.Everyone's system is different, like our fingerprints. Even people with same hardware will experience differences. Intel will tell you that no two cpu's they make are perfectly alike. There are so many variations involved with FSX that Nick's guide can only be used as just that ... a guide, not a statement of objective facts. Not to mention we all use different add-ons as well. Making all this stuff work together is like trying to balance an egg on the head of a nail. And for what it's worth, BP=0 for me was a disaster. I got the most ungodly texture flashing you've ever seen. Sky, ground, VC, you name it. And I have the same hardware setup as a person I've seen say that it was a godsend.

I've followed Nicks guide to the letter 3 times now and can't get my 9800 GTX Nvidia to anti alias in FSX with FSX.IAN

If it's not applying AA: Did you create a new profile for FSX and delete the .exe in the default profile?

I've followed Nicks guide to the letter 3 times now and can't get my 9800 GTX Nvidia to anti alias in FSX with FSX.IAN

Maybe you changed settings in FSX, nHancer AND the nVidia CP...? Using nHancer and the nVidia CP at the same time isn't a goof thing. Pick the one you want to use and stick to it, otherwise indeed some options won't have an effect anymore. If you are REALLY stuck, uninstall the nVidia driver AND nHancer, use Driver sweeper in safe mode and then restart and install the driver again, and nHancer if you need to.As far as NickN's settings are concerned: use them as a base and work from there. I've changed quite some settings to get more out of FSX than I would get with his guide alone.

Chapstick is correct. Start by totally deleting any previous profile you created for FSX in nHancer, then create a new one from scratch. Sometimes trying to edit an existing profile will not work. I've seen this hapen on people's computers I helped them set up.And there should not be a need to choose one or the other when it comes to nhancer or the nVidia Control Panel. If you make sure the "Allow Override of Predefined Settings" option is checked in nHancer, the nHancer settings will override any nVidia Control Panel profiles, including the one in the Control Panel for FSX.Also, make sure you are using the correct version of nHancer for your video card driver you have installed.