I have a somewhat powerful system (Jetline), and still, with certain circumstances....the ground texture becomes blurry.   First, here is my system:

Operating System:     Windows 10 Home Edition (64-Bit)
Chassis:                    NZXT S340 Elite Mid-Tower, Black
Motherboard:            Gigabyte Aorus Z370 Gaming 5, LGA 1151
Processor:                Intel 8th Gen Core i7 8700K (4.8GHz Overclock) 
Core                          Six Core
CPU Cooling:            Corsair Hydro Series H100i v2 Liquid Cooling
System Memory:       32GB Corsair DDR4 SDRAM 3000MHz
Graphics Processor: 11GB Nvidia GeForce GTX 1080 Ti, PCI Express 3.0
System Power:         850 Watt Corsair RM Series Power Supply
Sound Card:             7.1 High Definition Integrated Audio
Primary Drive:          1TB Samsung EVO 860 Solid State Drive (SSD)
Secondary Drive:      2TB Mechanical Drive

This scenario occurs when I'm flying FAST.  Perhaps a 737 and up.  After a while, at about 30,000 feet, the ground scenery becomes blurry.  I fix it easily.  Go to Options, Graphics, and just move slider for Autogen or any other really, from full right to one level below on the scale.  Then...it may happen again, and I do the same thing, but this time move the slider to full right!  The ground becomes clear again. You just have to change a parameter from Ultra to High....or from High to Ultra.

This never happens when flying GA aircraft, so I assume it has to do with texture loading when flying at over 300 kts per hour.

Does this happen to you?  If so, what changes can I make to my Options screen that would prevent it from happening?

Thanks,

Stan

 

Well my first question is if you are locking frames to free up CPU cycles to render textures and scenery?

 

I lock mine at 30 and it has helped tremendously in preloading textures and eliminating some blurries.

 

Regards

Yeah, locking the frames should help. On my system the sim starts to stutter a lot, even when 30 fps are achieved. But it's better than blurry ground textures and missing autogen...

Regards

Felix

Got a largely identical system to you. If you got anywhere in the world where I could take off in the default F-22 and test it (I do have the various OrbX Global, LC, all the regions etc.), somewhere you find the issue could be consistently replicated, I would love to try it, see how my own system / setup handles it.

Frame rate target setting is directly linked to terrain loading resource allocation. If you have your frame rate limiter set to unlimited, then you are basically running FFTF=0.01, or what ever the lowest value is, I don't know. This means that from each rendered frame, there is almost no cycle time allocated for terrain loading. If you set this to anything other than unlimited, then FFTF goes to 0.33, so one third of cycle time is allocated to terrain loading. Now if you fly slow, then that minimal allocation might be enough to keep terrain loading because it doesn't have to do it as much as when going at 300kts.

Some people are even able to get away without a limiter at higher aircraft speeds and that is usually because in those scenarios, high frame rates are present. If you render 100 frames per second, then that is a lot more terrain data loaded than 30 frames per second, because remember, FFTF is a fraction per cycle. The more cycles, the less fraction time you can get away with without starting to see blurries.

You can also solve this by playing around with manual FFTF entry in config file, but I really don't recommend it. One should always set a target frame rate from within sim first and then tune other settings to achieve your target frame rate.

Edited November 24, 20196 yr by Evros

8 minutes ago, Evros said:

You can also solve this by playing around with manual FFTF entry in config file...

Or use FFTF Dynamic

Greg

1 hour ago, lownslo said:

Or use FFTF Dynamic

Greg

Greg,

I read about this program.  Is FFTF Dynamic easy to use.  Does it automatically set your frames so that terrain isn't loaded beyond the computer's capabilities or what?  I think I'll buy it.  It's not that expensive and if it solves the blurry problem at fast speeds, then I'm all for it.

Thanks for the tip.

Stan

8 hours ago, spilok said:

Does this happen to you?  If so, what changes can I make to my Options screen that would prevent it from happening?

Stan -- are you running hyperthreading enabled, or disabled?

FYI i have the same cpu, and if I run hyperthreading disabled, I will get blurries unless I cut back cpu-intensive sliders.  However, with HT=on, I do not have that problem.   I run framerate unlimited with vsync on, 30 hz refresh.

9 minutes ago, Mace said:

Stan -- are you running hyperthreading enabled, or disabled?

FYI i have the same cpu, and if I run hyperthreading disabled, I will get blurries unless I cut back cpu-intensive sliders.  However, with HT=on, I do not have that problem.   I run framerate unlimited with vsync on, 30 hz refresh.

Yes.  Hyperthreading is enabled.

Stan

2 hours ago, spilok said:

Is FFTF Dynamic easy to use.

Yep, Stan it is easy to use.  There are two modes to choose from... Frames (rate) Range or AGL (altitude) Range.  I use the latter.  But it is very easy to configure, and with the two available options it can cover just about any scenario you throw at it.  This app makes choosing an FFTF value in the cfg file a thing of the past... it can give you a real dynamic FFTF based upon how you fly and your priorities. 👍

42 minutes ago, spilok said:

Yes.  Hyperthreading is enabled.

Have you tried with HT disabled?

Greg

Again and again this topic appears although millions of threads deal about it. Even if you do not like it, blurries are 99% due to overloading your CPU. So either reduce your settings until your CPU can handle it or use a frame limit. I doubt FFTF Dynamic will do a great deal unless you use a low FFTF value in your config (lower than the default value of 0.33). However, I really recommend FFTF Dynamic if you want to use rather high settings on heavy airports, there it does "wonders".

Then hyperthreading: it has NOTHING to do with hyperthreading whether or not you experience blurries. If you want to use HT, what I do without any issue, I suggest to use an affinity mask in your config, for example AM=1365 (this is what I use).

If you want, Stan, I can once send you my prepar3d.cfg. As we have basically almost an identical setup, it might help you to find the ideal setup.

You don't need any FFTF dynamic or some other sorcery. Just have two different graphics profiles. One with unlimited FPS and one without. When you are in terminal airspace at heavy airport, chances are you are going slow enough to successfully run unlimited and get maximum frames out of your setup. Higher up where you cruise at 300kts, you will have better performance anyway, but terrain loading might lag behind. In that scenario, use locked FPS because you can spare those extra frames and you'll get sharp ground textures. Not to mention lower power bill compared to letting your hardware run full-tilt full-time. Oh and did I mention it cuts down stutters by smoothing out frame delivery time?

Edited November 26, 20196 yr by Evros

Stan, would you happen to have messed around with affinity masks in the past?

8 hours ago, AnkH said:

hen hyperthreading: it has NOTHING to do with hyperthreading whether or not you experience blurries.

Then how, at identical slider settings, does my 8700K blur with HT=off, and does not with HT=on?

"You don't need any FFTF dynamic or some other sorcery. Just have two different graphics profiles"

Not going to argue about FFTF but for me, any thought of changing profiles (settings) mid- flight is courting disaster.... 60% chance of a CTD.