It doesn't work for me because of my mm set up. I wish I could find a way to quickly switch between mm and sm. I use my computer for other stuff and really need mm outside of FS. It is not that big of a deal in FS because I only use it for pop up panels, gps...

I don't have a mm setup and know nothing about it, but can't you use UltraMon for that...? As far as I can see you can set up profiles in which monitors are disabled... But maybe the ENB addon really needs the monitors unplugged...? I don't know, but you could give it a try: there is a full-featured trial version. But maybe you already gave it a try... :(

Just bought this after considering it for the entire weekend. Oh well, there are more weekends :)Hopefully this scenery will help me get back into flight simming. I was a huge fan of Megascenery PNW but feel that at this time, photo scenery has come as far as it will ever go. Increasing the resolution and fidelity won't fix the "flatness" inherent to these types of scenery. However none of the "data"-based scenery products for this area provided enough accuracy and detail to be comparable to photo scenery.First impressions are very good. Very nice work on the textures and landclass details. Roads and rivers were already very good with UTX. If you can't tell the difference between this scenery and UTX/FSGenesis or whatever, try finding a small town using Google Earth. Then see if you can find it with those products installed, then do the same with FTX installed. That was always the advantage of photo scenery - no missing towns. Knowing there should be a town there but only seeing forest really ruined the realism for me. But now they're there in full autogen glory. I might purchase one of the addon airports later, but it's nice that many airports are already improved slightly.Now for some things that could be better:-Very big FPS hit over major cities even relative to the improvement over e.g. UTX+GEX. They look better, but not enough to justify the framerate hit. Sure, you can turn autogen down, but this also affects rural areas which look very nice with autogen maxed and with excellent framerates. Also constantly going in and changing the settings depending on where my plane happens to be at the moment is too tedious.An option to install "low detail" or less dense city scenery while maintaining the high density of rural areas would have been nice. Either that or optimize the placement of autogen buildings more - that's more important than the actual density in my experience. For now, I'll tweak my system so as to get a minimum of 10-12 FPS around the most complex scenery areas, and avoid the biggest airports. That's what I normally do anyway. I've upgraded my CPU three times and the video card twice since I bought FSX in 2006, yet it still manages to bring my system to its knees :( -I would have preferred a more "square" coverage area instead of the long and narrow rectangle of scenery you get now. Many of my favorite places are east of boundary. If yo decide to expand the coverage area with future products, my vote would be to extend the scenery to the east rather than to the south or north.

-Very big FPS hit over major cities

Did you ever fly over KSFO with a stock FSX setup? It is a slideshow on my system. Other than that, PNW looks and runs perfect and usually does better than stock FSX in the FPS department IMOjja

The PNW documentation states that with all graphics enabled to the max, it will still be hard to get an "acceptable" performance level in FSX in certain scenery areas. The manual also states PNW was designed this way on purpose to accomodate the next generation of computers. That is the way it has always been with any new version of FS and "next generation" addons for it.PNW is a fantastic addon, no doubt. But to expect to be able to max everything out in a large urban area like Seattle and fly something like a PMDG 747 with My TrafficX or Ultimate Traffic X maxed at 100% AI is still pretty unreasonable, even on an overclocked i7 with the best available video card and RAM. The amount of autogen PNW can create in those situations is gonna cause problems.PNW is a bush pilot's dream scenery, and it works very, very well in slower aircraft. Toss in a fast and complex jet though, and you should expect to have to make some concessions.One way to REALLY enjoy everything PNW has to offer is to fly a helicopter using the scenery. You can get up close and personal with all the scenery and enjoy the eye candy to the max without forcing FSX to have to keep updating autogen all the time. Pick an area in PNW, let FSX load all the autogen and everything else, then sight-see the local area in a chopper. All the autogen for your LOD Radius area will already be loaded, and you can fly from building to building, cruise down a river to find a bridge, etc to your heart's content. I like Bush Flying too, but for me PNW has raised the bar on helicopter flying by a magnitude. It's a fantastic way to "discover" all the stuff there is in PNW one local area at a time.

Well my take on this scenery since I bought it is as a single addon it is everything everyone says it is. It does suffer though with the same problem Mega Scenery has. That is to complete the North America (Or even just the US and Canada) series based on the size of the area covered and the required disk resources, will take at least double and probably more, the number of volumes that of the Australia project. That makes it cost prohibitive not only the dollars spent, but the system resources (Disk space) that would be required to complete the continent. It does have performance issues in cities, as mentioned, but not to bad on my system. There are some problems with some of the airports like KSEA, KPDX, mostly with Navaids. Looks though Orbx is on top of it, and hopefully soon there will be a fix.The biggest problem I see now is the with the FTX Central utility, that is suppose to revert back to the previous scenery (default, UT/GEX etc...), should you choose to. While it does disable itself, it does not however disable the Airport elevation files which are installed in the scenery/world/scenery folder. This causes significant elevation problems if you revert to your original scenery, unless you remove (or move) them.

Hi guys,we have new FTX Central code being tested right now which resolves the persistent elevation issues when switching to 'Default'. That was our boob-boo, sorry about that. We have also fixed the AI landing short and navdata issues at the airports, so a patch is not too far away for those and other minor reported issues.We also have an SP1 in the works for later in the year, which fixes all the customer issues reported, adds stuff that did not make RTM, and also improves performance where possible.Good point about the "less city autogen" option, I'll have a think about that.For me though, switching autogen density mid-flight literally takes seconds, since I invoke the options dialog using ALT O-E-D then flick the slider back a notch. Takes me literally 4 seconds.Good feedback though - thank you!

There is a utility program for FS8/9 that would automatically raise or lower the autogen slider based on average framerates. It's a pity no one has figured out how to write a similar app for FSX yet... ;)

PNW is a fantastic addon, no doubt. But to expect to be able to max everything out in a large urban area like Seattle and fly something like a PMDG 747 with My TrafficX or Ultimate Traffic X maxed at 100% AI is still pretty unreasonable, even on an overclocked i7 with the best available video card and RAM. The amount of autogen PNW can create in those situations is gonna cause problems.

That I understand perfectly. However like I said, around rural areas and mountains, and even fairly large cities, my system manages extremely smooth framerates. So 95% of the time, I can fly with autogen maxed (I keep a few other settings like AI traffic turned down). It's a little frustrating having to turn down settings just to get acceptable performance for the remaining <5% of my flying time. My solution for now will have to be to just live with the low framerates over those areas and avoid landing at e.g. SeaTac. As long as I just cross those areas and don't try to land there, framerate doesn't really matter anyway.This is really more a criticism of how FSX works than how this particular scenery product does things. Settings that work for small, rural GA fields will not work for big airports. You either have to find a compromise that provides acceptable performance over big cities, at the expense of ridiculously high framerates and lower detail over rural areas, or manually change the settings depending on where you fly. However it's made worse because at high settings, the framerate difference between rural areas and cities is greater with this scenery than default or other addons I've used.

Good point about the "less city autogen" option, I'll have a think about that.

As long as it will be an option I don't mind that less city autogen, but I am a Extremely dense autogen nut, so please do not take that away from me! :( :( I set up my system and tuned it all in such a way that I can fly low and slow with Extremely dense autogen. Right now I can fly above the bush and Darrington and Twin Oaks with Extremely dense autogen and smooth performance (and fps between 23 to my max 25). (I usually fly the Carenado C182RG and since I bought Darrington I use the Bell 206 more and more). I can even fly above Seattle with Extremely dense autogen with an fps of 19 (lowest average): it's not the smoothest experience, but it certainly works. And all that on a i7 920 @ 3.3 (stock cooler) and a GTX285, which isn't a top system...! Of course this means I had to make compromises... It's all about choices. Some people might not like what I have (no AI for instance, sometimes textures load late and I don't use 8xS FSAA for instance but ingame FSAA), but to me Extremely dense autogen is worth it. Luckily I am a low and slow flyer: that helps. :( But I do have water at High 2x and clouds density at maximum, so it's not a matter of dragging all options ot the left: in fact, I think I have ALL options quite high to completely right, apart from AI. I even use the ENB addon! And it still runs great! And it looks even better! (I posted various screenshots over here, and I think they look quite okay...!)By making the right choices and tweaking the system, you can get more out of PNW that even the PNW manual itself says. B)

There is a utility program for FS8/9 that would automatically raise or lower the autogen slider based on average framerates. It's a pity no one has figured out how to write a similar app for FSX yet... ;)

I'd like to see a gauge that would let you change autogen 'on the fly'. And not in the usual steps, but a 'gapless' slider. That would be nice. B)

Simply a hotkey combination to manually toggle between two preset "autogen profiles" would be enough for me :(

Simply a hotkey combination to manually toggle between two preset "autogen profiles" would be enough for me :(

Now that is a brilliant idea! :(

Does anyone know when the DEMO will be out?

Simply a hotkey combination to manually toggle between two preset "autogen profiles" would be enough for me :(

Should be simplw enough to incorporate...something like the Ultimate Traffic X hotkey combos that can increase or decrease the amount of AI traffic "on the fly". But in FSX, don't forget this will still cause the autogen to have to be "reloaded" and you will get FSX pausing while it goes to reload all the scenery again (with the associated "white window and black progress bar" thingie).Also, because it will be reloading the Scenery Settings, any setting you have that exceeds a "maximum" slider setting in FSX will get reset to it's maximum default setting. Like if you had Texture_Max_Load =4096 for high definition clouds, it's gonna get reset to 1024. Same with LOD_Radius...anything higher than 4.5 is gonna get reset to that again.

Hi skunker,

Does anyone know when the DEMO will be out?

The demo installer went into final testing yesterday. It should be ready for release in a few days.Cheers, Holger

Well, I bit the bullet and bought PNW. So far so good, I am generally impressed and so far, haven't seen a noticeable hit on my system. A few small problems however - I did the default install and made no changes other than 5m mesh. I run GEX, UTX and FSG. I noticed in one airport in western Washington that the runway was elevated above the ground. Another was non existent - I selectdd a parking spot and oaded and was nicely nestler in a clearing surrounded by trees with no runway in sight.So far most of the airports and scenery have been just fine and look fantastic.Vic