Is some amount of blurries inevitable...

[flyinjoe]

Maybe I just don't get what the 'blurries' refers to, but is it safe to assume that some amount of blurries is inevitable.

I've been messing around with different settings and even if I lower all my autogen sliders to nothing, try different target frame rates and change my Texture Bandwidth and Fibre Time settings, there always seems to be times when the ground texture is not perfectly clear.  You can distinguish what it is, but there's always parts that take a few seconds to become crystal clear.

Is that just normal and some amount of blur is par for the course?

[Flying Mouse]

I bought Accelaration and since I have installed it I saw a massive reduction in blurries.

I don't know why you experience blurries as I don't know your rigs specs to point to a contributor but I can assure you SP2 does make a huge difference in that field.

Otherwise make sure your graphics card drivers are up to date, since I installed the 169 Forceware Beta drivers (Had to for Crysis) for my geforce I also noted a reduction in blurries.

Also enable AA as that will reduce the alot.

SP2 and updated drivers now ensure crisp ground textures at both low and high altitudes.

Goodluck  ;)

[Wingo]

Blurries are a part of life. I like to define them into to two types. One is the type you get after changing views and looking down, at first there are blurries then they quickly sharpen as the textures load. These can be fixed by meddling with the Terrain Texture Resolution. The higher the value (e.g. 76m) the quicker it will sharpen, but the more blurrie it will look close up as there isn't much detail. The lower the value (e.g. 30cm) the slower, as there is more detail to load. With stock FSX you should set it to 1-2m, as there is no stock textures more detailed than this. Basically this type is caused due to the textures taking time to load. Meddle with the Texture Bandwidth Multiplier and your frame lock. I would not suggest setting the TBM higher than 2-2.5x your frame lock. Read this blog on FSInsider for why

[quote]TEXTURE_BANDWITH_MULT

The mysterious sounding TEXTURE_BANDWITH_MULT is our first target.  This is a setting in the [DISPLAY] section of the file, formatted like this:

[DISPLAY]

TEXTURE_BANDWIDTH_MULT=n

Where n can range from 10 to some reasonable value that is related to your frame rate limit.

From Rafael Cintron, part of the FS Graphics and Terrain team, comes this description:

"The TEXTURE_BANDWIDTH_MULT option in the Display section is the target frame rate use for calculating texture bandwidth.  The higher you set this value the more textures we will allocate and copy per frame to the graphics card.  The lower you set this value, the less we will allocate and copy up to a minimum limit.  As an example, the default rate in the