Hi,I decided to post here until I get my new login at the ORBX forum. I am the owner of PNW and Darrington but thinking about Cushman Meadows. Due to my taste in scenery complexity I have chosen to not use PNW at this time as it cripples my system. What I would like to know is if it is possible to install a few of the addon airports offered by ORBX but not have PNW active, is this possible?Any help would be much appreciated,RegardsBob

In theory, you should be able to drop some folders or files from this directory. ORBX\FTX_NANow I can't tell you if it works since e. g. some elevation data is set up in the scenery\world\scenery folder too and should be used with the corresponding airport files only to build up that nice picture.But before starting a big trial&error run on all those files, you should look for some settings which fit to your system. First step is to be current on all PNW patches since the later ones enhanced the autogen performance for example. That planned partial approach of yours will eat up time and may not lead to a satisfying outcome in the sim. PNW (with all files enabled) on low details will always be better than any self-build stuff and also avoids unknown problems.

Hi,Nice approach thank you. I am aware of the elevation data as I experienced this exact issue when uninstalling PNW, as a number airports where now sitting -50ft AGL. This is a little bit of a disappointment as many folks myself included of course, may be interested in those smaller airports and not the whole banana. I would think that this would have crossed their minds to find a solid approach to allowing folks to purchase the smaller airports without the need of the PNW purchase. It is possible I guess that they designed themselves into a corner or maybe it is a marketing approach but one will never know. I just wish there was a way to get this done.Bob

In theory, you should be able to drop some folders or files from this directory. ORBX\FTX_NANow I can't tell you if it works since e. g. some elevation data is set up in the scenery\world\scenery folder too and should be used with the corresponding airport files only to build up that nice picture.But before starting a big trial&error run on all those files, you should look for some settings which fit to your system. First step is to be current on all PNW patches since the later ones enhanced the autogen performance for example. That planned partial approach of yours will eat up time and may not lead to a satisfying outcome in the sim. PNW (with all files enabled) on low details will always be better than any self-build stuff and also avoids unknown problems.

I must admit that this is the first complaint about the PNW package I see so far. Those smaller airfields are a part of the package and without the rest, they will lose nearly all attraction in my eyes.The only framerate hog in the big PNW area may be the one around Seattle (speaking of the airport) while the rest gives you light system load, nice textures and dense autogen trees for example.Orbx never released some airfields only, but I guess that this is because nobody would buy them but will go for the complete thing. Since the price for those hundreds of reworked fields in that nice surrounding isn't that high, the "airport only" may not even have a financial attraction.But these are just my viewpoints of course. I don't see this sentence happening.

This is a little bit of a disappointment as many folks myself included of course, may be interested in those smaller airports and not the whole banana.

PNW currently is down from 41 AUD to 23. That's close to stealing. ^_^As said, maybe you can try to find some settings which allow you to run the thing. The autogen will surely have the biggest influence there and they give you some rough templates to follow in the manual.Their forums also offer some tips&tricks section where devs and customers explain some more helpful things, so you should come to a nice solution if not running on a very, very old PC. If so, FSX alone might be the bigger problem then.

I decided to post here until I get my new login at the ORBX forum.

How long could this take? Can't remember any complicated procedure over there, but they may have changed something in the meantime of course.

CoolIP,Yep I love the Seattle area so much as I lived there for 12 years. You are correct about the surrounding airports and the splendor of it all. I love everything ORBX has put out. I also own the AU offerings and fly often. I am more interested in the individual packages right now as they offer me a little more stability and smoothness then flying into the Seattle area. I will see what happens here and get back. It did find the 003 and 3a patches to the base PNW package and maybe spend some time again on adjustments and see if I can live with them. I have an OK PC. QX9650 Oc'd to 3.8 but with 3:2 ratio bit O could not get the bus speed I had hoped for. So basically it is not the most effecient OC even though the clock speed would indicate so. I am waiting for the CPU's to come down before I buy my next one. I bought the 9650 when it first came out and I will not do that anymore. Thanks for your input, I really appreciated your thoughts.RegardsBob

I must admit that this is the first complaint about the PNW package I see so far. Those smaller airfields are a part of the package and without the rest, they will lose nearly all attraction in my eyes.The only framerate hog in the big PNW area may be the one around Seattle (speaking of the airport) while the rest gives you light system load, nice textures and dense autogen trees for example.Orbx never released some airfields only, but I guess that this is because nobody would buy them but will go for the complete thing. Since the price for those hundreds of reworked fields in that nice surrounding isn't that high, the "airport only" may not even have a financial attraction.But these are just my viewpoints of course.As said, maybe you can try to find some settings which allow you to run the thing. The autogen will surely have the biggest influence there and they give you some rough templates to follow in the manual.Their forums also offer some tips&tricks section where devs and customers explain some more helpful things, so you should come to a nice solution if not running on a very, very old PC. If so, FSX alone might be the bigger problem then.

No problem.I think that quite some guys around (or over at Orbx') run that CPU too (which still is a good one), so they may help you with some settings. KSEA are is dense indeed, but it should work with reducing details.The rest of PNW should already work like a charm with that thing, so maybe it just needs some closer look on the actual settings then.I could only name very few "hogs" in the known Orbx program, one might be the KSEA area and another one may be Brisbane. Those two are mentioned in quite some threads, so your stressing of the actual hardware needs around KSEA surely is reasonable.

Cushman has some problems if you're not using the PNW package, as it was designed to sit atop those custom files. If you're not going to purchase the whole PNW, you could at least download the free demo. It covers the Olympic Peninsula, including the area around Cushman, and I've heard from at least one user that the two seem to work well together. I have to say though, hearing it "cripples your system" surprises me. There's definitely more detail in the PNW than the default scenery, but outside of the major urban areas I haven't heard anyone complain about performance. In fact, at Cushman many of the beta testers found they could crank their autogen setting much higher than usual because the area is so underpopulated. Apparently, the AGN trees don't cause nearly the frame rate hit that the urban objects do. My advice is to try the demo and see if that works for you. If it does, then get Cushman.

Hi,No, I do own PNW. I can run it but not at the detail level at which it makes me smile if you know what I mean. When you combine in traffic, a semi-complex aircraft and the scenery density levels that I am comfortable with, I really cannot live with the issues at those levels. This is why I wanted to install only the smaller airport offerings as I can operate in those areas at the slider levels I like to see. It really comes down to having a better system. If this does not work then I will need to wait until the processor prices etc come down. Then I can try again.Bob

Cushman has some problems if you're not using the PNW package, as it was designed to sit atop those custom files. If you're not going to purchase the whole PNW, you could at least download the free demo. It covers the Olympic Peninsula, including the area around Cushman, and I've heard from at least one user that the two seem to work well together. I have to say though, hearing it "cripples your system" surprises me. There's definitely more detail in the PNW than the default scenery, but outside of the major urban areas I haven't heard anyone complain about performance. In fact, at Cushman many of the beta testers found they could crank their autogen setting much higher than usual because the area is so underpopulated. Apparently, the AGN trees don't cause nearly the frame rate hit that the urban objects do. My advice is to try the demo and see if that works for you. If it does, then get Cushman.

Hi,No, I do own PNW. I can run it but not at the detail level at which it makes me smile if you know what I mean. When you combine in traffic, a semi-complex aircraft and the scenery density levels that I am comfortable with, I really cannot live with the issues at those levels. This is why I wanted to install only the smaller airport offerings as I can operate in those areas at the slider levels I like to see. It really comes down to having a better system. If this does not work then I will need to wait until the processor prices etc come down. Then I can try again.Bob

PNW is a strange beast for me. I can run it with good FPS all around even with complex a/c and lots of AI, but the only issue I have with the area is that I struggle to keep the ground tiles in focus when flying planes like the PMDG's and LDS 767. Low and slow a/c are no problem, but anything complex at faster, ie anything greater that 150 kts gives me some blurries. PNW is kind of a write off product for me since I normally fly heavies.When KPDK comes out I will most likely be trying to find a way to install it outside of the ORBX folder so that I can run it as a seperate airport without having to have the PNW turned on. This way I can still enjoy that airport when flying heavies but not be burduned with the blurry ground textures PNW gives me.

I get excellent performance with the PNW scenery except for the areas around cities. There are tweaks you can do to reduce the autogen in cities without it affecting rural areas. Personally I just live with the lower framerates over cities. Only time I pass the bigger cities is when I'm on the way from rural airport to another :)From the Cushman Meadows manual:WHAT WILL YOU MISS OUT ON IF YOU DON'T HAVE ORBX FTX INSTALLED?- Blending of the airport photoreal into the surrounding terrain with exactly matching ground textures- The eastern side of Oregon beautifully represented by Orbx's FTX textures, landclass, mesh and more- Moving traffic on all major and minor roads, properly aligned to the photoreal ground terrain- 3D light poles along roads and in urban/township streets and around the airport- Orbx's modified autogen houses, custom trees and other objects- The FTX Central application, which is used to launch all the Orbx tools and also switch FTX off

Hi,Yep, same issure here too. above 150 and the blurries set in. It is very demanding but accurate to say the least.Bob

PNW is a strange beast for me. I can run it with good FPS all around even with complex a/c and lots of AI, but the only issue I have with the area is that I struggle to keep the ground tiles in focus when flying planes like the PMDG's and LDS 767. Low and slow a/c are no problem, but anything complex at faster, ie anything greater that 150 kts gives me some blurries. PNW is kind of a write off product for me since I normally fly heavies.When KPDK comes out I will most likely be trying to find a way to install it outside of the ORBX folder so that I can run it as a seperate airport without having to have the PNW turned on. This way I can still enjoy that airport when flying heavies but not be burduned with the blurry ground textures PNW gives me.

Hi,Well good news and I am quite suprised. I think the improvement I am seeing now, which is signifigant from previous trys, and I believe it must be the .003 patch. Nothing on my system has changed including detail settings. I am getting a 25% improvement in frames and it is really quite smoothu. Again the only difference with this install was the 003 patch. I am really enjoying. Who knows what tomorrow may bring and I may have to perform another exorcism. FSX seems to have a life of its own sometimes.RegardsBob

I get excellent performance with the PNW scenery except for the areas around cities. There are tweaks you can do to reduce the autogen in cities without it affecting rural areas. Personally I just live with the lower framerates over cities. Only time I pass the bigger cities is when I'm on the way from rural airport to another :)From the Cushman Meadows manual:WHAT WILL YOU MISS OUT ON IF YOU DON'T HAVE ORBX FTX INSTALLED?- Blending of the airport photoreal into the surrounding terrain with exactly matching ground textures- The eastern side of Oregon beautifully represented by Orbx's FTX textures, landclass, mesh and more- Moving traffic on all major and minor roads, properly aligned to the photoreal ground terrain- 3D light poles along roads and in urban/township streets and around the airport- Orbx's modified autogen houses, custom trees and other objects- The FTX Central application, which is used to launch all the Orbx tools and also switch FTX off

Good to hear the PNW.003 patch helped! We have the PNW.004 patch coming out soon (Holger is in Germany but working on it as we speak).TIP: For the Seattle area, simply drag the Scenery Complexity slider to the left one notch - it makes all those cranes at the Seattle docks area go away (you won't miss them really), and viola! ,an instant FPS boost in Seattle. Also, reducing the scenery complexity slider will not have too much impact in the other Orbx airports since their complexity is controlled using their control panels, not the sliders.So give that a go and revisit the Seattle area.P.S. we have a side freeware project going which is going to do a CityScape Seattle using the same tech as our freeware Portland, which replaces all the FPS-heavy models in the city and docks with uber-efficient ones. Stay tuned.

Cityscape for Seattle is great news.That area really does slow down my machine.If it's anything like the Portland one it will improve things enormously.Thanks

Hey that is great news. Nice to know that the team just keeps going and going and going........RegardsBob

Good to hear the PNW.003 patch helped! We have the PNW.004 patch coming out soon (Holger is in Germany but working on it as we speak).TIP: For the Seattle area, simply drag the Scenery Complexity slider to the left one notch - it makes all those cranes at the Seattle docks area go away (you won't miss them really), and viola! ,an instant FPS boost in Seattle. Also, reducing the scenery complexity slider will not have too much impact in the other Orbx airports since their complexity is controlled using their control panels, not the sliders.So give that a go and revisit the Seattle area.P.S. we have a side freeware project going which is going to do a CityScape Seattle using the same tech as our freeware Portland, which replaces all the FPS-heavy models in the city and docks with uber-efficient ones. Stay tuned.