Bilinear and Anistrophic are mutually exclusive, you either use one or the other, not both.But I think knowing how FSX does relate to the ATI or nVidia Control might be good for us all, since nobody is posting any specifics about their graphics driver version nor what setting they are using via the Control panel.I've been using nVidia 8800 driver 158.22 (5/17) and using the Global setting of "3D application controls" which is what the FSX Programs setting in the nVidia Control panel is using also.But I had blurries before and after SP1.I would be interested to see what resolution you folks are using and how much graphics card memory you have. I'm at 1920 x 1200 with 768MB video memory. I certainly have enough video memory to run a page frame with detailed textures so I'm not exactly sure what is going on.I have turned OFF a lot of setting also (Auto Gen = OFF) Water = 1.x Med.My weekend is open this week so I'll put together a comprehensive list of settings and how they have and have not affected FSX -- with screen shots.Robin.

In case the data is helpful, I too am experiencing a significant increase of blurred ground textures since installing SP1.Pre-SP1, textures were crisp almost as far as I could see out of the virtual cockpit, and all around when in spot view. Textures were only blurred that were so far away it felt realistic - like the kind of blurring one would experience due to atmospheric factors in the real world. Of course, if I switched from a GA prop to a jet, the increased ground speed would cause some blurring, but that was easily resolved by either turning down some sliders to decrease the load on the CPU or pausing for a few seconds to let them build back up again.After SP1 (a full uninstall of all add-ons and FSX itself, deleting all associated folders per Phil's recommendations, etc. and then reinstalling FSX RTM, applying SP1, and several defrags before and after), ground textures are only crisp directly under the plane and what seems to be a radius of about a few miles or less. Then they get increasingly blurry. When I fly towards the blurred textures, they eventually load and look crisp, but the previously crisp textures behind me get quite blurry, in the same radius. I can leave it paused indefinitely and the further textures simply won't load. Turning down all the sliders (AI, water, lighting, etc) to maximize frame rates has no impact on the small radius of crisp textures. Interestingly, changing the "level of detail radius" slider seems to have absolutely no impact on the actual radius of detailed textures. Ditto for checking "land detail textures". In fact, even when I change the fsx.cfg entry for detail radius from 4.50000 to 5.50000 or 6.50000 (guessing on the number of zeros, can't remember), it seems to have no impact on the blurry textures. When I go to 7.5000, I eventually get an "out of memory" error, but alas no increase in crisp textures.I've tried moving the slider that controls texture resolution from 7cm to 2m, etc. but still it doesn't change the radius of crisp textures.It sure feels like something isn't working right since the SP1 installation. Like going back to FS9 with regards to ground textures, and oh so frustrating since I was so thrilled with the texture improvements in FSX and love flying with the new Megascenery Hawaii and Phoenix add-ons (only Hawaii is currently installed until I can sort this out). Of course, my frame rates did show a 20 or 30 percent increase, and other fixes from SP1 sure are welcome. But I'm hopeful they didn't come at the cost of clear textures. In fact, looking at the screenshots that the install program for FSX displays during the install look super-sharp as far as the eye can see, and only made me want that experience even more. Is anyone able to duplicate those kind of screenshots any more after SP1?My System:Processor: Intel 6600 (dual core) - default speedsRAM: Corsair 2GB Video: nVidia 8800GTX (158.24 drivers for Vista)Audio: Creative Labs xFi Extreme MusicHard drive: 150GB 10K rpm SATAPlus a couple of gigs of SD readyboost memoryThanks, Phil, and fellow AVSIM simmers for any help you can provide.Jesse

>Is anyone able to duplicate those kind of screenshots any more>after SP1?>Certainly not me. The LOD radius after SP1 is GREATLY reduced and it was one of the very first things I noticed after spending more time with the sim. I was flabbergasted at the performance increase that I saw after installing SP1 and the first thought in my head is "how in the heck did they do that?" Now it appears we know how they did it; at the expense of texture resolution and LOD radius. Let's hope there is an easy fix for it or else my time in this sim will be extremely minimized. I flew in the megascenery hawaii lastnight and while things still look good up close, the mountains a few miles away were blursville. :(________________________________________________________________________________________________Intel D975XBX2 'Bad Axe 2' | Intel Core 2 Duo E6600 @ 3.20Ghz | 2 GB Super Talent DDR2 800 | Big Typhoon VX | eVGA 8800GTS @ 565/900 | Seagate 2x320GB SATA RAID-0 | OCZ GameXStream 700W | Creative X-Fi | Silverstone TJ-09BW | Matrox Triplehead Setup

>Those tweaks are not snake oil. They have a documented effect>on various aspects of the terrain engine. Phil Taylor (senior>product manager for graphics and terrain) even describes many>of them in his webblog.Regardless, we should not have to tweak to make it work as it should. Perfectly sharp textures should be a given, not a luxury.For me anyway, the textures simply do not load, even if I spend two minutes hovering over the same spot. I have yet to spend more than two minutes, so perhaps after three minutes they laod?

>Regardless, we should not have to tweak to make it work as it>should. Perfectly sharp textures should be a given, not a>luxury.This statement would make sense if every computer was identical. It ain't. I could also say "wealth should be given, not a luxury" - equally nonsensical.Michael J.http://img142.imageshack.us/img142/9320/apollo17vf7.jpg

>>>Regardless, we should not have to tweak to make it work as>it>>should. Perfectly sharp textures should be a given, not a>>luxury.>>This statement would make sense if every computer was>identical. It ain't. I could also say "wealth should be given,>not a luxury" - equally nonsensical.I have never seen a game that does not load the texture resolution you specify, this includes Pre-SP1 FSX. Pre-SP1 has tack sharp textures at all times. No so with SP1. What you see below is with the same settings flying in a fixed direction over the same scenery area: Pre SP1 textures:http://sio.midco.net/111lll/fsx%202007-01-...05-56-25-68.jpgPost SP1 textures:http://sio.midco.net/FTP5/blurry.jpg

I've had success reducing the heavy blurries by increasing the AGP aperture size to 256mb for my 128mb 9800 ati card. At lower I even got display corruption. It seems the Aces team opened up some new throttle because I never found much difference with that setting before.Maybe SP1 requires more video memory...Of course, this is obviously only for those with ancient AGP machines;)/Mats

Can you provide some specific settings for which we can adjust and see the results?So far the info I've read about is:PerfBucket (increase 10X) = 70FIBER_FRAME_TIME_FRACTION (increase)AffinityMask = 3 (dual core)SWAP_WAIT_TIMEOUT=120TEXTURE_BANDWIDTH_MULT=360TextureMaxLoad=10Keep water effect Low 2.x or lower.AutoGen OFFAnything else?Thanks, Robin.

With SP1 it looks like it runs out of video memory and then blurs everything, even the VC textures. After that it never really catches up again. When increasing the AGP aperture size in bios that problem disappeared. I still have blurries when moving fast (slewing) but it soon catches up again just as in pre-SP1. I call this heavy blurries as it might be a different problem than the "usual" blurries.I also think it's a good idea to check the hardware, overclocking, cooling and so on now with SP1 as it seem to pressure the hardware even more./Mats

OK here we go for an example with SP1 blurries and photo real terrain. To get the second screen I had to pause the sim and wait for 1 minute... The 737 was flying at 200 KTS. I never had similar issues with RTM.http://forums.avsim.net/user_files/171937.jpghttp://forums.avsim.net/user_files/171938.jpg

>Not necessairily - the system auto-detects if you have>multiple cores or processors. If you do, it will utilize them.>If NOT, it will not split up the threads and remain>monolithic, more like FS9 and FSX RTM. >I would modify that response to "the system SHOULD auto-detect" and "If NOT, it SHOULD NOT split up"....-SNIP->If you are a single-core user with blurry textures, there is>something else at play. It isn't the lack of multicore that is>causing the issue. My response to..."If you are a single-core user with blurry textures, there is something else at play."...it's called SP1! Paul >>Regards,>-Greg>

Same problem here. I was flying around LA and for 10 min's and everything was fine but as I started my approach into LA the textures turned blurry and didn't reload for a good 1-2 mins.

I'm officially done with blurries... not that I still don't think there is something about SP1 that is making my machine more prone to them than with RTM, but I've now got SP1 running such that the textures are loading I think about as fast as with RTM. And though I have sacrificed FPS to get there, the bottom line is I am still running with significantly better settings than with RTM with FPS that doesn't drop as low as it did with RTM.I've tried everything posted here on the issue. Almost none of it seemed to make a difference except the obvious fps locker and FIBER_FRAME_TIME_FRACTION. Despite my attempts to avoid FIBER_FRAME in favor of the fps locker per ACES's advice, I still felt like I was seeing more obvious benefit from boosting FIBER_FRAME.A couple other things I've think I've noticed:* Tiles load much slower near downtowns of cities. This may seem obvious, but I realized much of my memories of how RTM terrain looked were based on rural flying while I had been doing most of my SP1 testing in urban areas (since those are what caused me fps horror in RTM). Therefore, I think at least some of my problem was "invented" due to an unfair comparison.* Tiles seem to load better while I'm in the cockpit? Can this be true? While working with this issue over the past several days, I have been doing much of my examination from exterior views. Though even with my tweaked settings I will still see some blurries I don't think should be there with the exterior views, I seem to have a really hard time finding them once I get back in the cockpit. I don't *think* this is just because a lot of my view is blocked, but who knows...My final settings:Large detail radiusTEXTURE_BANDWIDTH_MULT=40UPPER_FRAMERATE_LIMIT=20PerfBucket=7 (default)SWAP_WAIT_TIMEOUT=30 (default)FIBER_FRAME_TIME_FRACTION=0.5PoolSize=5000000Anti-virus disabledApril 2007 Dx9c update installedMipBias not set (too much shimmering)VSync offAA forced on via gpu settings (16x)ansio filtering set (16x via gpu settings)System:A64 2.2GHz2 Gigs8800 GTS(...and I'm hoping the dual-core cpu I get to open for my b-day next month means I can drop that FIBER_FRAME at least back to .33, maybe bump the fps a bit, and put this issue completely out of my mind)

Just to add my observation... I also found the actual radius of detailed textures to be so small that I could only really see detail textures directly below my aircraft (in spot view) and hardly at all in front of the aircraft (in cockpit view). By trial and error, I found the LOD_RADIUS does matter, but when set to "medium" (3.5) it was really small, and when set to "large" (4.5) the computer could not keep up and I would soon outfly the detail. It would come back if I hit the pause key and waited a minute or so.When flying over a rural area, this was not that obvious, but nearing a major city, things would quickly turn blurry.Here is what helped, in my case.First of all, keep the FPS lock low enough to give the computer a chance to keep up with texture refresh. Once it falls behind, you may as well hit Pause, because it cannot find the cycles to recover.Secondly, I found that Texture_Bandwidth_Mult does matter. The default is 40, and in my case, going to 200 helped a lot. I've seen recommendations for 400, but, again, in my case that was too extreme, so experiment a bit.Thirdly, the LOD_RADIUS can be adjusted, and does make a difference.. in my case, 3.5 was too small, 4.5 too big.. so I've settled on 4.0.Is this perfect, no, but most of the time I have a very believable view out front, and the scenery engine keeps up.Lastly, try flying a slower aircraft, if the scenery cannot keep up..The Piper Cub is a good test platform, as well as a hoot to fly !P4-2.8, single core, 1 GB memory, 256 MB video.

This is a positive thread for those suffering the blurries. However, many may be overly focussing on FSX minutia. Users with the blurries would do well to get out of the FSX box for a moment and have a look at their general machine setup. I am reminded of the old saying: "Can't see the wood for the trees".SP1 has enabled FSX to use more of the PCs computing power than before. This increases the load on the motherboard memory, graphics and disk sub systems. I do not get the blurries as shown by the Jpegs here and I have done no tweaking in FSX SP1 other than to set the affinity mask which wasn't necessary anyway. FSX is above all else about shifting bytes around your system like cars on a road network. Any constraints to free moving traffic are likely to grid lock the entire network. I cannot tell you why I and many others don't get the blurries but I do observe common sense PC setup practices such as defragging often. Keeping the operating system, Page file and FSX on different disk spindles (not just different partitions). Stopping unnecessary OS and ancillary processes whilst FSX is running. Balancing the graphics subsystem memory and CPU (it