Thanks, I'll try it out tonight.

 

I've got most of the change data for the first 21 "fixes" ready to go, other than still needing to verify how the entries for MagVar, Runway Sfc and Runway Hdg work.

 

From the Tetlin example, Runway Hdg appears to be a 90 degree offset between the two actual runway headings.

 

Runway Sfc will require me to check the surface at several runways in the database against real-world data, to figure out which numbers correspond to which surface-type (gravel, turf, etc)

 

MagVar appears to be stating the magnetic heading for True North, rather than the traditional way of reporting the deviation relative to True North (such as 22E).

 

Of course, for our simple planning purposes in Flight, none of them probably matter much if I get something wrong.

 

So, expect a new Plan G database to play with later tonight or possibly tomorrow, depending on how things go. 21 changes is about 3% of the total airports in Flight's Alaska, so that's a bit of progress.

:t0116:

You guys deserve an award if this all works out! Thanks for all the effort.

I seem to recall someone explaining how to open a specific Flight file to check out which airports you had already visited in the game: I don't remember if that file shows EVERY airport by default. If so, maybe opening that file and opening the Plan-G database side to side would make editing for instance all ICAO codes a lot easier. Well, maybe...

 

OK J, your task is to go land at every airport in Alaska to make sure that list is fully populated, then send it on over! :p0502:

OK J, your task is to go land at every airport in Alaska to make sure that list is fully populated, then send it on over! :p0502:

 

Er... roger... over and out. See you when you are done with the database...

Ok, here is the deal with Manokotak....

 

Somebody goofed.

 

According to current charts, the Manokotak Airport (PAMB) is located 6 miles southeast of the town of Manokotak. According to satellite imagery, there is another airport where the town of Manokotak (gawd, if I type this a few more times I might spell it right on the first try) is actually located, right on the northern edge of town, assigned the 17Z code, right where Flight has it. The airports have totally different physical data (elevation, runways, etc.), so they are not duplicated data. I can't find any airport by satellite southeast of town, but the overheads there are terrible.

 

EDIT: Actually, I'm still researching this... the plot thickens!

 

I'm finding conflicting data and I don't think I can sort this out with going up there myself. And we don't really need to do so anyway, since we're more concerned with what's in Flight than in the real world.

 

For the purposes of Flight, I propose creating a new "Manokotak Town Airport" (and yes, I did spell it right that time on the first try!) using the 17Z code in Plan-G's database on the location of the town itself. I can get the LAT/LONs from the Stearman's GPS and the rest of the data by looking at the Airport panel in the game.

 

How does that sound?

from the Stearman's GPS

I didn't know it had one.

 

The rest sounds good.

I didn't know it had one.

 

The rest sounds good.

 

It's not much of a GPS... but the little handheld radio also has GPS-derived LAT/LON and ALT displayed on it.

 

 

I used it a bit flying by paper sectional.

 

But in any case, your editor app works perfectly! I'll have a product to post later on.

But in any case, your editor app works perfectly! I'll have a product to post later on.

Cool. I wasn't sure because I've had mixed results distributing stuff made with Visual Studio. I have the full environment at home and work so everything always works fine for me.

 

I'll do another one for the NAV aids if there is need.

Ok, the Manokotak thing is coming back to haunt me... I misunderstood the Plan G situation for it. Turns out, Plan G already has the 17Z airport in the right location. I need to create the other one, to the southeast, using the PAMB identifier. Airnav seems to have the correct info on the airport in this location, so I'm using it.

 

With a spur of creativity, I shall call it "Manokotak Southeast"!

All posted changes are in. The only exception is "Emmonak is PAEM in Flight but ENM in Plan-G." I found Emmonak to be PAEM in both Flight and the FSX database being distributed.

 

You can download the updated database here: http://sdrv.ms/Nv9b6m

 

Copy it into your Plan-G/Data folder. WARNING: this will replace your existing FSX database file. Make a backup copy of your original file before doing this, in case any problems occur.

 

If problems do occur, and you didn't make a backup copy, I'll play a tiny violin for you and that's all you're getting from me.

 

If any download-related problems or usage of the file with Plan-G come up, let me know and we'll try to figure it out.

 

If it does work, start sending me more things to have fixed! :Party:

Cool. I wasn't sure because I've had mixed results distributing stuff made with Visual Studio. I have the full environment at home and work so everything always works fine for me.

 

I installed a bunch of stuff from MS that CompactView depends on, so that may have helped.

 

The only thing I could not figure out was clearing the data from all the fields in the editing window. But the app loads instantly, so I just closed the app and restarted it after adding each airport.

 

Is there a way to deselect the selected airport, clearing the fields so another can be added?

 

I'll do another one for the NAV aids if there is need.

 

I have not noticed any navaid errors yet, but we shall see. I can always fix them in CompactView if it's just one or two.

 

Is there a way to deselect the selected airport, clearing the fields so another can be added?

Dang. I should have put a clear button on it. Sorry, I just didn't think of it. I'll add one and update the download. It will only take a few minutes to add but it will have to wait for tomorrow because I didn't bring the source files home.. I was also thinking of adding some way to select the area to edit. Right now I only show Alaska and Hawaii but I could add a way to select the state or area and that way it will be useful for not only the next area DLC but for FSX mods if needed. I'll take a look tomorrow.

I've update the editor for the following.

Added an Add Airport button that takes you to a cleared entry screen or clears the data from the entry screen.

I added the ability to select a state, (wishful thinking for future DLC), but it defaults to Alaska and Hawaii.

Added a box to enter the ICAO code if you know it. That way you don't have to scroll through the list to find it.

 

You can get the new version at the same location as the last.

 

If the next DLC is in a different country I'll deal with it then.

I've update the editor for the following.

Added an Add Airport button that takes you to a cleared entry screen or clears the data from the entry screen.

I added the ability to select a state, (wishful thinking for future DLC), but it defaults to Alaska and Hawaii.

Added a box to enter the ICAO code if you know it. That way you don't have to scroll through the list to find it.

 

You can get the new version at the same location as the last.

 

If the next DLC is in a different country I'll deal with it then.

 

That sounds like a plan... Thanks for the updated editor.

 

Does anyone have feedback on the revised database? I would appreciate if somebody could at least verify for me that you were able to download it and that the changes are working for you.

That sounds like a plan... Thanks for the updated editor.

 

Does anyone have feedback on the revised database? I would appreciate if somebody could at least verify for me that you were able to download it and that the changes are working for you.

 

I downloaded it without problem but was unable to try it out last night because I had to work on a hair dryer for the wife. (she has a dog grooming business) Maybe tonight I'll have some time.