For all who are experiencing blurries, if all the other suggestions dont produce results - its possible your configuration is giving you a timing dependent thread collision issue and not a configuration/driver issue.It does look like quite a few of these issues are being resolved thru drivers and other things, but that a small percentage are not being resolved by anything.So lets try something. To try to isolate the problem, you can try this:use the [JOBSCHEDULER] tweak to reduce your core usage step-wise downwards to see if reducing the total number of threads scheduled has an impact.if you have 4 cores, try using only 3, and then only 2, and then just 1 by setting AffinityMask appropriately based on my blog post. if you have 2 cores, try using only 1.it would also be interesting to hear if this is more prevalent on 4 cores. if, for instance, 2 core machines are getting resolved via the other suggestions but 4 core machines are not - then trying this stepwise reduction is further good data.report your results on this thread and we will gather the data.

Any tips for single core users? Anywhere outside of autogen generation is blurred?

If you have blurries with a single core, this cannot be the thread problem I am referencing.In that case I suggest the other config related suggestions ( drivers, DX, etc ) or turning down your settings.

Would hyper-threading help any? I do not have it enabled.....

No, this suggestion is for multi-core machines only.We do not schedule threads on HT, because those are not real cores and the lock contention is way worse.You can certainly try to lock things to a single core, in the slim chance we are detecting a class of HT CPUs wrong.

Phil,Thanks for working to try to gather data on this, but while I have seen some dual core users reporting the problem, it seems like the prevalence of reports on this board at least seem to be single-core (and perhaps AMD specifically? ...or maybe simply most of the posters with single core machines have AMD). Anyway, what I was trying to ask on your blog is do you have any theories for new causes for blurries on single core machines? (akin to thread collision for dual core)? Obviously, it sounds like "no", but it seems odd that a number of us single-corer's seem to have more of an issue with blurries than we did with RTM with the same settings (I know a number of us single core AMDers tried with autogen completely off, etc... scenarios where tiles loaded great with RTM). Also a curiosity, it seem like at least a couple of us single core AMDers seemed to record an FPS jump way above what we were told to expect (I received >100% increase and Solar measure 95% in at least one test). That made me curious if the tile loading was perhaps not using as much CPU as it was supposed to in some cases?I'm *not* asking for tech support here, I've adjusted my settings to the point where tiles are loading more that satisfactorily and I still have decent FPS... I'm quite happy with SP1 overall. This is just a curosity for insight from your end. I'm still holding out a small hope that you'll say "Oh actually, SP1 does XXX where RTM doesn't, so maybe that causes a problem on some machines... try doing XXX and see if that helps". ...but then again, if you knew of such a thing, I'm sure you'd have already done so...Anyway, thanks for keeping an ear open to our issues...

This discussion is for multicore only. Period. no other.We did see higher gains on some configs, but I was being conservative with my statements to talk to what we expected across all configs except the really, really old and mouldy configs.

Phil,I have the best result never had before with this below, I just installed new driver and these are so far the best I could ever imagine, ultra smoothForceWare 158.27 XP WHQL fsx.cfgTEXTURE_BANDWIDTH_MULT=400FIBER_FRAME_TIME_FRACTION=0.50{BufferPools}PoolSize=5000000{JOBSCHEDULER}AffinityMask=3Dual Core 2 2.4GHZ 2 gig ram Gforce 7600 512 MBThanksChris Willishttp://www.hifisim.comhttp://www.hifisim.com/banners/hifi-dev-sigbanner.jpg

On a dual core, AffinityMask=3 means you are using both cores.So the threading is not causing blurries, the driver update or the other config settings fixed you up.

I had actually tried do this, but it appeared that FSX still used both cores. I even removed the entry completely and it still used both cores.I even let FSX rebuild the config.I will try it all again and report back!

Here I just deleted fsx.cfg and let it rebuild. This is cpu usage:I tried with affinity=1 and it appeared to use only 1 cpu.It does appear that perhaps my cpu is maxed out and there is just not enough time to load the final detail so I don't get the blurries. When I load up a flight initially and fly around the area, the textures are clear, but as I fly away I can see textures clearing up, but they never get too clear.

In the FSX.cfg, can I just put{JOBSCHEDULER}AffinityMask=3anywhere? Or does it matter?

Box 1: Intel E6300 OC'd to 2.45 ghz, 2 gig RAM, nvidia 7600 GT, Gigabyte Intel 945 chipset, 230 watt PSULooking at your above spec, it looks like your chipset doesn't match your CPU, according to INTEL? The 945 chipsets are for Pentium D's, The C2D's use variations of the 946,963, 965 and 975x chipsets! See below!http://compare.intel.com/pcc/showchart.asp...1&culture=en-US

>Any tips for single core users? Anywhere outside of autogen>generation is blurred?I reduced my blurries actually by increasing the level of detail radius to large.Buffer Pool is at 1750000texture bandwidth is at 40 to reduce tree flicker.autogen is normal but set to 2500 per cell in the cfg filemesh complexity is set to 52. there is a giant difference between 52 and 53 on this box.I managed to pull an average 18-20 FPS on this old box of course in super dense areas it drops but still my big iron approaches and landings work smooth.AMD Athalon 2400XP+ 2GHZ2GB PC2100NVidia 7600GS 512MB AGPdaveo ESSB

>use the [JOBSCHEDULER] tweak to reduce your core usage>step-wise downwards to see if reducing the total number of>threads scheduled has an impact.>Thanks for bringing it up, as I wrote I have better results with affinity set to =2 (vs.3) value on my Core2 Extreme 6800 system.Dirk.