July 18, 201213 yr 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. It works! Awesome! I first checked the errors from my yesterday post in Plan-G while downloading your modded file. After checking those erros, I quit Plan-G, copied the new file into the Data folder (after backing up my original), started Plan-G and now all the codes and missing airports from my yesterday post were there!!! Cool!!! No problems, no errors, no messages, no nothing. ;)
July 18, 201213 yr Author It works! Awesome! I first checked the errors from my yesterday post in Plan-G while downloading your modded file. After checking those erros, I quit Plan-G, copied the new file into the Data folder (after backing up my original), started Plan-G and now all the codes and missing airports from my yesterday post were there!!! Cool!!! No problems, no errors, no messages, no nothing. ;) Fantastic! Ok people, start posting more problems as you find them... Anything that Flight and Plan-G don't agree on, let me know. This goes for Hawaii, too. If a Flight airport is missing from Plan-G, please post the Name and Identification Code used by Flight. If you can visit it to tell me what type of runway surface it has (asphalt, gravel, dirt, grass, water, etc) that will help too. If an airport has one Code in Flight and a different one in Plan-G, give me both. Keep in mind that I may not take the time to verify every "delete" request due to airports in the Plan-G database not being present in Flight. So, make absolutely certain it really does need to be deleted before telling me to delete it! If you're not 100% sure about something, just ask me to take a look at it. I'll try to sort it out. I do need to take another look at the MagVar and Main Runway Hdg values. I couldn't quite figure out how the values are being produced by Plan-G, so I approximated them. It shouldn't impact us for flight-planning, as I suspect they are just in there to properly orient the airport symbol displayed on the map so that the runway is aimed in the right direction.
July 20, 201213 yr Hello Folks, That is a list of some differences i noticed: Different ID codes: Plan-G / MS Flight JZZ / PAJZ KNW / PANW CEM / PACE VEE / PAVE Existing airfields: Plan-G / MS Flight PAZK / missing A88 / missing CZST / missing (the area is cleared, but no runway, and not in the map) -------------------- Keep on flying!
July 20, 201213 yr CZST is in Canada so I'm not sure Flight would have had it anyway. We can't add airports to Flight so it would most likely be best to remove them from Plan-G. On the other hand I guess we could just consider some of these missing ones as remote and undeveloped strips. Still,you will not be able to select them in Flight. Rag Tag Fleet Development Team Member. http://yankeeclippersmobile.com/forum
July 20, 201213 yr Author I've been deleting Alaska airports from the Plan G database if they are not present in Flight, to facilitate using Plan G to pick a destination in Flight. I've got a list of about 40 more changes I'm working on, so I'll add these to it and hope to get a new database revision posted this weekend.
July 20, 201213 yr CZST is in Canada so I'm not sure Flight would have had it anyway. We can't add airports to Flight so it would most likely be best to remove them from Plan-G. On the other hand I guess we could just consider some of these missing ones as remote and undeveloped strips. Still,you will not be able to select them in Flight. Ops, i didn't know that. The strange thing is that the Dev team cleared a rectangular area among the trees exacly were the airfield should be! Well, maybe it will be filled when the Canada DLC comes up. Nice flying to all!
July 20, 201213 yr Author Ok, found another thing I'm going to fix... Several airports have different names in Flight as compared to Plan G, which can make searching for them in Plan G a little harder if you are looking for the Flight name. For example, KEB is "English Bay" in Plan G but "Nanwalek" in Flight. I've also seen a couple with the same name, but the spelling was a bit off (usually capitalization or punctuation differences). There may be other stuff out there I haven't noticed, as well. But in any case, if you find any differences between Flight and Plan G whatsoever, please bring it to my attention here in this thread.
July 20, 201213 yr Author Revision 2 of the Plan G database for Flight is now available for download here. As before, copy it into your Plan-G/Data folder, after making a backup copy of your existing FSX database. The 63 changes completed to date can be viewed here in Excel format, since AVSIM does not honor table-insertions.
July 21, 201213 yr Hi Folks! Today in my "Alaska: all airports journey" i began tackling the Anchorage main airfield "cluster"...a region with about 120 airfields, more or less. I was able to fly the first 73 airfields in my plan until now and i noticed that some airfields missing. I´m really sorry not to post more detailed information about the airfields today...kind of tired after all those flights...but i promise to double check the info tomorrow. Most of the area i´m flying is between and a little south of the BGQ-Big Lake-VOR and AK53 airport , and I used the latest database (posted above): NOT IN PLAN-G DATABASE, but in MS FLIGHT MAP: Airfields : AK92, AA05, 97AK, AA85, AA06 (is on database - just missing info), 79AK (i guess it is a seaport, but the database say "grass" rw), AK85, AK99. Seaports: 66AK, AA85, 29A (island lake), AA11 (Misty Lake), AA01 (west beaver), 91AK (kucera), AA02 (horseshoe lake), 86AK (HOPPE'S), L95 (JONES LANDING), 85AK (MARION), 6A7 (BROCKER LAKE) NOT IN MS FLIGHT but in PLAN-G DATABASE AK79, 7AK4 Difference in ID CODE: one airfield were Plan-G is A89/ MsFlt is 41AK; I hope it helps...sorry again for not searching for all info today...no time left...but if you guys need any specific ones i can post it tomorrow. ------ Keep on Flying!
July 21, 201213 yr Author That's actually enough info for me... the airport code and what the problem is. I can gather the rest myself... the hard part is just finding the ones that need fixing. Thanks for checking the Anchorage cluster... I've been looking at the Kenai Peninsula and surrounding area, but that little bit looked like a nightmare. :P
July 22, 201213 yr Hello folks! I finally cleared the "main" Anchorage cluster (128 airfields in total, from 7AK9 to PAWD)...i noticed that AA30, 08AK, AA33, AK86, 36AK were missing in Plan-G too. ------- Keep on Flying!
July 23, 201213 yr Airport to change - Flight = Golovin (PAGL) - Plan G = Golovin (N93) Also I noticed that you made a list of changes you've made to the database, these included Airports that you had deleted from the database as they arent in Flight but show up in Plan G, this has caused a problem for me as I use Plan G for FSX too and now I have airports missing (temp fix, I've reverted back to my original file)
July 23, 201213 yr Author Airport to change - Flight = Golovin (PAGL) - Plan G = Golovin (N93) Also I noticed that you made a list of changes you've made to the database, these included Airports that you had deleted from the database as they arent in Flight but show up in Plan G, this has caused a problem for me as I use Plan G for FSX too and now I have airports missing (temp fix, I've reverted back to my original file) Thanks, I'll add Golovin to my list. As to creating problems for FSX usage, yes, as this version of the database is adapted for Flight, it is going to become less usable for FSX. For anyone using FSX to fly in areas also covered by Flight, I suggest keeping copies of both the FSX-standard database and the Flight-modified database, and copy the applicable one into the Plan-G/Data folder as needed. Anyone only using FSX outside Alaska and Hawaii (for now) should not encounter this issue. If you prefer not to deal with swapping databases around as you switch between FSX and Flight, another possible solution would be to take my list of changes and create your own User Waypoints for each airport marked "ADD." This should be easy, as the LAT/LON and any other information you need should be in the file. There are a number of drawbacks to this option, though, which I've outlined earlier in this thread when I decided to abandon the idea of doing this via Waypoints. I do intend to continue removing airports that are not in Flight, though, as several people have already commented that they like using Plan-G to decide where to go in Flight, which can obviously lead to problems if Plan-G includes airports that don't exist in Flight. The only real solution is for Plan-G to directly support Flight along with FS9/FSX, but my understanding is that this is unfortunately not even being contemplated at this time. In fact, it is only because they are not planning to support Flight for the foreseeable future that I decided to adapt the database myself. Otherwise, I'd just wait for that new "Build Flight Database" button to appear and automate the whole process.
July 23, 201213 yr How about this option. Name the flight data base the same as the FS9 database. That way it will not affect the FSX data and will only be a problem for the people using Flight and FS9 which I'm assuming is far fewer than those using FSX and Flight. Then they can choose which one to use in Plan-G. Rag Tag Fleet Development Team Member. http://yankeeclippersmobile.com/forum
Create an account or sign in to comment