I had the same exact symptoms and I believe changing to FIBER_FRAME_TIME_FRACTION=0.33 made all the difference for me. It's in the [MAIN] section. Mine got set reall low for some reason like 0.05. Hey it's an easy change and worth a shot. Good Luck.Steve

Just for the heck of it, I just took a quick spin around EHAM in the PMDG 747 and took a few snaps for you to compare to yours. All of mine were taken while I was moving and not paused. I was doing 200kts while I took these. Click on them to expand and compare to yours, but I reduced them a little to conform the Avsim rules on photo attachment.The good news is that it's not your HD since your on a solid state and I haven't run a defrag since installing this, so its probably not a HD issue. Perhaps it's a hardware issue or something with the video card or its settings. Just to make sure are your Global texture resolution turned all the way up and Texture Resolution set to 60cm or better? In the shots I posted I am using the default radius of 4.5 so much more than that probably isn't really needed imho.

Thanks, that's definately closer to the result I'm after. texture res is at 7cm, mesh at 10m. I thought the FIBER_FRAME_TIME_FRACTION= mod was only relevent in FS9?Am tearing my hair out here cuz I know people with similar rigs who are getting excellent results and I'm still fiddling about with mine. Grrrr Cheers for help anyway :)

Thanks, that's definately closer to the result I'm after. texture res is at 7cm, mesh at 10m. I thought the FIBER_FRAME_TIME_FRACTION= mod was only relevent in FS9?Am tearing my hair out here cuz I know people with similar rigs who are getting excellent results and I'm still fiddling about with mine. Grrrr Cheers for help anyway :)

Increasing that value may help you, since it will allow FSX to spend more time rendering the terrain, but it may also cause stutters.Have you got your rig configured to shutdown as much as possible before starting FSX. With only two cores you need all the CPU cycles you can get. Tools like game booster or Alacrity PC can do this very well. Turn off as much junk as you can.Have you checked if core parking is enabled in Win 7. If you have done some windows updates, some of your performance counters will have been turned back on and you will need to turn them off again using the Windows resource kit utility.

Thanks, that's definately closer to the result I'm after. texture res is at 7cm, mesh at 10m.

What about your Global texture resolution slider on the first page of the FSX settings menu? Is it turned all the way to the right?

I thought the FIBER_FRAME_TIME_FRACTION= mod was only relevent in FS9?Am tearing my hair out here cuz I know people with similar rigs who are getting excellent results and I'm still fiddling about with mine. Grrrr Cheers for help anyway :)

My FIBER_FRAME_TIME_FRACTION is set at .33 which I believe is the default setting. In fact, even if you erase it from the fsx.cfg it will still remain internally in FSX as set to .33.Yeah, your rig is not the problem as you can see from my pics, somewhere along the way something either got set wrong or not set at all, but its not because you have a dual core.

What about the 4Gb of RAM you have?DDR2?

What about the 4Gb of RAM you have?DDR2?

I doubt it's that either since I run 2GB of DDR2 and have no issue, so I would imagine his 4GB are fine.

If you're running frames unlimited or with the external limiter, try switching to limiting frames within FSX. While it's been documented that there's some dead-weight loss of FPS by limiting them within FSX (so to speak), this was the only way I solved a similar blurries problem. The problem seems to be that FSX, when running unlimited, throws any extra cycles at increasing the rendering speed and none (or virtually none) at loading terrain. Even when I would pause it would take AGES for the terrain to catch up. Now it loads faster on the fly (when running locked) than it did paused (running unlimited).

Yeah I've tried running both unlimited and locked (progressively lower frame locks too). It definately improves when the system is under less load (weather off etc), and I'm pretty sure it's my cpu holding me back and have done everything I know to reduce load (excluding fsx directories from antivirus, disabling antivirus, closing all progs and unnescessary processes, etc). What was this about performance counters? I must have missed something here if they make a significant difference to performance?EDIT: will give the FIBER_FRAME_TIME_FRACTION a bit of a play to see how I get on tonight

Just my 2 cents worth, on my quad core I got much better results by setting the affinity mask to 14. This allowed FSX to use core 0 (even though it is turned "off") to run the scheduler and core 1 to do the rest. I saw a real improvement with the blurries by doing this. Of course, this info and tweak comes from Bojote, not me.

Just my 2 cents worth, on my quad core I got much better results by setting the affinity mask to 14. This allowed FSX to use core 0 (even though it is turned "off") to run the scheduler and core 1 to do the rest. I saw a real improvement with the blurries by doing this. Of course, this info and tweak comes from Bojote, not me.

He is running a dual core processor, not a quad {!)

Just as a test, turn water down to lowest and set vis to 10nm. Improvement?

I was having issues with the the ground textures not keeping up also on my Q6600, especially after adding FTX PNW scenery. I was still having problems with just normal autogen and using 1X high water. Good framerate but bad blurries. I found they improved when I stopped using the FPS limiter and limited frames to 35 within FSX. What finally really helped for me were these lines in my FSX config file: [Display]TextureMaxLoad=1TEXTURE_BANDWIDTH_MULT=35I had been running TextureMaxLoad between 9 and 30 previously, thinking that higher numbers would reduce blurries. One day I tried to use numbers below 9 and noticed a substantial improvement. Using TextureMaxLoad=1 has almost elimated the blurries for me now. I do not understand why this works so don't ask me to explain, but it most definitely has worked on my rig.Regards MartinQ6600GO @3.2GHZGigabyte P35-DS3R4GB PC8500 Gskill Ram 5-5-5-12 @ 1065mhz 8800GT 512mb GRAPHICS CARDWD 320GB SATA DRIVECorsair 520Watt Modular Power SupplyVista 32 Home Premium SP1FSX, UTX, GEX, FEX, FTX, ASA, LDS763, CS757, Realair SF260, Lotussim L39, DA Piper Cheyenne, etc.

What was this about performance counters? I must have missed something here if they make a significant difference to performance?

Quote from Nicks' guide on Win 7, but it applies to XP and Vista too http://www.simforums...D=198187#198187:

DISABLE ALL PERFORMANCE COUNTERS BUT LEAVE SUPPORT FOR OS AND PROCDownload this package from Microsoft: http://www.microsoft.com/downloads/details.aspx?FamilyID=7ff99683-b7ec-4da6-92ab...Run the installer: exctrlst_setup.exe Once installed you will have no shortcut to the tool, simply browse to: C:\Program Files\Resource Kit Double click the file: exctrlst.exe A box will appear. Make sure there is a bullet in "SERVICE"There is a list of services showing in the lower pane of the box, simply click the top service in that list to HIGHLIGHT IT and CLEAR the check OUT OF THE BOX labeled: "Performance Counters Enabled"Scroll down the list and repeat the highlight\uncheck until EVERY SERVICE in that list displays a cleared "check", verify you got them all -but the two- I list below... then close the box NOTE: MAKE SURE TO LEAVE A CHECK IN THE FOLLOWING ITEMSPERFPROCPERFOS

Upgrading from a dual core to a quad fixed the blurries for me - none of the other numerous tweaks suggested on this and other forums worked.Bruceb