Can you list the changes that you made? I am not familiar with the perfbucket.________________________________________________________________________________________________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

I'm going to see if your findings are also reflected in default scenery.I'm always a bit wary of increasing variables significantly beyond their default values..Some tweaks will have you increase variables to 10x their size or more, which seems a bit odd given that the default values are probably what the devs optimized for.However, if your theory about PerfBucket is correct, then it might make sense to try a much higher value.I've also found that the fiber framerate tweak doesn't have as big an effect as pre-SP1, either on framerates or texture loading speed, even on my single core system.

> which seems a bit odd given that the default values are probably what the devs optimized forFor sure I haven't found the optimal value yet. I tried something new based on speculation and it had a huge impact (yet keeping the sim playable for me) and now it's up to the community to figure out if this approach can be generalized or if more moderate adjustments already have the desired effect.

My previous post in this thread has all the details. Easiest to find when viewing the thread in linear mode.

That's strange.. as a developer given the task of optimizing the terrain engine, it makes sense that the first thing you'd try would be to get the most out of the current code, ie. trying different fsx.cfg variables, before taking the engine apart.Increasing the Perfbucket to 10x its size (50) seems to have made textures load faster, but also increased stutters somewhat. Fiber framerate fraction also increases texture load speed at the expense of performance. So, what to do now? Decrease fiber fraction and keep the bucket setting, vice versa, or change both? Clearly this is about finding the balance between these two for each unique system...

>Hi simmers. I'm still getting blurries with SP1 when I fly>at low altitude even though my target FPS stays constant and>at the maximum value of 15 FPS. Since my FPS isn't going down>and is staying constant, I'm guessing I may have resources to>spare to reduce the blurries.>>Any suggestions on how I can reduce the blurries? Thanks.>>GadwinHey Gadwin,It would be interesting to know how much RAM you are using? Even more specifically how fast the RAM is? SP1 is said to have addressed CPU usage. It begs to reason that if your cpu is cycling faster than your RAM can handle that you would not see any gains in texture loading regardless of SP1. I could be wrong. This is just an educated guess on my part.Chris,

>Blurries and Neon green boxes.>>The reason the FSX results in blurries (and also neon green>textuers)>is because the SP1 patch has extended the old FS9 way of doing>>texture meshes to use dual-core, and beyond - to many core.>-SNIP->Enjoy the simulation - I wish I had the horse power some>people>quote here, this is just cutting edge software so it is>difficult to get the best. SP1 made it easier for computers>to reach that >wow factor,>but you may have to get under the hood to really get the>perfect>solution for yourself.>>Regards>TomAfter reading your explanation, Tom, it would seem that SP1"fixes" things for those fortunate enough to have a multi-coreCPU but absolutely PORKS things for those of use with single coreCPU's.I guess I'll just have to back out to FSX pre-SP1 and wait untilthis fall when I plan to build a new system... :( Paul

I'm getting texture blurries too with SP1, with 2-6 FPS average increase over RTM, with occasional bursts to 30-40 FPS. My system is quite modest (see specs below) so I'm happy with any improvement, however I never had blurries before except with TileProxy when server didn't timely provide the tiles. If I pause the flight now, in 10-15 seconds the textures get crisp but would get blurry soon again. Hope the solution will be found soon.Cheers,=S.V.=eMachines T5026/P4 3.07GHz/1Gb RAM/160Gb SATA/Windows XP Home SP2/ATI RADEON 9250 256Mb (PCI)/ViewSonic VX910 19' (1280x1024)/Microsoft SideWinder Force Feedback 2

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. While a single-core system cannot physically use these threading enhancements, multicore support is just one part of the overall SP1 picture. MANY MANY other optimizations have been performed which apply to ALL computer types, especially those relating to DirectX draw calls and other items.Yes, multicore computers are enhanced, but they are without question not the exclusive benefactors of the SP1 experience. 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. Regards,-Greg

Well, I've been experimenting with various settings/combinations since SP1 was available and there does not appear to be a golden bullet. (or we have not found it yet!) Apologies if I've missed the bleeding obvious, but did this not get picked up in Beta? Surely someone testing had this problem which was not solved easily so perhaps they can comment? I think we will soon get to the bottom of this given the change that has happened in code clearly since SP1 and the fact this does not appear isolated to any one hardware config - i.e. it's a common issue - and a major one.For my opinion, I am reasonably happy with the SP1 improvements but if the blurries remain I think we have taken a backwards step. I think it would be ideal timing for Aces to acknowledge we have a problem here and give the community some comfort in the knowledge that they are looking into this issue (apologies if i've missed a post). In the mean time - you never know - we might crack it!

Same here horrendous blurries. it starts of fine but in a few minutes it becomes completely blurred. This is a clear case of texture not loading and to me at default installation, ideas about poolbuffer, scheduler etc look more like snake oil. Sorry but thats what i feel. 4 or more beta passes and look what we have got!! It happens on my single core machine more than my dual core one.

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.

Same blurries problem for me too after installing SP1.Tried out all the suggested tweaks, even limited the target framerate and/or texture quality sliders to min.So the good news of SP1 (fps increase appr. 50% on my system) for me is more then "compensated" by this new blurry problem.Texture details just won't fully load, even not in SpotView with the aircraft at airspeed 0 for a minute or so and no autogen. :-(. RobSystem: AMD4000+ (single core), 2Gbyte mem, nivia 7900GT (256Mb)

I'm having the same issue with blurries also. I tried Phil Taylors suggestion of: [TERRAIN]SWAP_WAIT_TIMEOUT=The default is 30 frames.This entry was not in my FSX.CFG so I added it and set the value to 25. I have FSX locked to 30 fps. What values should be used to help with blurries?Processor: Intel X6800 @ 3.6GhzRAM: Patriot PC8000 2GBVideo: nVidia 8800GTX (158.22 drives for WinXP Pro)Audio: Creative Labs xFi Pro EliteHard drive: 2 WD Raptor 74GB 10K rpm SATABase FSX install with SP1, no add-ons. Run at 1920 x 1200. Changing graphics settings in FSX doesn't seem to help with the blurries. Changing nVidia driver settings doesn't seem to help either.Any suggestions on how I can remove the blurries?FPS have increased, but image quality has decreased. The detail texture radius appears to have shrunk also.Thank you.Robin

Hi Phil,I have not touched the Fiber_frame_time setting but have set the JOBSCHEDULER - Affinity = 3 (Intel X6800 CPU). The blurries are pretty bad beyond a very small radius of my view point. Switching views is smooth, but I can watch the detail texture change happen over about 5 second period -- but ultimately leaves a very tiny detail texture radius around my view point.Clean install, defrag -- see my earlier post. 1920 x 1200. nVidia 8800GTX 158.22 drivers (dated May 17th 2007).Any suggestions?Thanks, Robin.