Guys, I need help here. I tried cleaning upgrading to the latest nvidia driver last week. I tried a couple different AA settings in Inspector (8xS, 8xSQ, 16xS). I rebooted. Nothing has worked. I duplicated the settings from this thread and when I run FSX, I get no AA. If I turn AA on inside FS, it looks great. If I turn it off inside FS, the drivers don't seem to be overriding FS's selection of "no AA thanks." Don't know what causing this. Even go into the Nvidia controller doesn't override the fsx setting. Please explain to me how I should do.

I hope this helps.  Remember that a driver upgrade resets the gaming profiles.  Go to your FSX profile in Inspector and make sure you reselect FSX.exe and add it.  That should work for you.  I do keep AA enabled in FSX and aniso filtering.  I've attached my Nvidia settings to help.  Like you, I had no AA in FSX until I did this, now it works great (or at least the way it was, which was good).

 

JC

 

My question is that according to the tweaking guide, you should not have the AA setting in FSX checked, instead yo should use the Nvidia inspector to set the AA. Otherwise, you would be using the same AA from the FSX not the Nvidia one. The problem I'm experience here is that no AA at all after I use the inspector if no AA checked in FSX. Please help if someone also know the solution. My inspector setting worked well before only after upgrading to the most updated 332.21 driver.

My question is that according to the tweaking guide, you should not have the AA setting in FSX checked, instead yo should use the Nvidia inspector to set the AA. Otherwise, you would be using the same AA from the FSX not the Nvidia one. The problem I'm experience here is that no AA at all after I use the inspector if no AA checked in FSX. Please help if someone also know the solution. My inspector setting worked well before only after upgrading to the most updated 332.21 driver.

 

I helped with many of the tweaks....  The Affinty mask tweak which many have taken credit for was mine, for instance.  Setting AA or not setting AA in FSX might have an impact on some systems--it has no negative impact on mine--I just leave it set.  There are also some other tweaks from Bojote's site which I applied then removed, because they had a negative impact peformance wise.  With the settings above I get great performance, anti aliased aircraft and most important, AA'd ground textures and AA'd cockpits.

 

Just curious, did you try my suggestions?  Did you restart FSX after trying them--remember the settings look for the FSX excutable.  Worse comes to worse, turn AA off in FSX, observe what you see--look at the top of an instrument panel and look at the aircraft.  If you want to see what my FSX looks like--look at some of my screenshots in the screenshots forum i.e:

 

http://forum.avsim.net/topic/431929-some-more-to-share-over-a-photoreal-southwest

 

I get a smooth locked 30 fps which I love, and great looking photoreal scenery.  About the only thing I sometimes change in my Nvida config is my Aniso setting.  May be placebo, but sometimes 16x looks better to me which differs from what some of the Nvidia tweaks suggest.  My suggested AA setting you see is an absolute must, btw. 

 

What tweaks do I leave out from Bojote's site?  Namely the ones related to TextureMaxLoad which caused a memory leak and stutters over time on my system (it would surface since I use photoreal scenery about 45 mins into a flight).  The best tweaks from his site were the Bufferpools tweak and Highmemfix--great results on my video card.  I have had FSX running as long as 48 hours since I like to sometimes pause a flight (to eat, for instance)....  The good thing if you use his site is his app will tailor the tweaks based on your system.  You can back out the ones that don't work.  Here is a link--it is the best site IMHO since it consolidates just about every known tweak there is.

 

I was on two MSFS beta's, by the way--FS2004 and FSX although I only observed the FSX beta since my system way back then could not handle FSX.  Even by today's standards my system is slow for a cpu bound app like FSX but the results have always been good for me.  IOTW, the beta participation evolved many of the tweaks that have come since and they were a collective effort from many MSFS old timers like meself.

 

John

Guys, I need help here. I tried cleaning upgrading to the latest nvidia driver last week. I tried a couple different AA settings in Inspector (8xS, 8xSQ, 16xS). I rebooted. Nothing has worked. I duplicated the settings from this thread and when I run FSX, I get no AA. If I turn AA on inside FS, it looks great. If I turn it off inside FS, the drivers don't seem to be overriding FS's selection of "no AA thanks." Don't know what causing this. Even go into the Nvidia controller doesn't override the fsx setting. Please explain to me how I should do.

 

Hi all. I had the same problem, the Nvidia inspector doesn't override because the Nvidia Driver is corrupted, the solution is uninstall the driver, clean up registers and re-install the driver that's all.

 

Carlos R.

Problems with the profile can often surface when the driver is updated.
 
Near the top of this page explains how to restart the NVidia profile which I think is causing your issue: more about using CP, and NI, for DX9, DX10, and DX11 here. Note that AA settings depend on which version of Direct 3D (DX) is in use.

Whenever I update the Nvidia driver (or change my graphics card) I do the following:
01) Delete the C:\Nvidia folder on my C: drive.
02) Uninstall the existing driver (and any other Nvidia graphics software installed with the driver package).
Then reboot and let Windows install a generic graphics driver - do not let Windows install a Nvidia driver automatically!
03) [Apparently this step is not essential for recent Nvidia drivers]
Use Driver Sweeper to check all Nvidia graphics components are removed (Driver Sweeper has been superseded by another application but I haven't used that).
Then reboot.
04) Delete the NvidiaInspector application folder (back up your profiles if you want - but beware if the profiles are somehow corrupt! So I just remember the various settings).
05) Delete the FSX cfg file (back up any individual tweeks to a text file).
[i've never done this but at this point you could also delete the current FSX shader cache]
06) Install the Nvidia driver (make sure there isn't any Nvidia bloatware c### installed with it!).
Then reboot.
07) Use the RUN command and "msconfig" to actually check that no Nvidia bloatware c### is running on system startup! I just wanted the display driver, the control panal and PhysX installed.
08) Set up your NvidiaInspector profiles (check the profile is pointed to the correct FSX.exe file, and use appropriate settings for either DX9 or DX10).
09) Run FSX and let it rebuild the cfg file (and shader cache if you deleted it).
Close FSX.
10) Edit the FSX cfg file with your tweaks (remember some tweaks that you manually add to the cfg file will automatically revert to their default values if you change any graphics settings from inside FSX).

I'm wondering if your AA issues are to do with a corrupted FSX shader cache???
Q) Are you using DX9 or DX10? (Perhaps you've accidentally ticked DX10 Preview Mode in the FSX settings but are using DX9 settings in NvidiaInspector?)

Make sure the very first line in the AA section:

 

Behavior Flags is set to "none"

Display Driver Uninstaller is the de facto Nvidia driver removal tool today.

 

http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

 

Not quite sure why we've resurrected a topic from the beginning of 2014 with such outdated information ?

Display Driver Uninstaller is the de facto Nvidia driver removal tool today.

 

http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

 

Not quite sure why we've resurrected a topic from the beginning of 2014 with such outdated information ?

Hi there, I was wondering if it sufficient to do a clean install under advanced options when installing the latest driver or do I need to use the third party software to mentioned?

 

And could someone confirm if it is necessary to delete the Nvidia Inspector application folder before installing a new driver? I had not heard this before. Thank you

If you are running FSX DX10, you can not control AA within NI. (NI does set transparency AA and AF though). You have to set AA in FSX, and set an AA level within the DX10 fixer program, if you want greater then the default which I believe is 2X. I have mine set to 8xCSAA! If you are using DX9, then you need to set The Anti Aliasing Behavior Flag to None, the Anti Aliasing Mode to Override any application setting. and set an AA level. Make sure AA is unchecked in FSX.

... do I need to use the third party software to mentioned?

 

As I mentioned using the uninstallers is optional with the newer drivers, but considering that many gamers and flightsim folks use them it might be a good idea.

 

... such outdated information ?

 

I did link to Display Driver Uninstaller in my previous post. The method I posted has always worked for me when updating the Nvidia driver. My current system is rather outdated so I should probably take a look at Display Driver Uninstaller which perhaps is more suitable for newer systems.

 

And could someone confirm if it is necessary to delete the Nvidia Inspector application folder before installing a new driver?

 

No, you don't *have* to delete the folder NI is running from. I should mention that I put NI in it's own folder in Program Files for housekeeping, you could probably run NI from any local disk. I just prefer to start with a new NI and to set up my NI profiles from scratch after a new display driver install; then I can rule out a corrupted NI application or corrupted profiles if I find any issues.

 

 

No, you don't *have* to delete the folder NI is running from. I should mention that I put NI in it's own folder in Program Files for housekeeping, you could probably run NI from any local disk. I just prefer to start with a new NI and to set up my NI profiles from scratch after a new display driver install; then I can rule out a corrupted NI application or corrupted profiles if I find any issues.

 

I did actually mean the profile, it wouldn't make much sense to delete the application folder- my bad. This is something I will start doing as I only use a couple of tweaks in NI anyway. Thanks Djang0!

 

 

10) Edit the FSX cfg file with your tweaks (remember some tweaks that you manually add to the cfg file will automatically revert to their default values if you change any graphics settings from inside FSX).

 

In relation to this point Django, do you know where FSX gets the screen resolution values from? I have two monitors both 24" but my main one is 16:9 and my instruments monitor is 16:10. Until I upgraded to a GTX 980 from a 780 I could never get the resolution I set for it in the Nvidia Control Panel, it was always considerably lower and everything looked blocky. It seems to be working now, but I would like to know for future reference in case I have similar problems with future monitor upgrades. Thanks

As far as NI and new Nvidia driver installs is concerned, I prefer to start from scratch so I literally delete the NI exe and any other associated files, profiles etc. Since NI is 3rd part and not officially supported by Nvidia I want to avoid obscure incompatibilities with NI and new drivers... who the hell knows how and why... with FSX if it can happen it will!

 

 

 

... do you know where FSX gets the screen resolution values from?

 

In short - no! In the FSX settings each display should appear (drop down box) with accompanying options for you to set the resolution. Perhaps the issue you were having was due to a compatibility issue between different display interface standards (e.g. I believe that the GTX9## supports newer HDMI revisions than the GTX7##). Windows might present a default resolution for one display when there is an incompatibility between display connection standards [guess].

Q1) What kind of cables/interfaces were you using, VGA, DVI, HDMI, Display Port etc?

Q2) What resolutions and frequencies did you want to run the displays at?

Q3) What are the model numbers of the displays?

Q4) What Windows version are you running?

Q5) Did you try setting the screen resolutions in Windows? I always set screen resolutions from Windows.

Q6) I assume you're running FSX in full screen?

 

 

Q1) What kind of cables/interfaces were you using, VGA, DVI, HDMI, Display Port etc?
Q2) What resolutions and frequencies did you want to run the displays at?
Q3) What are the model numbers of the displays?
Q4) What Windows version are you running?
Q5) Did you try setting the screen resolutions in Windows? I always set screen resolutions from Windows.
Q6) I assume you're running FSX in full screen?

 

Q1- I was originally using two DVI cables but after one stopped working I replaced it with a 

IBRA® 1.5m High Speed v2.0/1.4a HDMI Cable. This is connected to my main monitor which has a native resolution of 1900x1080. The second monitor which has a native resolution of 1900x1200 is still connected by a DVI cable. 

Q2- I'm running the main monitor at 1080 and 60Mhz and with the second monitor I tried both it's native resolution and forcing it run at 1080 also at 60Mhz

Q3- The main monitor is a AOC G2460PQU 24" Widescreen 144Hz 1ms Gaming LED Monitor and the second monitor which I bought back in 2008 I think is a Acer G24 Widescreen Gaming LCD Monitor.

Q4- I running Windows 7 64 Bit professional.

Q5- I can't say for sure that I set the resolution in Windows, I would always use the Nvidia Control Panel and both monitors displayed as expected.

Q6- Yes, I am running FSX in full-screen.

 

When I get a third larger monitor I was considering switching all the cable connections to DisplayPort as the 980 has three of those ports. Would you recommend that or should it make any different. My current display situation has both monitors running at 1900x1080 in everyday Windows use but in FSX since switching from the 780 to the 980 and rebuilding the fsx.cfg file, the second monitor is now displaying at 1900x1200. I'm perfectly happy with that, and I hope I don't encounter any more anomalies when I add a third display with a higher resolution. There's so many variables involved that it just makes my head hurt! I'm sure the different cables connecting the monitors to the GC are significant, but unfortunately not in a way that I fully understand despite researching the three main variants (all of which have different version numbers and therefore different capabilities, such as bandwidth). The different aspect ratio of the second monitor might be a factor as well, but I'm sure there's a lot of simmers using monitors of different resolutions and aspect ratios in tandem

I appreciate you taking the time to help and I know how hard it is to troubleshoot a PC problem without having access to it's various settings.

I'm probably due a graphics driver upgrade and I'll make sure to delete the entire NI folder this time. 

Thanks again.