Deadly-it has been validated-both ways.....If you read my above posts-I am one that had no blurries for 1 yr. 1/2-on rtm, sp1, and acceleration.Since changing my monitor a month ago-I am now one that has blurries-consistantly!Now-what the debate seems to be is:1) what causes them2) what can we do to get rid of them3) Placing blamere #1: I would submit-since the only thing I did was replace a hardware component, and that I had never had blurries till I did this-that it is a pretty good guess that the hardware is responsible.2) Still investigating this one as many others are.3) A waste of time imho...and the poster you took a jab at is one of the most respected simmers in the business. He has been around since the beginning, is a well known scenery designer, and a extremely helpful individual.What is your resume?http://mywebpages.comcast.net/geofa/pages/rxp-pilot.jpgForum Moderatorhttp://geofageofa.spaces.live.com/

>The op #4 post impled that Aces deceived simmers-along with>misinformation to substantiate that fact.>>Instead of our usual scolding -we treated this one with some>humor-admittedly a different tack from usual.>>I'd be glad to go back to just banning as we are supposed>to-if that is what you would like.>>Also if this place is so distasteful for you I'd suggest it is>the wrong place for you to be coming. Perhaps you should>follow your advice.>>http://mywebpages.comcast.net/geofa/pages/rxp-pilot.jpg>Forum Moderator>http://geofageofa.spaces.live.com/Nice... consider it followed. Goodbye all. I'm off to the other boards where human beings are treated with respect and mods act accordingly.

Sorry...I've deleted the picture mistakenly *:-* Here it is againhttp://img225.imageshack.us/img225/6204/65286254dy9.jpg

Goodbye!http://mywebpages.comcast.net/geofa/pages/rxp-pilot.jpgForum Moderatorhttp://geofageofa.spaces.live.com/

Phil has stated 100 times that FSX was designed for DX9.Neither the hardware required or DX10 itself existed when FSX started its dev cycle.Glenn

>Its ridiculous for any company to release a software and>expect the hardware company to release a patch to fix their>software. The software should at least work on the current>version.It is clear the mechanics involved are not fully understood.For the benefit of everyone reading this thread, let's describe it in general terms first, and then see how that relates to FSX specifically:1. No user software application "talks" to any hardware directly. Instead, they "talk" to an API (Application Program Interface) module (see: http://www.gordano.com/kb.htm?q=234 for more).2. In simple terms, think of an API as a "blackbox," with an input port and an output port. The API acts as an "abstraction layer" so that software authors need only concern themselves with coding for the pre-defined parameters of the API's "input port."The major advantage of using this scheme is that the application software can be totally hardware agnostic.3. The API's only function is to take the pre-defined "input" and translate it to a pre-defined "output" specification. As with the case of the application program, the API is agnostic. It doesn't "care" who's driver code it "talks to."4. All video hardware requires softare "driver code" that "translates" the data from the API's "output port" directly into the format required by the vendor's hardware.With regards to FSX specifically, the video output from FSX goes directly to the "imput port" of the DX9.x or DX10.x API as directed to by the "switch" in FSX's options dialog.The selected DX API then "translates" the input data stream into a properly formatted output stream and sends it to the "output port."The software driver for a specific video card then reads the data stream from the DX API's "output port" and converts it into hardware specific commands.In summary:FSX => DX API => Video Driver => Video Carda) ACES wrote FSX and is responsible for providing the correct data to the DX API.:( The DX API is written by Microsoft to specification standards developed via agreement with video hardware manufacturers.c) The Video Driver is written by a specific manufacturer for their video hardware. They and they alone are responsible for their video driver's correct operation.

Thanks Bill,that is what I tried to explain, but you are better with words :-).Jan

>re #1: I would submit-since the only thing I did was replace a>hardware component, and that I had never had blurries till I>did this-that it is a pretty good guess that the hardware is>responsible.I will reject your submission until I see an FSX box with a certain type of monitor listed in the hardware requirements. Obviously, your system met all requirements before changing monitors. It is the responsibility of the software maker to let customers know if their product will work on a customer's hardware. In this case, that's impossible because ACES themselves don't know the cause of this problem and say they weren't aware of it until AFTER release.It has been established that:1 - the majority of users with blurries state that they started with SP12 - SP1 contained changes in the way that textures are handled3 - users report elimination of blurries when reverting to RTM4 - blurries are reported on PCs from high-end to low-end5 - lack of blurries are reported on the same spectrum of PCsThat's as close to a smoking gun as we can get. But yes, there are still people that don't report blurries and remains to be explained.You are right that casting blame on the software/ACES is a waste of time. I submit that attempting to absolve the software/ACES is also a waste of time, and it is a bit maddening to read repeated posts putting the onus on hardware when that hardware doesn't have texture loading problems with RTM or any other sim/game.This forum has no polling capabilities that I can find but it seems to me that a wealth of information could be gathered for study by AVSIM offering the users a survey to complete. That might help pinpoint the problem.

>>re #1: I would submit-since the only thing I did was replace>a>>hardware component, and that I had never had blurries till I>>did this-that it is a pretty good guess that the hardware is>>responsible.>>I will reject your submission until I see an FSX box with a>certain type of monitor listed in the hardware requirements.How can you "reject" it? I mean, that's what happened for him. That's like me going to work today, and you saying, "no, you didn't.". I better stop now, I'm starting to sound like Plato. :)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

> Since changing my monitor a month ago-I am now one that has blurries-consistantly!That brings up one question: Does reverting back to the other monitor immediately solve your blurries issue?If so, could the higher screen resolution that you are running on your new monitor be causing the issue?These are probably things you've investigated aready.

LCD? Does replacing it with the old CRT just make it go away, at the same resolution?This could be 18-bit color with wonky FRC controls ala http://www.xbitlabs.com/articles/other/dis...d-guide_11.htmland http://www.tomshardware.com/2004/02/26/lcd_technicalities/http://www.tomshardware.com/2003/11/05/17/index.htmlI quote from Toms Hardware:"Based on this information, a lot of popular LCD monitors have actually only 18-bit LCD panels that use dithering etc to 'achieve' 24 bit"is this extra dithering causing the blurries?

When I a get a chance I will be trying my old monitors (I have a lcd and a standard). The one I went from was a 19 inch running at 1600x900-now I now a 24 inch running at 1900x1220. I have tried running the new monitor at lower resolutions-makes no difference.I'll also check into the dithering-interesting!Would using the digital connector vs. the analog make a difference?http://mywebpages.comcast.net/geofa/pages/rxp-pilot.jpgForum Moderatorhttp://geofageofa.spaces.live.com/

There is where the difference is-I not blaming or absolving-I am simply reporting....that...I used pre sp1-I used sp1 and I used acceration-with no blurries-none..I now have blurries-the only change is the monitor.I am interested in solving the problem though as I now face it-and I really don't want to go back to my 19" monitor. Phil has some interesting ideas to look into below-I'll be checking them.http://mywebpages.comcast.net/geofa/pages/rxp-pilot.jpgForum Moderatorhttp://geofageofa.spaces.live.com/

I don't think it is the higher resolution as running in lower resolutions I get the same results.When I get a chance-I will try the old monitor and see what happens-though Phil gives a couple interesting leads below.http://mywebpages.comcast.net/geofa/pages/rxp-pilot.jpgForum Moderatorhttp://geofageofa.spaces.live.com/

>>>re #1: I would submit-since the only thing I did was>replace>>a>>>hardware component, and that I had never had blurries till>I>>>did this-that it is a pretty good guess that the hardware>is>>>responsible.>>>>I will reject your submission until I see an FSX box with a>>certain type of monitor listed in the hardware requirements.>>How can you "reject" it? I mean, that's what happened for>him. >>That's like me going to work today, and you saying, "no, you>didn't.". >>I better stop now, I'm starting to sound like Plato. :)You don't sound anything like Plato. He was supposedly a very intelligent man and would have seen that Geofa made more than a simple statement like "I went to work today". He used the change of monitors and the acquisition of blurries to place the blame on hardware. It was a leap in logic and I have no doubt Plato would have seen it too. Logic was one of his strengths.BTW, blurries are not limited to LCD monitors. I use a CRT and I have them.http://img.photobucket.com/albums/v226/GOY...t/Blurries2.gif