Those two display entries don't affect negatively. FSX creates 0.0 entry for DX10, so you can have different AA and aniso settings for DX9 and DX10. They do not cause blurries in any way.

 

Hate to disagree but where did you find this info? There are two display settings ONLY if you have more than one monitor installed. I got my info from Word Not Allowed's guide and I have seen it in other places too. If you have DX10 enabled, the only line changed is d3d10=0 for off and =1 for on. The fsx.cfg is very similar to DX10 and DX9 except for this setting. For sure, you should have AA and AF turned on in DX10 and some people like to use their video card drivers to run AA/AF in DX9 but I think that is rare. FSX likes AA/AF settings enabled no matter what's running. Can you provide documentation regarding your statements?

 

Best regards,

Jim

I would turn down the Mesh Complexity to about 80 for starters. If you really need all these tweaks on your kind of system you should not be running any scenery sliders all the way to the right. IMO anyway.

 

Get rid of the Max_Async batch jobs line.

Get rid of the swap wait timeout.

Which OS btw? Your system specs don't tell us too much.

TEXTURE_BANDWIDTH_MULT=40

MESH_COMPLEXITY=80

TextureMaxLoad=6

cars lowered to 5

 

With all these changes along with a fresh new fsx.cfg (second monitor vanished) i must say that it's running better. Now I can fly longer before the non-loaded areas left behind. As soon as i'm on the ground all the scenery loads up in no-time.

Funny as i was wondering just last week if i should buy an SSD and move the whole simulator there.

Daveo, it's W7 64bit. What are the lines you wrote for?

TEXTURE_BANDWIDTH_MULT=40

MESH_COMPLEXITY=80

TextureMaxLoad=6

cars lowered to 5

 

With all these changes along with a fresh new fsx.cfg (second monitor vanished) i must say that it's running better. Now I can fly longer before the non-loaded areas left behind. As soon as i'm on the ground all the scenery loads up in no-time.

Funny as i was wondering just last week if i should buy an SSD and move the whole simulator there.

Daveo, it's W7 64bit. What are the lines you wrote for?

 

The same W764 Pro. I pretty much run the video stuff stock. No NV inspector or anything. Frames are unlimited AF and AA I just run thru FSX and let the NV control panel use app settings. It works for me. Very minimum of stuttering except in the normal Hi dense areas. Frame rates i could care less about. The sim runs smooth and my scenery loads fine so I leave it pretty much alone.

My Mesh complexity I run at 75

Texture bandwidth is at 70.

I do tend to run a little on the high side of AI and that is usually when I start running into issues. AI seems to be the real stake in the heart concerning FSX.

I use external limiter (30fps) through the inspector.

 

Not saying this is a source of the problem, but this definitely causes some blurring, autogen loading problems etc. in my department. I suggest you do a test with clean fsx.cfg and my tweaks. Also check the internal FSX settings. Mind the Nvidia Inspector settings too. I see that you already set up after my guide, but I see tweaks in your FSX.cfg which are not present in my guide, leading me to think you used Bojote's tool as well. These two are, as I noted in the beginning on my guide, uncompatible.

You can find it here for the reference: http://#####...hardware-guide/ (newest version) and here: http://forum.avsim.n...-guide-for-fsx/ (hopefully getting updated some time soon)

Word Not Allowed, you are fully correct. The first thing i done with my fsx.cfg (it was about an year ago) was sending it to venetubo. By this time i didn't know about your guide. In time i learned more and more about the cfg tweaking and started sticking in it the advices you're giving. As you can see the final product is messed up.. I realized that i have never rebuilt the cfg. So now that i did so i'm about to set it entirely according to your guide. For now things are better than before but sure they're not as it should be. The loading of the ground textures takes decades if i'm in the air flying. The bad thing is that it's happening with all default settings (all sliders to the right though) and entirely bypassing the nspector .. I defragmented the drive. That helped a little witch suggests me that my hard disk may need a replacement.. It served me well for about 4 years now..

Well, do a simple test: DELETE (or rename) FSX.cfg, reset Nvidia Profile for FSX, in FSX do only this: limiter to 30, LOD to 4.5 and traffic setting minimal. See if you get blurry textures. Do not omit any of these steps for starters.

I'm finding this topic very interesting as I'm having this exact same problem as the OP:

 

http://forum.avsim.net/topic/387887-ground-textures-changing/

 

I have tried all the suggestions in this topic so far but with only limited success.

 

And like the OP, I to used both Bojote's tool and Word Not Allowed's guide not realising there was incompatibilities.

 

Now to try Word Not Allowed's suggestion and let fsx rebuild the fsx.cfg

 

I don't mean to hijack, but just to let the OP others are having the same problem.

After the initial few sentances of my guide, it says:

 

IMPORTANT: If you feel like going through this guide and set up my tweaks, I strongly suggest you start doing that on the clean FSX, meaning clean fsx.cfg, no mods like ShaderMod 3, no other tweaks, especially not tweaked FSX.cfg through Venetubo tool (not saying Venetubo is bad, only that this is a different approach).

 

I wonder why people are not reading? :(

TEXTURE_BANDWIDTH_MULT=40

MESH_COMPLEXITY=80

TextureMaxLoad=6

cars lowered to 5

 

With all these changes along with a fresh new fsx.cfg (second monitor vanished) i must say that it's running better. Now I can fly longer before the non-loaded areas left behind. As soon as i'm on the ground all the scenery loads up in no-time.

Funny as i was wondering just last week if i should buy an SSD and move the whole simulator there.

Daveo, it's W7 64bit. What are the lines you wrote for?

 

Leghorn, I have been using close to the same settings you have shown above and I very seldom have blurries. However I must add that I have been converted to DX10 but still hope this will hlep. I found that by increasing my FFTF from 0,1 in small increments hleped in reducing blurries. The number that worked best for me was 0.25 or even has high as 0.33.. Unforunately by increasing FFTF also had a slight impact on FPS. Autogen is set at dense and in fsg.cfg file buildings per cell are 907and Trees per cell= 1400.

It seems i finally managed the simulator to load it's textures fast enough. The weird thing that solved my issue is:

 

TEXTURE_BANDWIDTH_MULT=800

 

That number just doesn't make any sense. But... if it works for ya... :blink:

Indeed.. I simply can't understand fsx sometimes... :ph34r:

Totally agree with Word Not Allowed! Unbelievable setting!

 

Best regards,

Jim

Guys, thanks a lot!!! It tried everyone's advice. UsePools=0 and Reject threshold=0 makes no difference here. I use external limiter (30fps) through the inspector. I have set vsync to 1/2 refresh rate. It's a single display setting.. Lowering the water detail didn't help so the only thing left now is to see is the TEXTURE_BANDWIDTH_MULT at 40.. Unfortunately I must try to have some sleep now. I will post here later if there is an improvement... Pretty exhausted after a night of proving 500 ways that don't resolve the issue :lol: Thank you, guys a lot for trying to help! Very kind of you!

 

Externel limiter used to give me blurries. I had to restrict it to a finite number of FPS within FSX. This is the first thing you need to do. Set it to 30.