>>>The fact that FSX runs on many user's machines without unacceptable blurries indicates that it is not the FSX code at fault because we all run the same code. Ergo the blurries issue must be in the individual hardware/setup combinations.I would agree with this observation, except to point out that it is possible to push FSX to the point where any individual PC cannot handle the load. This point is different for each machine and each setup.All sliders to the right, and most machines will be unable to cope.So the question, in some cases, is: Do I buy a faster machine, or do I fine-tune FSX so that I get as much out of my machine as possible. If the latter: First comes fine-tuning the machine itself (balanced components, no stuff running in the background, defrags etc), but then comes finding the "sweet spot" where FSX can keep up with what is demanded of it and provide adequate framerates so that it is smooth.. That is the purpose of sharing information, I think, in a thread like this one..

>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".I see your point, however if you don't have problems, its probably not fair for you to judge how people that are seeing the problem should be dealing with it. I agree that its likely that many of us that seem to face a regression in tile loading are still better off overall (that's certainly the case for me and I said exactly that a couple posts back), yet you can certainly understand how it would be annoying to face a regression in an area of FSX where there wasn't before? And you could certainly understand our desire to undo this "regression"?

Bert,Thanks for your suggestions. I wasn't convinced I was seeing any improvement with TEXTURE_BANDWIDTH_MULT being > 40, but maybe I'll give it another try.

I wasn't judging anybody, merely providing the advice that the problems being experienced may not be within the confines of the FSX config file itself.As for your comment that I am not in a position to judge because I don't have the problem is similar to saying to a Doctor "I don't want you to treat my heart attack because you haven't had one". But, as I said I wasn't judging merely trying to help those with the problem to try other avenues of investigation. As a person with a 30 year IT career behind them, several of those years spent as a Mainframe Performance Analyst and knowing, through bitter experience, that performance choke points are often the least expected place to find them, I thought I might have something to offer. Apparently not. John

>I wasn't judging anybody, merely providing the advice that>the problems being experienced may not be within the confines>of the FSX config file itself.>>As for your comment that I am not in a position to judge>because I don't have the problem is similar to saying to a>Doctor "I don't want you to treat my heart attack because you>haven't had one". But, as I said I wasn't judging merely>trying to help those with the problem to try other avenues of>investigation. >>As a person with a 30 year IT career behind them, several of>those years spent as a Mainframe Performance Analyst and>knowing, through bitter experience, that performance choke>points are often the least expected place to find them, I>thought I might have something to offer. Apparently not. >>JohnI was refering to the comment I quoted in your last post that made it sound as if we should just pipe down and enjoy what's working and not worry about fixing what's not.Also, your analogy-- first I'm not sure what qualifies you as "my doctor", and second its more like the doctor saying "You are letting the pain of your ulcer prevent you from enjoy life. Stop thinking about the pain and enjoy life".Anyway, not to get in a "who's is longer" debate, but I'm a c++ programmer with 7.5 years experience-- while I don't have 30 years experience and I haven't done any programming related to graphics since college, I think my field may be even more relevant than yours.Thanks for the parts of the post that were intended to be helpful, I'm just saying don't belittle us because we feel we have a problem relating to SP1.And again, let me point out that overall I am happy with SP1 and I fully realize that the blurries issue is very likely an issue of hardware or configuration, not a "bug" (though I admit I have pondered the possibility that it is a bug in a couple of posts).

Horrible blurries in FSX before and after installing SP1 were cured on my Core 2 E4300 Radeon 9800 128mb machine by changing AGP aperture size to 256mb as suggested above. Thanks, /Mats. Give 256mb a try. If that doesn't eliminate the blurries try setting double your video card memory as AGP aperture in the bios.At last,Smilinpete

I don't why I bother to respond but read post #80, this is an example of what I was meant about users taking their head out of the FSX box for a moment and looking at their machine setup. It's true I'm a has been, C++ wasn't around when I was cracking code it was all FACT, ARGUS & FORTRAN and there was no tertiary education courses connected with EDP (now IT) but then its not me with the blurries. For the last time myopic one I wasn't trying to belittle anybody I was genuinely trying to help nor did I ever suggest that I was your doctor, I think that your imagination is getting the better of you. I never meant to suggest

Arg... I can't read. I totally misread that first paragraph and thought you were saying something you weren't. I can't understand how I interpreted it the way I did either except that I guess i just read too fast and let my mind fill in details that weren't there. Sorry.* hangs head in shame *

Accepted mauihawk, put it down to language and the impetuosity of youth.This is a little humour so don't get it wrong again:I'm a has been, you're a wannabee.The difference is I've been there.;-):-beerchug John

"(...) I probably have a different cultural background to you and speak English English (...)"It's happening oftener and oftener, mucher and mucher, frequenter and frequenter: Merkins being unable/unwilling to understand anything but their own dialect. Not only that: there's also the mindless software that fairly often doesn't even allow the posting of English English words, on account of them not being Merkin and hence "bad".One tends to wonder: Tom is really an internationally experienced guy who probably has trod the soil of many more countries than I ever did (and I sure trod the soil of SOME!), yet when it comes to words on this forum only Merkin is "good" and all other English is "bad". Remarkable. In order not to challenge the right of any webmaster to set his own rules: if you want to pursue the matter further, please do it at http://www.2lazy2fail.com (then hit "forum").Be well!Jaap Verduijn.

Let's not make this something its not. I don't see a single word in the paragraph I misread that would have been written differently by a "Merkin". I'm sorry for misreading, but this seems deliberatly and needlessly inflammatory.

> Tiles seem to load better while I'm in the cockpit? Can this>be true? In my second embarrasment of the night, I solved this problem: I was flying with my cockpit zoom at 50% but the external view at 100%. Small wonder the blurries are less obvious when they are shrunk to half their size....so I suppose one very "cheap" yet effective workaround to the issue is to simply decrease zoom :D

Well, we don't seem to be getting very far with this blurries issue. I have tried all the fixes posted in the forum none work. The only fix for me is revert back to RTM and that cures blurries immediately. So it's not a machine issue it's a SP1 issue.May people say they are not getting blurries but I don't belive many of these poeople have photo scenery loaded for a quarter of a country! So I believe you, but, if you installed the same photo scenery you would get blurries.I have tried on a friend's rig and we have the same issue. No it is not a bug with the scenery that works well with RTM!!!Rgds,JCMK

Had same problem, tried a dozen solutions none that worked for me. Until I made a fresh install of FSX and SP1 *after* manually deleting leftover folders and files represented in the Microsoft GamesFSX-folder. Also deleted the profiles and save-files in Documents And SettingsuserFSX... That did the trick! Why? My guess is that after tweaking my original FSX with different "autogen and texture" resizing methods trying to earn some more fps prior to SP1; the tools and additional manipulated files were leftovers in my FSX-folder even after the uninstall procedure. These may have corrupted the effort of SP1.So if you're giving up and havent tried this, give it a chance :-)regardsScandi426Oslo, Norway

Useful thread, many interesting observations. I try to keep my zoom at 0.80 - 0.85, going below affects FPS in my case. Can't say I'm struggling with the blurries, but ocasionally get that green sheen of an airport when turning my head (TrackIR) in the direction of an airport, like KSEA.