Could be expecting too much then! Thanks all for your input.

Try to play with the fiber frame.

If you have low values (0.10-0.209 you gain fps but can more easily have blurries.

If you increase this value to 0.40 or more, you will reduce blurries losing fps.

If you don't have this line in the cfg the default value of 0.33 would be used.

I found my limit in

FIBER_FRAME_TIME_FRACTION=0.25

but my cpu is slower then yours so you can try lower values.

 

Another blurries generator is

MAX_ASYNC_BATCHING_JOBS=3

but eliminating this line in FSX can introduce stutters (in P3D I deleted it).

 

Best Luck

Here's something you might want to try.

 

 

I've also changed the MinFilter, MagFilter to Anisotropic (was Linear), and the MipFilter to Linear (setting this to Anisotropic caused shimmering so I left it at Linear). The LODBias is set to -1. The file is locaed in the ShaderHLSL/Common/Common.FXH.

This is interesting... could I get you explain what those parameters are and how your changes improve the blurries?

I've had some blurries myself, and in my case it was all about zoom. In outside view I used to have a zoom level of 1.0, but when changing it to 0.5/0.4 things got alot sharper and crispier.

Any chance you could post a screenshot where you're zoomed all the way out?  I know Jim mentioned not many people fly in spot view, but I do all the time once I get to altitude and the autopilot is doing well because I want to see the scenery.  The screenshots you've posted it is kind of hard to tell if you're just looking off at terrain in the distance that definitely is going to start blurring out, or if you have an actual problem.  If you can zoom all the way out to 0.3 zoom and post a shot that would be great.  If you have blurred textures directly under the plane you definitely have a problem.  Otherwise it could be either an aniso problem or a LOD range thing combined with being zoomed in.  I'm generally always zoomed all the way out in spot so I can take in as much as possible (yeah the fisheye is a bit annoying but I deal with it, too bad you can't change spot distance like in FS2004 and earlier)

The more I think about it, the more I think it's just the zoom and that this is normal and I am just being too demanding.

 

You're right in that when I'm zoomed all the way out things are much crisper. I guess I just expected that when zoomed in the sharpness would remain but I think I've been over optimistic!

We have similar PC specs, I have all the "Terrain Settings" sliders maxed to get the best results. Here's my settings.

 

I use SweetFX 1.4 which also adds sharpness plus a lot more to the quality.. (Still tweaking settings to get it just right)

 

 

These settings work well in most cases and may need to be turned down a little depending on the add-ons involved and location plus all the other variables.

 

I never touch these settings anymore, been like this for a few months now.

 

Here's my card.

We have similar PC specs, I have all the "Terrain Settings" sliders maxed to get the best results. Here's my settings.

 

I use SweetFX 1.4 which also adds sharpness plus a lot more to the quality.. (Still tweaking settings to get it just right)

 

 

These settings work well in most cases and may need to be turned down a little depending on the add-ons involved and location plus all the other variables.

 

I never touch these settings anymore, been like this for a few months now.

 

Here's my card.

 

Your inspector settings certainly seem to have sharpened things up a tad, thanks!

This is interesting... could I get you explain what those parameters are and how your changes improve the blurries?

 

In other software that I use, they had an issue called "texture popping", which around here people call blurries (same thing). So I decided to investigate a bit.

 

The MinFilter and MagFilter has something to do with resizing mip levels (upscaling or downscaling). May help wth the zooming in and out with the camera, but I haven't tested it yet.

 

The way I've been told LODBias works is that an LODBias of 0 will load the default mipmap (FSX default setting). An LODBias of -1 will load the next highest resolution of mipmap (sharper, clearer textures). However, an LODBias of 1 will have it load the lower resolution textures (blurrier textures). I haven't had many blurry textures setting mine to -1. Least it wasn't noticeable.

 

You could probably achieve the same thing by going into Nvidia Inspector and changing the LODBias to a negative value. Probably easier too. Just set the LODBias to -3.00, which is the max it will allow without resorting to a custom settings file.

 

There is a limit to this tweak though. Just don't buzz the treeline at 400 knots and it should work. I managed to fly around KJFK at a speed of 250 knots (altitude of around 1000 feet) without any issues.

BA757,

 

Your settings:

 

'Antialiasing - Transparancy supersampling:   4x Sparse Grid Supersampling'

'Antialiasing  Setting:  8x SQ'

 

Especially the  4x Sparse Grid Supersampling  is very hard on the system even for a GTX-670.

 

You are better off with   2x SGSS (with a little water shimmering) and  8x S instead.

 

And despite of NickN's advice i am still better off with  FIBER_FRAME_TIME_FRACTION=0.15 on my system.

 

I tried really EVERY method for tuning my FSX  (NickN, Bojote, Word Not Allowed, ....)  during 2 years and i never found any better than Word Not Allowed's Tuning Guide :

 

http://#####.wordpress.com/fsx-software-and-hardware-guide/

 

Now i enjoy the best possible flying in FSX instead of endless tuning!

 

^_^

BA757,

 

Antialiasing - Transparancy supersampling:   4x Sparse Grid Supersampling

Antialiasing  Setting:  8x SQ

 

Especially the  4x Sparse Grid Supersampling  is very hard on the system even for a GTX-670.

 

You are better off with   2x SGSS  and  8x S instead.

 

And despite of NickN's advice:   after lots of trying:  FIBER_FRAME_TIME_FRACTION=0.15  is still the best setting on my system!

 

I tried really EVERY advice and method for tuning my FSX during 2 years and i NEVER found any better than  'Word Not Allowed's Tuning Guide'

 

It's all in here :

 

http://#####.wordpress.com/fsx-software-and-hardware-guide/

 

Now i enjoy the best possible flying in FSX instead of endless tuning!

 

^_^

Your inspector settings certainly seem to have sharpened things up a tad, thanks!

You're welcome.

Thanks Bart! Will play around some more!

BA757,

 

Antialiasing - Transparancy supersampling:   4x Sparse Grid Supersampling

Antialiasing  Setting:  8x SQ

 

Especially the  4x Sparse Grid Supersampling  is very hard on the system even for a GTX-670.

 

You are better off with   2x SGSS  and  8x S instead.

 

And despite of NickN's advice:   after lots of trying:  FIBER_FRAME_TIME_FRACTION=0.15  is still the best setting on my system!

 

I tried really EVERY advice and method for tuning my FSX during 2 years and i NEVER found any better than  'Word Not Allowed's Tuning Guide'

 

It's all in here :

 

http://#####.wordpress.com/fsx-software-and-hardware-guide/

 

Now i enjoy the best possible flying in FSX instead of endless tuning!

 

^_^

 

+1

 

Best advice in my opinion. I have tried all posible approaches, and this one really makes a difference. 

 

About Nick's and any other advices: Just try and see how it works for you. Everything can sound well untill you put that in practice and get a slideshow ))

I like Word Not Allowed's practical aproach.

 

I agree that in theory FFTF should not work, but in practice - why i'm getting higher FPS and better smoothnest when i set lower value? I tried once to folow tweaks and philosofy by one very knowledgeable person, and i ended with 8-10 worse FPS and slideshow, despite vsync tweak. FSX + Windows(OS) + PC are to complicated to work like in theory. So, you never know until you try...

In other software that I use, they had an issue called "texture popping", which around here people call blurries (same thing). So I decided to investigate a bit.

 

The MinFilter and MagFilter has something to do with resizing mip levels (upscaling or downscaling). May help wth the zooming in and out with the camera, but I haven't tested it yet.

 

The way I've been told LODBias works is that an LODBias of 0 will load the default mipmap (FSX default setting). An LODBias of -1 will load the next highest resolution of mipmap (sharper, clearer textures). However, an LODBias of 1 will have it load the lower resolution textures (blurrier textures). I haven't had many blurry textures setting mine to -1. Least it wasn't noticeable.

 

You could probably achieve the same thing by going into Nvidia Inspector and changing the LODBias to a negative value. Probably easier too. Just set the LODBias to -3.00, which is the max it will allow without resorting to a custom settings file.

 

There is a limit to this tweak though. Just don't buzz the treeline at 400 knots and it should work. I managed to fly around KJFK at a speed of 250 knots (altitude of around 1000 feet) without any issues.

 

With so many variables (and I already had my system configured reasonably well), it's a bit hard to tell for sure, but I tried you 'common' shaders file changes suggestions and that may have improved things a bit for me. Thanks!