Blurry textures! Argh

[Guest fiddlejo]

Please help me with this...I've been trying to get it right for about two weeks now, its starting to drive me nuts. Everyone seems to know it better than the other, claiming to know the right values.My terrain chapter of the fs9.cfg looks like this at the moment:[TERRAIN]TERRAIN_ERROR_FACTOR=100.000000TERRAIN_MIN_DEM_AREA=10.000000TERRAIN_MAX_DEM_AREA=100.000000TERRAIN_MAX_VERTEX_LEVEL=19TERRAIN_TEXTURE_SIZE_EXP=8TERRAIN_AUTOGEN_DENSITY=5TERRAIN_USE_GRADIENT_MAP=1TERRAIN_EXTENDED_TEXTURES=1TERRAIN_DEFAULT_RADIUS=4.000000TERRAIN_EXTENDED_RADIUS=4.000000TERRAIN_EXTENDED_LEVELS=4But I get blurry textures around me.What are the real values I have to set?Please help!

[Farlis 2,277]

Your config is perfectly fine.All blurries you still get are either due to a slow CPU, a fragmented HD or simply the limitations of the engine.

[altstiff 71]

Try either of these changes.....TERRAIN_DEFAULT_RADIUS=9.000000TERRAIN_EXTENDED_RADIUS=9.900000TERRAIN_EXTENDED_LEVELS=4TERRAIN_DEFAULT_RADIUS=9 TERRAIN_EXTENDED_RADIUS=9.5 TERRAIN_EXTENDED_LEVELS=5

[Farlis 2,277]

Forget it, those are rubbish. FS9 doesn't process values greater than 4 in these parameters.

[Guest fiddlejo]

>Forget it, those are rubbish. FS9 doesn't process values>greater than 4 in these parameters.Are you completely sure?

[Farlis 2,277]

>>Forget it, those are rubbish. FS9 doesn't process values>>greater than 4 in these parameters.>>Are you completely sure?Absolutely. There is a german introduction into the world of the FS Engine and it includes a thourough chapter on these values proving with replaced bitmaps in different colours for the various mipmaps levels that 4 is indeed the maximum value that is processed.

[Guest]

Yeah at this point there isn't much you can do for blurries if you otherwise maintain your system well. FS9 is just limited.

[Orlaam 306]

I wouldn't be so sure about the 4 numbers. I've seen several threads by those in development say the the first two can be set to 9.5 or maybe 10 and the bottom one set to 1 or 4. Like I have here: TERRAIN_DEFAULT_RADIUS=9.0000 TERRAIN_EXTENDED_RADIUS=9.0000TERRAIN_EXTENDED_LEVELS=4The last line defaults to 1, but with buffer mesh you can try 4. I can't say if 2 or 3 work.All I do know is that I've done a lot of tweaking with these lines and some others and found that they do make a difference when going above 4 in the radius settings. You could try 8.5 or even 4.5, but they do work above 4.TEXTURE_MAX_LOAD has also been one that seems to really effect blurries IMO. I've gone from tweaking it from 512 to 1024 and even other numbers and it seems to change the blurry problem. I don't know if people have no clue about these settings or if they work because they effect parameters outside the known function, but I've seen changes on three computers when only changing those lines in the FS9.cfg file.

[altstiff 71]

I am by no means an expert....BUTSteve Lacey suggested a set of those numbers to me. He was a developer for MSFS. Also suggested by many other people who seem to be in the know (such as the FAQ tips in this forum, Peter Wilding of GE fame and Vauchez of flight scenery fame)Steve Lacey also said the biggest factor in the blurries was capping your frame rate. Leaving it unlimited will cause blurries.....To each their own.....

[psolk 3,037]

"TEXTURE_MAX_LOAD has also been one that seems to really effect blurries IMO"TEXTURE_MAX_LOAD=512 vs 1024 just controls your global aircraft quality setting between Massive and the next one down... Adjust it and you should immediately notice the textures on your A/C are not nearly as clear at 512 vs 1024. It makes no difference in terms of number of textures loaded...Also, Extended_Levels actually default to different #'s on different machines. I just checked my backup of my vanilla FS and it was set to 232. The following link explains it all per Holger who I would trust my FS life too...http://portal.fsgenesis.net/index.php?name...d+terrain+level Cheers,-PaulPrimary Rig Liquid CooledIntel C2D E8500@3.8 /25CAsus P5N32SLI-Plus2 gigs Corsair XMS PC6400 4 4 4 12 @936Dual OC'd XFX 8800GTX @ 2 gigs24 inch Widescreen LCD 16XAA/16XAFDual 19 inch LCD'sRaid-0+1PCPower and Cooling 1k Quad SLIhttp://home.comcast.net/~psolk/3monitorsa.htmlBackup RigAMD 4000 San Diego @ 2.72 Gigs Kingston Corsair XMS CL2XFX 7900 GTX Raid-0

[Guest]

>I am by no means an expert....>>BUT>>Steve Lacey suggested a set of those numbers to me. He was a>developer for MSFS. Also suggested by many other people who>seem to be in the know (such as the FAQ tips in this forum,>Peter Wilding of GE fame and Vauchez of flight scenery fame)>>Steve Lacey also said the biggest factor in the blurries was>capping your frame rate. Leaving it unlimited will cause>blurries.....>>To each their own.....nonsense. i can cap it at 1fps or let it run at 80... blurries are there. fs just does not process the textures because of its internal priorities despite having plenty of spare system resources. blurries also tend to happen in major metropolitan areas vs somewhat rural areas. US roads and any of the megascenery products are blur ####. they are mostly unusable in some locations. also, FS has a problem with determining what you are looking at to load what textures in detail... if you pause the sim and look around you will see that to load the texture you were looking at before, you actually have to look at a different point.so the problem is 2 fold1. refresh speed on texture load, affected by overal load and geographical area (landclass)2. the way fs decides what you are looking at vs what you are really looking at. so you might be looking at blurries because fs doesnt know that you are looking there. it thinks you are looking over here! this is by far the MOST common issue.

[altstiff 71]

Agreed, "looking around" while flying causes blurries in abundance. And lets keep in mind we are pushing FS9 far more than it was intended to be pushed for sure.Add on this, add on that. Tack on a complicated PMDG and then AES, you get the idea. I don't think I have anything "stock" or Vanilla left now. And with that I almost always have soem sort of blurred ground at one point or another.Any who, here is the link to Steve's Blog and his post on the blurries. Keep in mind Steve is no slouch either (I thank you for the link to Holgers post), Steve was a key guy in the creation of Direct X too way back when.....http://www.steve-lacey.com/blogarchives/20..._blurries.shtml