>Okay you definitely have a tiling issue, with FSX making the>final pass only overtiles close to the aircraft.>>I assume you have not been panning while taking the screen>shots but leaving your view angle stable.>>Take the Water Effects down to Low 2.x. That still gives you>reflections but avoids another whole screen pass.>>What is your view distance - it should be limited to 60 miles>- the lowest setting.>>One problem FS has, will always have, is that it can be in>situations where it is trying to push more data through the>buss than the bandwidth can handle.>>Every computer is going to have a choke point which limits>performance, be it CPU or GPU or RAM or VideoRAM or Virtual>Memory or HD access speed or the Buss.>>The key to happiness is to find a setting which balances your>system so that everything can run near maximum.Yep agreed but you will always have a certain form of blur...Andr

>I have no blurries, neither before nor after SP1.>>My rig consists of:>>Intel DP965LT Lemont DDR2/1394 motherboard;>Intel Core2Duo E6600 2.40G 4MB processor;>Kingston 2x1GB CL4 DDR2 800 memory;>GeForce 8600GTS 256MB PCI-E graphics card;>Samsung Int. HD 500GB SATA-II hard disc;>FSP Epsilon 700 Watt Quiet power supply.>>I did do nothing to improve or eliminate the problem, because>I had no "blurries problem" to begin with. >>I guess I'm one of the lucky guys, at least when it comes to>flight simming (grin)! On the other hand: none of my GoFlight>stuff works with FSX... That's the story of my life: things>either work immediately, or they never work at all. >>Be well!>>Jaap Verduijn.Post a couple of pictures for us.

No blurries here either, you guys have your FPS locked yes/no?

Locked at 30.FPS doesn't appear to be a problem, but blurries is definitely a problem for me.Robin.

>[JOBSCEDULER]>AffinityMask=2>>//where>// n num of cores scheduled>//1 = 1 core 0001>//3 = 2 cores 0011>//7 = 3 cores 0111>//15= 4 cores 1111Dude, I could be mistaken, but I think AffinityMask=2 is similar to telling FSX you have a core 2, but not a core 1. I could imagine this could cause some weird sideeffects (2 = 0010)

He's saying that the intended implementation is that as you look further into the distance, the resolutions of the textures decrease. Therefore everyone is going to have "blurry" textures somewhere out there.But he seems to be intentionaly dodging the point that if everything well (as it seemed to work in RTM minus the poor fps), you don't actually notice the "blurries" because they are far enough away that you can't easily tell if they are blurry or not.

That's what I took him to mean as well. The problem is that such a definition renders the term meaningless. Using that definition, any game which uses a level of detail scheme and/or mipmapped textures meets the criteria for having the blurries. That is clearly not what is meant in these discussions and Andr

Count me into the "No Blurry" categoryMy system specs are belowGraphic Card Settings are 1280X1024X32 Res (Limited by my projector!)4X AA w/Temporal AA8X AF w/High Quality checkedMip Detail Level set to QualityVsync OnCurrently running in non crossfire modeI only have 2 issues graphically, One is the Popping of Autogen, which looks like a design issue, and the other is the scenery corruption when FSX default aircraft is used, which others have reported also. Non FSX default aircraft works fine!!This is what I see and my in game settings!http://forums.avsim.net/user_files/171904.jpghttp://forums.avsim.net/user_files/171905.jpghttp://forums.avsim.net/user_files/171906.jpghttp://forums.avsim.net/user_files/171907.jpghttp://forums.avsim.net/user_files/171908.jpghttp://forums.avsim.net/user_files/171909.jpg

No Blurries here-running unlimited.http://mywebpages.comcast.net/geofa/pages/rxp-pilot.jpg

No blurries here either.

I know the resolution will decrease into the distance but that's not the point...the point is that when I fly faste than 100kts, the scenery tiles cannot load fast enough....thus The Blurries...No matter if I'm locked or unlocked FPS...Also in my pics...see how close the next texture level is...very close at 170 kts.... not far away like others have shown

Come on Microsoft, there is no way you can shrug this problem off. This is so widespread that it's laughable. SP1 gave most of us a hefty performance increase, but what is that really worth if we can't enjoy it.:-(

Thank you for the screen shots (settings), just an FYI you can use Alt + PrtScn to capture just the currently "focused" window (i.e. doesn't include the entire desktop).I just purchased DeskKeeper Pro Premium to see if that helps with my Defrag -- after reading a KB article from Microsoft, it seems the defrag that comes with WinXP/Vista is a very "limited" version.Waiting for the defrag to finish...Robin.

I sympathize with your frustration. I'm still working like crazy to figure out what I can do (if anything) to resolve this problem.I'm puzzled that neither Phil nor those folks on the Beta list have not provide us with some more information on how we might be able to solve this. Surely at least one or two of the Beta folks ran into this problem??Robin.

Did you try the config settings I attached to post #14?