I just came across this. I dont know if it has been show here before or not.. If not, here ya go... :)http://www.nzone.com/object/nzone_fsx_techtips.html

No No NO, Don't rely on this, especially for Nvidia Display driver information. For a very nice setup, follow Ryan's (Tab - of PMDG fame) advise here:http://forums.nvidia.com/index.php?showtopic=38921or reitterated here:http://forums.avsim.net/dcboard.php?az=sho..._id=23202&page=The Nvidia FlightSim2004 and FSX driver profiles are messed up.With relative hardware, there are five basic steps to a very nice FSX experience.1) FSX.cfg: Change bandwidth_multi=40 to bandwitdth_multi=200. Not much higher as textures don't appear any faster and it will begin to cost FPS and induce stutters. I know about Phil's blog on this issue, but going above 40 still has a positive affect.2) Use DiskTrix - Ultimate defrag and place your FSX folder at the top of the "performance" section of the partition and then defrag by folder/filename. I still use Raxco - Perfectdisk for the offline portion of the defrag scheme.3) Allocate more virtual memory to FSX. This was originally designed to placate the famous OOM CTD errors in FS9 and FSX but appears to also enhance performance. In WinXP, edit the boot.ini file and add "/3GB /userva=2560" on the end of the last line. Then tag FSX.exe to use more RAM by following the instructions here:http://forums.avsim.net/dcboard.php?az=sho...topic_id=399256This works if you have 2GB of physical RAM as well.I added the "/3GB /userva=2560" switches to my boot.ini file like so:Example:(boot loader) << should be bracketstimeout=0default=multi(0)disk(0)rdisk(0)partition(1)WINDOWS(operating systems) << should be bracketsmulti(0)disk(0)rdisk(0)partition(1)WINDOWS="Microsoft Windows XP Professional" /fastdetect /NoExecute=OptIn /3GB /userva=2560Good Mirosoft Articles for WinXP boot.ini:Available boot.ini switches:http://support.microsoft.com/kb/833721How to properly edit your boot.ini file in WinXPhttp://support.microsoft.com/kb/289022/How to use the "userva" swith in WinXP:http://support.microsoft.com/kb/316739/Also, along with the /3GB fix, I still use FSAutoStart (further down the AVSIM forums) to turn off all unnecessary services and processes prior to starting a flight. Use the the memory-defrag function in FSAutoStart becuase as Phil explained, not being able to allocate a free, large chunk of virtual memory can also result in the OOM CTD. If you use FSAutoStart to defrag your memory and have 2GB or more of physical RAM, you may see an error "couldn't defrag all memory." Ignore it, it still defrags the majority of it.4) Use nHancer and delete the existing FS driver profiles and recreate them following the links mentioned at the top of this thread. Make sure you deactivate AA in the display settings in FSX. I found the Nvidia 162.15 driver very favorable with a noticable improvement.5) Install the June '07 DirectX Update from Microsoft. Phil explained that this has the D3D virtual-memory fix that allows Flightsim to go beyond the normal 2GB user-space limit. Personally, I installed this update imidiately following the clean installation of WinXP; before any drivers or MS updates.Redistributable DirectX-dowload for all Windows flavors available here:http://www.microsoft.com/downloads/info.as...isplayLang%3denThis is all I have done since recently dropping back to WinXP from Vista-U. No bufferpools, no fiber_frame, no other manual FSX.cfg tweaks. I can't begin to explain how satisfied I am with thre results. Very stable, fluid, no stutters -- just fun. Modified textures includes TreeX v2.1, HiFiSim XGraphics, FSGenesis LC & Mesh, and Ultimate Terrain-X.Description and a few pics of my results here:http://forums.avsim.net/dcboard.php?az=sho...e=search#406791

>>1) FSX.cfg: Change bandwidth_multi=40 to>bandwitdth_multi=200. Al have you seen the info on TEXTURE_BANDWIDTH_MULT?(on Phil Taylor's blog)RhettAMD 3700+ (@2585 mhz), eVGA 7800GT 256 (Guru3D 93.71), ASUS A8N-E, PC Power 510 SLI, 2gb Corsair XMS 3-3-3-8 (1T), WD 150 gig 10000rpm Raptor, WD 250gig 7200rpm SATA2, Seagate 120gb 5400 rpm external HD, CoolerMaster Praetorian

Yup, where he suggest 40 max? I don't buy it. I still see a marked improvement in texture loading when I set it up around 160 to 200. I don't know if he got some bad info somewhere or why, but when I set it to somewhere around these numbers, my eyes tell me it's better. Higher than this, I can see micro-stutters which I'd imagine get worse on non raid-0 or 7200rpm drives.

>Yup, where he suggest 40 max? I don't buy it. I still see a>marked improvement in texture loading when I set it up around>160 to 200. I don't know if he got some bad info somewhere or>why, but when I set it to somewhere around these numbers, my>eyes tell me it's better. Higher than this, I can see>micro-stutters which I'd imagine get worse on non raid-0 or>7200rpm drives.The thing that is strange, is that TEXTURE_BANDWIDTH_MULT is a target framerate type of setting.Putting it at 200 seems like it would not be good for anyone. But then again, I have also had great results with very high numbers like 360.I don't like things that I can't get a handle on...FS seems to be full of those things....RhettAMD 3700+ (@2585 mhz), eVGA 7800GT 256 (Guru3D 93.71), ASUS A8N-E, PC Power 510 SLI, 2gb Corsair XMS 3-3-3-8 (1T), WD 150 gig 10000rpm Raptor, WD 250gig 7200rpm SATA2, Seagate 120gb 5400 rpm external HD, CoolerMaster Praetorian