Version 1.01 addresses an oversight whereby, when adding new aircraft to the Aircraft List, the associated aircraft.cfg file was updated whether or not the cruising speed was changed. While this should have been of little consequence, apparently, FSX SP2/X-Pack "objects" when a default aircraft is modified in any way and takes several restarts before it recovers. Version 1.01 also addresses a problem where, if a new leg was inserted as the first leg of a flight plan, its originating airport was not recognized as the starting airport for that flight plan
When arrivals and departures for an airport were displayed, certain arrivals may have been missing. This has been fixed. Also, the version of FS used for the last compile and the last airport edit is now saved from one session to the next.
AI Flight Planner Version 1.08 is available here. It contains a fix for the problem reported earlier today by "lucclaus" whereby the FS9/FSX day-encoding selection was not being taken into account when flight plans were saved in the weekly-consolidated mode.
As well, under certain conditions, attempting to switch between the consolidated and non-consolidated mode resulted in an endless message loop. This as been fixed also.
First, as noted in another post, I am concerned that the compiler is not properly handling FS9 to FSX day conversion in all cases. AIFP now does the day conversion.
I have also discovered that the compiler/decompiler (I'm not sure which) does not handle midnight departures properly. (On decompile, they are scheduled a day early.) AIFP now looks after this as well.
The AIFP compile "flag" previously was an extra entry in the aircraft file with a reference number of "0". (The compile flag is the means by which AIFP knows when it decompiles a traffic file that it was compiled by AFP in the "normal" mode.) Becasue of the way aircraft data is stored in the traffic file, I am concerned that using AC#0 may have some unintended side-effects. Commencing with this release, the AIFP compile "flag" is an extra entry in the airports file with the ICAO symbol "*#@"". (That shouldn't conflict with any legitimate ICAO codes.) However, AIFP will still recognize the old extra-airport-flag for those of you who have already created traffic files and take appropriate measures.
AIFP now limits the number of characters in aircraft registrations (<=7) and the value of flight numbers (<=18383). I discovered these two traffic-file limits while investigating the above compiler issues.
The bulk FS9->FSX traffic file conversion seems to be working properly, so feel free to use it.
Finally, all bugs reported to date have been fixed.
I had hoped that Version 1.1 would be the last release for a while. But, the liklihood of me having made all these changes without "breaking" something is fairly remote. So, please be cautious.
Considering only a single problem report since Version 1.10 was released (and that one easily fixed), I have re-released AI Flight Planner on both Avsim.com and Flightsim.com as Version 1.1. It is also available here
Thanks to all those who have borne with me over the past few weeks and who helped me eliminate many residual bugs in the first release of AI Flight Planner.
As noted in another thread, there were still some difficulties with the latest general release creating custom airport lists. I've reworked that area. As well, I discovered a minor problem with flight in a very comple weekly flightplan, a leg having he same departure and destination airports escaped detection. This has also been fixed.
Minor changes are identified in the included "Version History.pdf". Two major changes:
Both FS9 and FSX require the aircraft list to be sorted numerically. If it's not (and it previously wasn't), many AI would not appear. AIFP now sorts the aircraft list.
Given the significance of the first item above, I will make another general release early next week. So, please give this one a real workout.
EDIT:Regarding appearance if AI, please note that the startup situation with FSX is quite different depending on whether the traffic file was compiled for FS9 or FSX. With a compiled-for-FS9 file, many more AI are on the ground. It appears that some spawn early. With a compiled-for-FSX file, my tests indicate that some AI that are scheduled to be on the ground at start-up time aren't, but instead will land shortly afterwards. Eventually, the two situations become similar.
It contains several improvements, the most significant of which is that Vista users should now be able to collect airports and convert FS9 trafic files without the system throwing a "no access" exception. As well, all the times in a flight plan may now be advanced or retarded by one hour to all flight plan files to be easily adapted for use with summer time.
"Collect airport" fans are in for a treat. Version 1.22 available here includes a new custom airport .bgl decompiler that speeds-up collection by at least a factor of 10. AI Flight Planner no longer requires BGLAnalyse9.exe and BGLAnalyseX.exe be present in the AIFP folder.
AIFP version 1.22 should not be used to collect airports. (Otherwise, it's identical to 1.21.) It does not handle add-on files generated by AFX properly and there are some as-yet-unidentified other differences between the AirportList.dat generated by it and that generated by its predecessor using BGLAnalyse. I'll try to have a fix available later today.