Having read through the SP1 Technical thread, and having just done an install of SP1 myself and can see what users are complaining about: blurries and popping scenery textures. In my case, loading a default aircraft on any airport runway, results in very greyed out / green textures in both VC and scenery which then takes some 30 seconds to loading the initial textures.Surely this could not have been the case when the SP1 was Beta tested. Is there something wrong with the SP1 release build, or any new / specific FSX.cfg settings, over and above those already blogged, that could correct these problems.Come on Phil / the ACES team, give us all some feedback on the mega threads. I know Phil has made some comments, but we don't seem to be getting very far.My own system is not very high spec (2.6 ATHLON CPU, 2 GigRAM, 7600GS 256 dram graphics), but pre-SP1 with the various tweaks etc. was actually running better than after the patch.Regards,Stuart

Seems like aces robbed peter to pay paul. Now while frame rate paul is happy, texture peter is the new moron in town! I have already gone mad with the various settings and advices for the cfg file, wonder how ACES team cope up with this day in day out!!

First set your TextureBandwidthMult to something like 200. If you start to see stutters, reduce a little. It's system dependent so you have to play with it til you get a setting to your liking. Next since your system is a single core, make sure FSX is not scheduling threads, force this by setting your affinitymask to 1. in the JOBSCHEDULER section of the fsx.cfg (See Phil's blog)

Stuart,I share your pain but I really don't think it's a problem with FSX or SP1. It could be your OS configurations, your computer system, or perhaps your video card settings coupled with your FSX.cfg settings causing your problem. I have some blurries myself but I know it is caused by the fact I must keep the level of detail radius setting at "Medium" in my FSX.cfg. Setting it higher will surely cause an out of memory (OOM) crash (I only have 4 gigs of RAM; maybe I need more?). The little time I had with the level of detail radius setting at "High" gave me a chance to see excellent textures (crisp and clear) and little or no blurries in my very high-end system (the Dell XPS710H2C which was recently certified by Microsoft for FSX). I don't think there's a magic bullet that will totally eliminate blurries (blurries also exist in many other computer games). Maybe when the video card makers get their acts together this will change as I think the technology is clearly here. Unfortunately your system, by your own admission, is not the latest tech and you will not be able to get the maximum benefits of FSX until you upgrade. However, I have read many other threads on AVSIM and other FS sites of flight simmers having very nice graphics and system performance with systems lower than yours. Since you stated FSX performed better prior to installing SP1, you might consider uninstalling the patch but I think the overall benefits of keeping SP1 outweighs this decision. I have two 8800 GTX video cards in SLI configuration and use the video card and FSX.cfg settings recommended by NVIDIA techs and receive good graphics 98% of the time (http://www.nzone.com/object/nzone_fsx_techtips.html). They even have recommended settings for your 7600! I also have no suggested "tweaks" installed that I have seen in Aces blogs or on AVSIM as I worry they could only make matters worse. I would just like to get rid of the OOM crashes so I can enjoy FSX even more. Hope you can find a fix for your problems soon and apologize in advance for any remarks I made which may have offended you. I'm just offering my comments and suggestions in hopes you can once again be a satisfied flight simmer.Best regards,Jim

>I don't think there's a magic bullet that will>totally eliminate blurries (blurries also exist in many other>computer games).Really? Can you name a few? :(Marco

Yeah...we need some good explanation of these parameters. Understanding them would help us to fine tune this.Blurries and Stutters are my major issues now. Blurries I was able to control to some extent. But stutters have gone so high when I flying low, that its almost unflyable.Manny

C'mon! processor affinity, job scheduler, boombang, radius, LOD, threads and what have you! Am I the last guinea pig standing for ACES? Surely with so many of us complaining of the exact same blurry issue all of us can't be wrong! My single CPU gets it, so does the dual core high end one-only difference the higher end one gets it later! That gives me the view that most of us will get it if we fly long enough continously.Never heard of a patch which creats more problems than it solves and that too discovered within hours of release!

>Seems like aces robbed peter to pay paul. Oh man I could not help but laugh at that. I certainly could not have said it better.I just hope Paul shares a bit of his earnings with Peter. ;)

>>Seems like aces robbed peter to pay paul. >>Oh man I could not help but laugh at that. I certainly could>not have said it better.>>I just hope Paul shares a bit of his earnings with Peter. ;)For us single core guys Peter and Paul interact with a setting called FIBER_FRAME_FRACTION and it's in the FSX.CFG. ;)RhettAMD 3700+ (@2585 mhz), eVGA 7800GT 256 (Guru3D 93.71), ASUS A8N-E, PC Power 510 SLI, 2gb Corsair XMS 3-3-3-8 (1T), WD 150 gig 10000rpm Raptor, WD 250gig 7200rpm SATA2, Seagate 120gb 5400 rpm external HD, CoolerMaster Praetorian

OK.. What Phil had in his blog. The first two entries are everything.1. [JOBSCHEDULER]AffinityMask=nI have it set at 2 for a Dual core system.2. [TERRAIN]SWAP_WAIT_TIMEOUT=Guys..don't mess around with LOD and stuff. Leave it as is. 4.5 is the maximum. Do not increase it any more. It used to error our before. now it doesnt and I am glad it doesn't and I am glad its there...for the future when we have a supercomputer. ;). Increasing the LOD would bring down your sim to its knees. I tried changing it to 8 and oh boy..I ended up with single digit FPS flying at Juliana on my 3.4GHz Core 2 Duo E6600.Set SWAP_WAIT_TIMEOUT=120 or something. That should help with the blurries.. Try increasing it or reducing it to suit your system.Another thing I noticed. Out of the 2 cores graphis on the Windiws Task manager(for two core system) set it such that the 2nd core (the right hand graphcis) is not quite at 100%. Because if that reaches 100%... it eats up from the Core 1 and that causes the dips in the core 1 and stutters. The left side needs to be a straight line..and the right side needs to be ..kind of wavy lines. Does that make sense?I would think for a Quad quore, the same thing should applies..for the last three cores not reach 100%. So the total utilization should be slightly less than 100%. Manny

>Another thing I noticed. Out of the 2 cores graphis on the>Windiws Task manager(for two core system) set it such that the>2nd core (the right hand graphcis) is not quite at 100%.>Because if that reaches 100%... it eats up from the Core 1 and>that causes the dips in the core 1 and stutters. The left side>needs to be a straight line..and the right side needs to be>..kind of wavy lines. Does that make sense?>>I would think for a Quad quore, the same thing should>applies..for the last three cores not reach 100%. So the total>utilization should be slightly less than 100%. >>MannyHow do you control that???

>Another thing I noticed. Out of the 2 cores graphis on the>Windiws Task manager(for two core system) set it such that the>2nd core (the right hand graphcis) is not quite at 100%.>Because if that reaches 100%... it eats up from the Core 1 and>that causes the dips in the core 1 and stutters. The left side>needs to be a straight line..and the right side needs to be>..kind of wavy lines. Does that make sense?Like Manny, I think this DOES make sense. Like Tom, though, I don't know how to control it.

These two control that.1.AffinityMask=nI have it set at 2 for a Dual core system.2.SWAP_WAIT_TIMEOUT=The number of frames and the AffinityMask.IF you have Core 2 Duo use AffinityMask=0001SWAP_WAIT_TIMEOUT=120 (or less)Play with these two.Manny

>These two control that.>>1.>AffinityMask=n>>I have it set at 2 for a Dual core system.Manny, that is incorrect. The n should never be even... This is a "mask bit" and represents a four digit binary sequence:Single Core with or without HT AffinityMask=1 (binary 0001)CoreDuo or AMD Dual Core AffinityMask=3 (binary 0011)Quad Core AffinityMask=15 (binary 1111)Your setting of AffinityMask=2 is meaningless (binary 0010)

>>These two control that.>>>>1.>>AffinityMask=n>>>>I have it set at 2 for a Dual core system.>>Manny, that is incorrect. The n should never be even... This>is a "mask bit" and represents a four digit binary sequence:>>Single Core with or without HT AffinityMask=1 (binary 0001)>>CoreDuo or AMD Dual Core AffinityMask=3 (binary 0011)>>Quad Core AffinityMask=15 (binary 1111)>>Your setting of AffinityMask=2 is meaningless (binary 0010)I wouldn't say setting AffinityMask to 2 is meaningless, it just means FSX will use core 2, Setting 1 will use core 1 only. There's a table someone posted in another thread that indicates which cores are being used for both single, dual, and quad core systems. I don't think though these settings will control how much of the cores will be used at any one time. For instance I use a setting of 3 for my dual core, and I've seen 100% usage on both cores at times.