Hi guys,FSX is missing just so many airports, runways, taxiways, etc. I mean, yesterday I posted a thread about a Janet 737-600 departing McCarran Intl. and I tried to recreate a flight of it from KLAS to KEDW using the NGX, but it's impossible. KEDW is missing a runway, but the FMC says that it has 3 while my FSX only has 2. This happens so many times to me. Then, there is Seattle/Tacoma missing the center runway. Then, there is O'Hare missing the new ruwnay. Then, there is Minneapolis/St. Paul missing the new runway. Then, there's Tampa with the wrong runway heading. Then, there is St. Maarten with the wrong runway heading. Then, there is... It just keeps on going! :(Before each flight on VATSIM that I do to an airport that I've never flown to before, I check on Wikipedia how many runways it has then I go to the airport in FSX using the Ultralight Trike then do a top down view to match the airport diagram. This gets very annoying. It kinda sucks, doesn't it? :sad:I wish somebody would do a big update to FSX's data.

The best way to remedy this is with AFCADs available at the library for airports you'll be flying. Also, the magnetic variation update linked in PMDGs forum is a must IMO.

The best way to remedy this is with AFCADs available at the library for airports you'll be flying. Also, the magnetic variation update linked in PMDGs forum is a must IMO.

I looked at that magnetic variation update/mod, but how does it work? Are you allowed to install both Europe and America versions?

Janet 737-600 departing McCarran Intl. and I tried to recreate a flight of it from KLAS to KEDW using the NGX, but it's impossible. KEDW is missing a runway, but the FMC says that it has 3 while my FSX only has 2.

I didn't think Janet flew to Edwards since pretty much everyone, military or civilian contractors can drive into Edwards. From what I understood is that Janet primarly operates the daily shuttle to Area 51 or other secret or undisclosed locations. In any case, you can probably find a replacement ADE in the library here or simply add another one pretty easily using ADEX.

Then, there is Seattle/Tacoma missing the center runway. Then, there is O'Hare missing the new ruwnay. Then, there is Minneapolis/St. Paul missing the new runway. Then, there's Tampa with the wrong runway heading. Then, there is St. Maarten with the wrong runway heading. Then, there is... It just keeps on going! :(

There are a couple fixes for KSEA in the library here, as well as the ORBX PNW adds the updated runway for KSEA.If you dont mind spending a few bucks, FSDT has released the update for KORD and you could buy the KMSP with the correct runways from BluePrint Sim. For Tampa and St. Maarten, FlyTampa have both of these airports covered with a seperate downloadable .bmp file to change the runways to the correct numbers. However, you might be able to find some ADE's for these aiports in the library here on Avsim or elsewhere that will fix you up for free.Like Travis said in his post above, there's probaby an updated ADE file for most large or midsize airports to get you up to date. Some of this was missing from FSX just due to the airports having been changed after MS got the airport data they needed to complete the sim. After all, being a $50 retail "game"/sim, you cant expect it to be perfect out of the box which is why we are able to upated it using ADEX for free. You could always open the airport your going to fly to in ADEX first before you do a flight and be sure it has the included runways before you start your flight so your not surprised when you get there.

Whenever I fly to an airport i've never been to before I just google the airport name + scenery fsx, for example KSEA scenery fsx. That usually tells me if i need to update the default and where i can get an update.