Sorry folks, I scanned all available 15 pages of postings and didn't see the scenery problem under windows XP show up (just Linux).I downloaded scenery and unzipped it to 'C:Program FilesFlightGear.98dataSceneryTerrainw130n30', which now contains subfolders ...'w122n37' and ...'w123n37' each of which in turn contain all the *.stg and *.btg.gz files as I expected.My environment vars are: C:/Program Files/FlightGear/data andC:/Program Files/FlightGear/data/Scenery for FG_ROOT and FG_SCENERY respectively.The problem: "C:Program FilesFlightGearbinWin32fgrun.exe" doesn't pick up any new airports (like Omaha's Eppley Field or Offutt AFB, etc). Or am I to obtain airports from sources other than these scenery files?Please tell me what I'm mis-reading. Thanks muchThe Fiddler

>Sorry folks, I scanned all available 15 pages of postings and>didn't see the scenery problem under windows XP show up (just>Linux).>>I downloaded scenery and unzipped it to 'C:Program>FilesFlightGear.98dataSceneryTerrainw130n30', which now>contains subfolders ...'w122n37' and ...'w123n37' each of>which in turn contain all the *.stg and *.btg.gz files as I>expected.>>My environment vars are: C:/Program Files/FlightGear/data and>C:/Program Files/FlightGear/data/Scenery for FG_ROOT and>FG_SCENERY respectively.>>The problem: "C:Program>FilesFlightGearbinWin32fgrun.exe" doesn't pick up any new>airports (like Omaha's Eppley Field or Offutt AFB, etc). Or>am I to obtain airports from sources other than these scenery>files?While you did provide plenty of possibly relevant information, you failed to sufficiently describe the problem so far. That is, what exactly does "...fgrun doesn't pick up any new airports..." mean to you? Do these airports not show up in fgrun at all? If so, have you tried rebuilding the airports cache file? Also, you may have to make sure that the airports you would like to use are actually available in FlightGear.FlightGear itself should have all airports available in its navdb by default, regardless of the installed scenery. However, they will only be visually available (i.e. show up as runways) if you install the corresponding scenery tiles. So that's another potential problem source if you fail to install the correct tiles.So, you seem to be describing a problem that is more related to fgrun than FlightGear-have you actually tried running FlightGear directly?

I apologize. I pulled the help chord too soon. I ran fgadmin (not sure what it would do) and was pleased to see that I was able to get the downloaded file installed. Plus, embarrasingly, I had two flightgear directories: flightgear and flightgear.98. Of course, this confusion didn't help matters any....I'll try to do my homework next time. Thanks for the quick response. I was actually going to try to pull the post before anyone responded, but it's nice to know there are helpful folks out there.Happy New Year

>I apologize. I pulled the help chord too soon. I ran>fgadmin (not sure what it would do) and was pleased to see>that I was able to get the downloaded file installed.Actually, it should really not matter whether you manually install (=extract) the scenery tarball or not. At least as long as you do it properly, according to the instructions.>Plus,>embarrasingly, I had two flightgear directories: flightgear>and flightgear.98. Of course, this confusion didn't help>matters any....>>I'll try to do my homework next time. Well, no need to apologize-yet it's still not really clear to me whether FlightGear is working for you now or not?>Thanks for the quick response. I was actually going to try to>pull the post before anyone responded, but it's nice to know>there are helpful folks out there.you're welcome-but no need to thank-simply try to return the favour next time :)>Happy New Yearditto!