>First one is San Diego-over Belmont park and mission bay.>The second is Michigan.>http://mywebpages.comcast.net/geofa/pages/rxp-pilot.jpgThose autogen trees are too tall, Geof! ;)

I think people feel the same way about you

They can hold off on YOUR copy, if you like...I want mine in October, 20 seconds after it hits the shelf. If it has some blurries, so be it. I'm sure I'll find plenty to enjoy!

Yeah-they must be fake plastic trees!http://mywebpages.comcast.net/geofa/pages/rxp-pilot.jpg

Let's see-$70 refund on real flying-about 15 minutes worth...I'd say Fs is quite the bargain!http://mywebpages.comcast.net/geofa/pages/rxp-pilot.jpg

Ouch. I'm hurt, really. :-xxrotflmao

Great! lets see if we can spot the difference between 'fluid' 8 FPS against 24 FPS. But hey if you're happy its okay...Just remeber I'm talking abou plain vanila FS-X thats without the add-ons that add the realy good content. But hey if your content.... Its al about individual choice. So enjoy!

THE OP gave us his views regarding blurring scenery in what he saw in the release version of FSX?, and in minutes it descends into off topic point scoring futility.I Know why I Lurk so much:(John

You are right-good natured bantering has no place here.... http://mywebpages.comcast.net/geofa/pages/rxp-pilot.jpg

Deary me, doesn't all this nonsense have a familiar ring to it?As for me, I have been paying attention, read the relevant blogs and have just applied my umteenth tweak to FS9 and, what do you know, textures now load much faster, the blurries have all but gone and it has taken only 3 years to achieve this state of near perfection!!!TEXTURE_BANDWIDTH_MULT=120TextureMaxLoad=10For crying out loud everybody, the fun has yet to begin :-jumpyMike

If I were a programmer on the FSX team tell ya what I would do.Add a couple mystery,do nothing lines in the .cfg file.Like, VISIONBLUR=10JAGGIE=5_100STUTTERRANGE=2435.77887Then sit back for the next 4 years and watch people try to figure em out and swear the difference changing each makes.Wait a minute, Think thats already been done in the fs9.cfg

>If I were a programmer on the FSX team tell ya what I would>do.>Add a couple mystery,do nothing lines in the .cfg file.>Like, VISIONBLUR=10>JAGGIE=5_100>STUTTERRANGE=2435.77887>Then sit back for the next 4 years and watch people try to>figure em out and swear the difference changing each makes.>Wait a minute, Think thats already been done in the fs9.cfgROFL!

>"So I'll never be happy with 12-15 fps in plain vanilla FS-X.>Sorry">>Why are you sorry? I don't care what you'd be happy with. Its a figure of speech. He is not apologizing to you.

Marten,Were you at the AvSim conference and are you reporting on your experience with the FSX setup running on the Matrox TripleHead2Go adapter? If so, I was the Microsoft guy standing there talking to you and yes, I was perplexed as to why things looked so blurry for you. After you left, I fiddled around a bit and figured out what the problem was. I looked all over the place for you to explain the cause, but unfortunately I couldn't find you. Anyway, for you and for those reading this thread, here is the story.Most of our setups at AvSim were using the ATI X1900, which is a very nice board. Lots of people wanted to see what FSX would do when running with the Matrox TripleHead2Go box, which allows the virtual cockpit to span three monitors (we had 1920x1200 widescreen LCD panels provided by Intel). Unfortunately, the ATI cards wouldn't output more than 600 horizontal lines when running through the Matrox box and FSX requires a minimum of 720 lines, so we switched to an NVIDIA 7900 card instead. That card allowed us to run at 3850x1024 spanned across all three monitors, which looked pretty sweet.After fiddling around, I determined that the display would go blurry only when running in 3 monitor mode with anti-aliasing turned on when there were a large number of high resolution scenery textures on the screen. (We were flying around the Las Vegas strip which has high-res textured models of most of the casinos.) As soon as I turned anti-aliasing off, the textures instantly became sharp again. Also, the textures were sharp when running in single monitor mode (1920x1200) with anti-aliasing on. Therefore, I believe the problem in this case was caused by an exhaustion of video memory. Why? I'm not exactly sure how NVIDIA implements anti-aliasing, but I'm pretty certain they do it by rendering to a very large off-screen buffer and downsampling to the screen resolution. For very high screen resolutions, the off-screen buffer could be quite humongous and use lots and lots of video memory. When that happens, there's not much video memory left for scenery, terrain, and aircraft textures (our NVIDIA cards had 256 megs of memory, I believe). When Flight Sim runs out of video memory, it reacts by dropping the highest resolution mipmaps on however many textures it takes to free up enough video memory to hold all the textures in the scene. When that happens, things can get really blurry in a hurry.The good news in all this is that the old cause of the blurries in FS9 really is better in FSX because the terrain engine was keeping up with loading textures. The bad news is that even though the terrain textures were fully loaded into system memory, if you crank up the screen resolution and turn up the settings (including anti-aliasing on NVIDIA cards) there wasn't enough room to fit them all in video memory and the result was still blurry textures. That bad news is tempered somewhat with the knowledge that all you have to do to fix it is throw more video memory at the problem. With 512 MB and even 1 GB video cards coming on the market now, that should be possible, albeit expensive.Cheers,Adam

>If I were a programmer on the FSX team tell ya what I would>do.>Add a couple mystery,do nothing lines in the .cfg file.>Like, VISIONBLUR=10>JAGGIE=5_100>STUTTERRANGE=2435.77887>Then sit back for the next 4 years and watch people try to>figure em out and swear the difference changing each makes.>Wait a minute, Think thats already been done in the fs9.cfgLOL that was the coolest post I've seen in a LOOONG TIME :)