Your fsx.cfg as got all sorts of errors in it, looks like you been doing cut and pste jobs and forgetting to remove certain bits or adding same bits twice.

 

Delete it and let fsx build a new one, delete your shader folders too.

 

Your rig should have no issue running fsx, I'd say that there something more linked to other aspects to your setup, than just tweaks needed in the fsx.cfg if you getting such issues. Look into how your windows installation and any other software is setup that maybe different since your new build, Also look at how your gfx card is setup even with ati card, changing settings in it can have dramatic effect on performance.

 

I agree, I noticed some things written in the wrong area of the .cfg as well.

 

The OP needs to start with a fresh .cfg and go from there being careful not to insert the tweaks into the wrong sections of the .cfg. Also for the OP, if you have Inspector setup like in Word Not Allowed's guide or Ryan's guide, you need to turn off Flitering: Trilinear in your first screen shot posted and select Anisotopic in the Flitering section.

 

Your rig should be more than capable to run the NGX well. I have a lot worse rig than you (E8400 @ 3.85ghz and 2GB of RAM) and can easily get 25 FPS or more at large hubs with 80% to 100% AI running around. Although I do get some delay in texture loading since I only have 2GB of RAM running at 1088mhz. Your settings are pretty close to mine, except I run more AI and have Lens Flare and Bloom turned off. I also only use 1024 textures for pretty much everything ie. clouds, scenery, even the NGX.

 

You might also want to have a look at NickN's setup guide for your OS to make sure you have it setup correctly to get the most out of FSX. The guide is here: http://www.simforums.com/Forums/topic34141_post198187.html#198187 starting at the post by NickN on April-11-2010 at 4:31pm.

 

Sean Campbell

Thank you for the suggestions. Just to clarify I have already deleted my fsx.cfg and the problem persisted. The cfg I posted did have some duplicate entries so one again I deleted it and started over with a fresh one. I also followed the various FSX tweaking guides (Word Not Allowed, Ryan, Nick, Bjote) seperately with the same results. My frame rates aren't bad actually....locked using Inspector at 30 and they never go below that. The problem is the missing textures for 2 or 3 seconds when switching views.

 

I read one of the forum posts (cannot remember which one it was now) that suggests when using Inspector you should set your filtering to Triliinear in FSX, not Anisotropic. Honestly I have tried both and don't notice any difference. I do not have this problem in the Level D 767....only in the NGX. The odd thing is that on my old system using an ATI 5850 didn't have that problem...ever. I was rather disappointed after switching back to Nvidia but since it only happens on the NGX.

 

On this new system I did a fresh install of Windows 7 Home Premium x64 and my Nvidia drivers. Whenever I update drivers I always use Driver Sweeper so I don't believe it is driver-related. I am starting to wonder if upgrading to Prepar3D would help at all. Its more of a nuisance because as I said...my frame rates are acceptable and there really aren't any stutters except the texture redraws when switching views. Maybe I will go back to an AMD card and see if it does away.

 

Again, thanks for all the feedback. These forums are great!

Thank you for the suggestions. Just to clarify I have already deleted my fsx.cfg and the problem persisted. The cfg I posted did have some duplicate entries so one again I deleted it and started over with a fresh one. I also followed the various FSX tweaking guides (Word Not Allowed, Ryan, Nick, Bjote) seperately with the same results. My frame rates aren't bad actually....locked using Inspector at 30 and they never go below that. The problem is the missing textures for 2 or 3 seconds when switching views.

 

I read one of the forum posts (cannot remember which one it was now) that suggests when using Inspector you should set your filtering to Triliinear in FSX, not Anisotropic. Honestly I have tried both and don't notice any difference. I do not have this problem in the Level D 767....only in the NGX. The odd thing is that on my old system using an ATI 5850 didn't have that problem...ever. I was rather disappointed after switching back to Nvidia but since it only happens on the NGX.

 

On this new system I did a fresh install of Windows 7 Home Premium x64 and my Nvidia drivers. Whenever I update drivers I always use Driver Sweeper so I don't believe it is driver-related. I am starting to wonder if upgrading to Prepar3D would help at all. Its more of a nuisance because as I said...my frame rates are acceptable and there really aren't any stutters except the texture redraws when switching views. Maybe I will go back to an AMD card and see if it does away.

 

Again, thanks for all the feedback. These forums are great!

 

Please keep us posted. I for one would like to know the answer to your problem, or in fact what your problem was.

 

Regards,

It sounds as if you are using an outside Framerate lock tool. It has been stressed multiple times that you DEFINITELY SHOULDN'T use any type of Framerate lock tool other than the Default FSX one to prevent complications. I recommend getting rid of any third party frame rate lock and trying it with default FSX lock.

here's my 10c.

 

Exactly, why subject your PC to another process, just to lock your framerate, when FSX sets it all up perfect anyway? I've found good performance from the PMDG737, no, make that excellent, outstanding even. The only tweaks that work well are the ones that chop trees and houses out of the view. GPUs can run hundreds of times faster than FSX could ever drive them. Programs that DLL into the FSX system slow down the show. Stick to a default fsx.cfg unless you really found a benefit with something. If you have addon airport and addon plane, and max sliders, expect no more than 15-20fps with anything not cooled in liquid nitrogen, it's the laws of physics. Best keep to a fixed fps lower than maxed will keep your fans from humming all the time and allow pre-rendering of frames ahead of time, that's how FSX is designed to work best.

Best keep to a fixed fps lower than maxed will keep your fans from humming all the time and allow pre-rendering of frames ahead of time, that's how FSX is designed to work best.

 

Very interesting. Your comment about about NOT tweaking (unless necessary) the fsx.cfg interests me in particular. So, in your opinion what "minimum" tweaks would you implement to prevent the fans from humming all the time. e.g do you think the v/sync fix (ForceFullScreenVSync=1) on it's own is a worthwhile tweak?

NOT tweaking (unless necessary) the fsx.cfg

 

And therein lies the rub.

here's my 10c.

 

Exactly, why subject your PC to another process, just to lock your frame rate when FSX sets it all up perfect anyway? I've found good performance from the PMDG737, no, make that excellent, outstanding even. The only tweaks that work well are the ones that chop trees and houses out of the view. GPUs can run hundreds of times faster than FSX could ever drive them. Programs that DLL into the FSX system slow down the show. Stick to a default fsx.cfg unless you really found a benefit with something. If you have addon airport and addon plane, and max sliders, expect no more than 15-20fps with anything not cooled in liquid nitrogen, it's the laws of physics. Best keep to a fixed fps lower than maxed will keep your fans from humming all the time and allow pre-rendering of frames ahead of time, that's how FSX is designed to work best.

 

My thoughts exactly, I used to run with a fully tweaked out FSX.CFG and had horrendous results, even had multiple OOM errors. I've since gone for a much cleaner CFG and slightly lower sliders and have a beautiful, yet smooth performance in most situations. Lots of people rely far to heavily on tweaks and tweak guides. However everyone's experience will be different. I'd personally keep everything as clean as possible unless you can prove it works for you!

Hold on...wait a tick...

 

 

 

 

 

You installed a new graphics card and everyone is involved in the FSX-obvious that it seems the most obvious issue is being ignored...

 

You installed a new graphics card, but nowhere in these posts have I seen any screencaps, or notes about your settings on the graphics card.

 

Tweaking the FSX.cfg is all well and good, but if your GPU is working off of a poorly set up profile, you're not going to see as much improvement in the tweaks as you would with a properly set up GPU.

do you think the v/sync fix (ForceFullScreenVSync=1) on it's own is a worthwhile tweak?

 

If you have a recent "twitch" first person game where the code is almost all run on the GPU and you are seeing >30fps then half sync my be worth exploring.

But in FSX you cannot get high frame rates with autogen. Say your monitor is 59refresh/sec. 3x19=57 if you set fixed19fps then there is less time for each frame to wait to sync, but with pre-rendered frames lined up it really makes no difference. I don't think an out of the box GPU setup would cause big issues of poor performance, more likely an odd hardware config problem maybe bus handling or memory, reset the firmware.Remember if you are seeing 60fps and then set fixed fps you will only see 30 since it will be halved to support the buffer.

My thoughts exactly, I used to run with a fully tweaked out FSX.CFG and had horrendous results, even had multiple OOM errors. I've since gone for a much cleaner CFG and slightly lower sliders and have a beautiful, yet smooth performance in most situations. Lots of people rely far to heavily on tweaks and tweak guides. However everyone's experience will be different. I'd personally keep everything as clean as possible unless you can prove it works for you!

 

I agree that you can play around with the FSX .cfg file too much, but there are certain so called tweaks required because "A" from what i can gather, FSX was broken to start with and then abandoned by Microsoft and "B" there are a lot of addons that have come along long after FSX was conceived and therefore FSX needs "tweaking to accommodate them.

 

I'm no expert, but that's my thoughts.

I've done a lot of testing, but not to see if i can coax more fps because I can't, or I never had results worth talking about, but rather I researched what makes FSX slow down as I can avoid that, I think that's more important. If your Ai traffic program injects too many ready to go flights, this can suddenly overburden FSX like the last straw on the camel's back. Loading any object with double the resolution texures takes four times as long as stock aircraft to load. You can reduce max texture load but only makes it blurred. The only way to get better performance is to increase the CPU throughput, use stock scenery and scenery built like stock, and stock planes, and use addons that run out of process. Everything else will slow it down. Uncheck scenery in the FSX scenery list if you are not going there that can help, makes no difference how many planes installed. A problem with the network could slow down FSX (even if you don't have another node) since simconnect could be compromised.

You installed a new graphics card, but nowhere in these posts have I seen any screencaps, or notes about your settings on the graphics card.

 

If you look at my original post you'll see links to my screenshots. I listed the driver version and another screenshot of my Nvidia Inspector settings. Which other settings would help? This was all installed on a new build so no corrupted drivers.

 

As far as using the built in FSX frame limiter versus an external limiter, there are various opinions on which is better. In my situation there is no difference as I have tried both. I also play Battlefield 3 and get excellent performance (62 FPS) with all settings maxed out but I know FSX is a different animal. Battlefield 3 utilizes 96% of my GPU and 1.8 GB of my 2GB VRAM versus FSX 36% GPU and only 713 MB of 2GB VRAM.

 

As far as sliders are concerned you will see mine are not maxed out either. As a matter of fact these are the same settings I used on my i7 860 @ 3.4 Ghz and ATI 5850 1GB GPU a few months ago before I built my new system. In my new build my frame rates increased about 5 to 8 FPS at identical settings with the Nvdia card. The difference is that now when I switch views from outside back to the vc I have the missing textures shown in my OP. I completely agree that it is unrealistic to expect 30 FPS with sliders maxed, so I turned mine down until I consistently got 30. After that is when I decided to do a bit of .cfg tweaking which did help a bit. Aside from the texture loading problem I am fairly satisfied with the smoothness I am getting. Overclocking to 4.2 Ghz didn't make a noticeable difference to me.

So if you try a stock aircraft stock scenery with default fsx.cfg and no addons, do you get the missing textures then?

If you look at my original post you'll see links to my screenshots. I listed the driver version and another screenshot of my Nvidia Inspector settings. Which other settings would help? This was all installed on a new build so no corrupted drivers.

 

Ah. Fair enough. I stand corrected, though there are a couple settings that differ from Ryan's recommendations which are giving me good results, even with AS2012 + Graphics, UTX and GEX.

 

Take a look here: http://forum.avsim.net/topic/324786-nvidia-configuration-guide-inspector-2xxxx-drivers-version-20-explanations-of-all-settings/

 

Specific differences are your supersampling is off, AA is disabled at the panel (not sure if that makes a difference versus "none"). I'd mess with your GPU settings more than your FSX.cfg first to see your results there, as apparently the FSX tweaks aren't doing much.

 

 

 

Also, I wouldn't compare FSX with other games, as FSX is well known for being poorly coded/implemented in many aspects, unlike BF and other games.