How is everyone?I have a little problem and i was wondering if anyone had a solution to it.It seems that when i fly everything around me looks amazing but in the distance trees and buildings appear from a blurry landscape.I'm having a hard time adjusting this problem and i had to come to the pros.Any suggestions?Thanks

If you mean that trees and buildings appear suddenly out of nowhere - "popping" autogen is a known problem in FSX and unfortunately there's no workaround. The programmers were forced for technical reasons to disable the alpha fade feature in FS9 that allowed autogen objects to appear gradually in the distance, the way they would in real life.As to blurry landscapes - that's an issue with your FSX settings. I highly recommend you follow this guide - helped me get rid of blurries almost completely on a system that, while quite good, isn't quite the equal of yours.Hope this helps.

As to blurry landscapes - that's an issue with your FSX settings. I highly recommend you follow this guide - helped me get rid of blurries almost completely on a system that, while quite good, isn't quite the equal of yours.Hope this helps.

Yes to everything except that guide. Honestly, it's a little over the top at times (though good for beginners). Bojote's tweaker takes care of all of the important performance tweaks. The affinitymask tweak helps greatly with blurries, as well as an external framerate limiter and a defrag every few weeks (or months).From there, I've used a texture_bandwidth_mult of "80". So:TEXTURE_BANDWIDTH_MULT=80Also, higher Anistropic Filtering settings set through Catalyst (ATI/AMD) or Inspector (Nvidia) helps with distant blurriness and shimmers.

It may sound a little stupid, but zoom your viewpoint out... the default view is rather zoomed-in and does not make the distant terrain look its best.You will also notice less agn pop-in when your view is wider.If you don't mind tweaking a bit, you can also extend the LOD radius in the FSX cfg, which will push the terrain loading out further, and sharpen the terrain somewhat [not sure if it helps the autogen]... downsides are longer loading times, and a possible performance hit.

 

Yes to everything except that guide. Honestly, it's a little over the top at times (though good for beginners). Bojote's tweaker takes care of all of the important performance tweaks.

Unfortunately, for me, Bojote's tweaker was unusable, as were his "manual" tweaks. Totally wrecked FSX performance and at times made my system unstable to the point where I couldn't start FSX. Whereas the NickN guide (which I'd hardly call a beginner's guide, not when you're editing deep in Windows 7) got me excellent results.What's that line about "your mileage may vary"?

Unfortunately, for me, Bojote's tweaker was unusable, as were his "manual" tweaks. Totally wrecked FSX performance and at times made my system unstable to the point where I couldn't start FSX. Whereas the NickN guide (which I'd hardly call a beginner's guide, not when you're editing deep in Windows 7) got me excellent results.What's that line about "your mileage may vary"?

That's strange, but that's FSX and the spectrum of different systems for you. As for my beginner's statement, I retract it. Personally though, The Windows 7 tweaking stuff is a bit of an extreme measure for me. If I have to squeeze every iota out of my system, it's time for me to splurge on new hardware. Again, different people, different approaches.As for blurries, there are plenty of work-arounds.

Alright i will try all of your suggestions guys :Party:I will keep you posted

LOD_Radius=6.500000TEXTURE_BANDWIDTH_MULT=120These settings work for me no more poping autogen.Josh

LOD_Radius=6.600000TEXTURE_BANDWIDTH_MULT=120These settings work for me no more poping autogen.Josh

Popping autogen is something that is going to happen, no matter what. The only way to make this less apparent is to limit visibility or (as said above) use low zoom levels.As for your TEXTURE_BANDWIDTH_MULT=120 setting. I'm not sure where you picked up that tweak, but "whatever works". It's an extreme setting (like your LOD_radius setting) that can dent performance. Especially when using high autogen settings or add-ons like the NGX.

That's strange, but that's FSX and the spectrum of different systems for you.As for my beginner's statement, I retract it. Personally though, The Windows 7 tweaking stuff is a bit of an extreme measure for me. If I have to squeeze every iota out of my system, it's time for me to splurge on new hardware. Again, different people, different approaches.As for blurries, there are plenty of work-arounds.

I agree completely that tweaking Windows 7, per NickN, is way more than I'd really like to do. Frankly, I'm sympathetic to John Venema's advice - IIRC, he recommends doing without tweaks entirely. I'd love to be able to just load and go - maybe on my next build, when Ivy Bridge and Kepler hit. But so far, I get my best performance out of the NickN guide. I have no idea why.As far as the Bojote tweaks are concerned - you're absolutely right, there seems to be no pattern to what works and what doesn't. There are plenty of people I know and respect who swear by Bojote - I just couldn't get good results with his stuff. I seem to remember somebody suggesting that the Bojote tweaks work best on older systems, but I don't know if that's true or not either.I think what you've got to do is try everything (after backing up everything first, of course) and see what sticks and what doesn't.FSX... the adventure continues... :(

As long as the PC standard is open there will be problems. Too little standardization.

 

I agree completely that tweaking Windows 7, per NickN, is way more than I'd really like to do. Frankly, I'm sympathetic to John Venema's advice - IIRC, he recommends doing without tweaks entirely. I'd love to be able to just load and go - maybe on my next build, when Ivy Bridge and Kepler hit. But so far, I get my best performance out of the NickN guide. I have no idea why.As far as the Bojote tweaks are concerned - you're absolutely right, there seems to be no pattern to what works and what doesn't. There are plenty of people I know and respect who swear by Bojote - I just couldn't get good results with his stuff. I seem to remember somebody suggesting that the Bojote tweaks work best on older systems, but I don't know if that's true or not either.I think what you've got to do is try everything (after backing up everything first, of course) and see what sticks and what doesn't.FSX... the adventure continues... :(

Ah the good ole endless tweaking - perhaps someday we will have systems, to where all this tweaking will no longer be required - I plan on upgrading my build with Ivy Bridge as well, and like you I hope perhaps that will be the day - we will see.I also find my best results, by using NickN's guide for Nvidia Inspecter - that and just a handful of tweaks to the cfg, like the 0 bufferpools tweak which really helped on my system, reducing the number of cells for autogen, and the himem fix.I too would not go through the hassle of all those windows 7 tweaks...

Recently I accidentally did something that rocketed my frame rates through the roof. I'm not sure what, yet, but it started when I adjusted my TEXTURE_BANDWIDTH_MULT= (mentioned earlier) from default "40" to "80". As that tweak never helped with FPS before (but rather blurries), I'm having trouble believing that's the tweak to thank this time around... Autogen, water, and scenery are maxed. 8xS AA with 2xSGSS. I'm suddenly getting constant 30 FPS locked and don't know what to attribute it too.Considering how methodical I am with my tweaks and setting changes, this one has thrown me for a loop. I copied the current .cfg to a safe location...

Well of your suggestions worked a little but i'm still getting trees and buildings appearing in the distance.I guess it's just something i have to get used too.At least the blurries are gone and i'm getting 35FPS locked solid :(

LOD_Radius=6.500000TEXTURE_BANDWIDTH_MULT=120These settings work for me no more poping autogen.Josh

If you change any of the graphics sliders within the sim, you will need to shut down FSX, go back into the fsx.cfg, and manually reset your LOD_RADIUS back to 6.5000. It happens every single doggone time on my system and I don't know why.