• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Introducing Development Release 3.4.3.14(b)

Status
Not open for further replies.
Sorry, folks. As almost invariably happens, with hours - or in this case moments - of a new general release an issue is discovered that necessitates an update. In this case, due to a typo I made in the late stages of Version 10 development, the compile dialog opened for every compile, not just when it was needed. Version 11, fixing that issue has been uploaded to http://stuff4fs.com. It should be detected automatically the next time you run AIFP.

Don
 
I have just uploaded Development Release 3.1.11(f) to http://stuff4fs.com.

It resolves:
  • an exception that was thrown when attempting to create a timetable from a Flight Plan List that included comments
  • a Day-1 issue with the timetable whereby the day-of-week display for over-midnight flights may not have been handled properly, and
  • an issue with the creation of a balanced set of flight plans from timetable data
The first issue was introduced in Version 3.1.10. The other two have been around for a while. They were both caused by hard-to-see typos.

Please give this development release a workout. If no more issues are highlighted in the next day or so, I'll release it generally.

Don
 
I have just uploaded Version 3.1.12 to http://stuff4fs.com. It should be detected automatically the next time you run AIFP. This new release was made necessary by a couple of deficiencies in the enhanced Timetable function initially included in Version 3.1.10 that, depending on the data, sometimes resulted in exceptions being thrown. This release alsoc ontains a fix for a long-standing issue with "deadhead" legs being added to flight plans created from timetable data.

Please refer to the included Version History for additional detail.

Don
 
I have just uploaded AIFP Development Release 3.1.12(a) to http://stuff4fs.com. Among other things, it:

  • [li]adds a Delete Selected button to the Select Aircraft dialog (used for substitutions and elsewhere);[/li]
    [li]adds a "sequence [fltsim.n] blocks" function for general use [/li]
    [li]highlights any legs not assigned when using the fewest FPs mode to create flight plans from timetable data[/li]
    [li]avoids an occasional exception thrown when selecting a DOW radio-button in the Traffic Analysis timetable[/li]

Regarding the second item, Sequencing [FltSim.n] blocks, AIFP has always had this capability. It was only used when deleting aircraft. However, given the repeated requests for such a feature, I have exposed the functionality for general use under the Main Panel Aircraft menu.

Please check out the new functionality and report any difficulties.
Don
 
I have just uploaded AIFP Development Release 3.1.12(b) to http://stuff4fs.com.

Apparently, a mixture of "[Fltsim" and "[fltsim" in an aircraft.cfg file sometimes creates difficulties for FlightSIm. So, since the SDK shows "[fltsim", this release uses the lowercase version only. As well, it adds some further detailed information to the confirmation report when legs remain unassigned from Create FPs from Timetable Data.

Please check out the revised functionality and report any difficulties.

Don
 
I have just uploaded Version 3.1.13 to http://stuff4fs.com. It should be detected automatically the next time you run AIFP.

The changes from Version 3.1.12 are minimal. Generally, they are:
  • a couple of fixes in the Traffic Analyser,
  • using "[fltsim." rather than "[Fltsim." when making changes to aircraft.cfg files (either is acceptable to Flightsim, but certain other utilities cannot cope with the upper-case version)
  • add a "Resequence [fltsim.n] entries in aircraft.cfg" function.
Please refer to the included Version History for additional detail.

Don
 
General Release 3.1.13 introduces padding for certain FP fields to allow for better vertical alignment for FP legs in tooltips and in the FP Text Editor. A side effect of this change is that should you save your data in a file set, the padding in included in the text file. These additional spaces are of no consequence, but are of (needless) concern to some users.

Development Release 3.1.13(a) eliminates the padding from flight plan .txt files. You can download it from http://stuff4fs.com.

Don
 
Any of you who are receiving a "you've made changes" message upon attempting to load a file immediately after startup may wish to install Development Release 3.1.13(b), now available at http://stuff4fs.com. I've found and fixed an error in the resequence aircraft numbers code that could set a "file-changed" flag set even though there were no aircraft to renumber.

Don
 
LM released P3Dv3 last week. Those of you who have acquired it will be pleased to learn that AIFP Development Release 3.1.13(g), now available at http://stuff4fs, allows you to conduct flight planning activities for P3Dv3.

I am not aware of an any AI-related changes in v3. Consequently, AIFP handles v3 exactly as it does v2 - and assumes an identical registry naming scheme. I say "assumes", since LM seems to want to extract another license fee from me for v3 and, at the moment, I'm resisting.

If you discover any v3-specific issues, please provide as much detail as possible in your reports.

Don
 
I have just posted Development Release 3.1.13(I) to http://stuff4fs.com. It corrects all P3Dv3 problems reported so far and, as far as I can tell, handles every P3Dv2 feature for which there is an equivalent in v2 exactly as it was handled in v2.
When you download, be sure to select the Development Release menu button.
Don
 
Shortly after posting 3.1.13(i), I became aware of a potential issue with the installation of repaints. Development Release 3.1.13(j) fixes that issue and includes a little "clean-up". If you've already downloaded (i), please update to 3.1.13(j).
Don

EDIT: In fixing an earlier P3Dv3 bug, I introduced another. Please update to Development Release 3.1.13(k) - http://stuff4fs.com
 
Last edited:
AIFP now offers P3D v3 compatibility.

Since it has been more than 2 weeks since I made the last development release, 3.1.13(k), with no new issues being reported, I feel comfortable in making it a general release. Consequently, I have just uploaded Version 3.1.14 to http://stuff4fs.com. It should be detected automatically the next time you run AIFP.

In addition to P3D v3 compatibility, this new release also addresses a few non-v3 issues that have recently been reported. Please refer to the included Version History for additional detail.

Don
 
It's really unfortunate that more people don't use the development releases. The end result is that errors such as AIFP not automatically selecting the last used FS Version at startup - which would otherwise have been identified and resolved prior to general release - aren't reported until after a general release.

I have just uploaded to http://stuff4fs.com Development Release 3.1.14(a) which initializes the target version at startup to the version selected at the previous shutdown. Be sure to download the development release.

I'm going to wait for a few days to see what else "crawls out of the woodwork" before re-releasing generally.

Don
.
 
I have just uploaded Development Release 3.1.14(b) to http://stuff4fs.com. It:
  • enables the Flight Plans/Subset button at startup, and
  • allows manual extraction of repaint archives when AIFP is unable to automatically extract them.
Regarding the latter, it seems that certain repaint providers are now using a .zip format that cannot be read by AIFP. When that situation arises, AIFP will advise you to manually extract the files to a folder named as the .zip file less the .zip file extension. That file MUST be in the same folder as the .zip. Do not delete the .zip until you have completed the installation. While the revision seems to do what I intend, it is only through you guys exercising the code that we can be sure. Please let me know of any problems and when you are happy with it.

Don

BTW, the recently-added Version.ini file is now gone. It has been reintegrated into AIFP.ini.
 
For those of you who make use of the Traffic Analyser, I've just reworked the peak parking utilization features to provide much more flexibility in your analyses. You may now analyse with any combination of parking codes and parking types, filtered by aircraft parking radius. Please download Development Release 3.1.i4(g) from http://stuff4fs.com.

Given the other issues addressed by this series of development releases, it will soon be time for a new general release. Hopefully. some of you more experienced users will download and use the latest development release (whether or not you are interested in the enhanced traffic analyser) in order to minimize the likelihood of a new bug being reported within hours of the next general release.

Don
 
I've just uploaded Development Release 3.1.14(k) to http://stuff4fs.com. For some time, I've been meaning to adapt the Select Aircraft dialog (that pops-up in a variety of function) to display its data in a listview control. This provides much more flexibility. Finally got around to it.

Please give it a try.

Don
 
At long last, I've released Version 3.1.15. Not that I've run out of things to add/enhance; I've just run out of alphabet for development releases. The next time you run AIFP you will be notified of the update. Download it when prompted and copy its contents over you current installation - or, if you want to be extra cautious, create a new folder for Version 15 but before installing Version 15, copy the contents of your Version 14 folder into it.

Version 3.1.15 is the same as 3.1.14(v) with the addition of a newly-requested OLDAIRLINES feature. (The operation of that feature depends on there being an OLDAIRLINES entry in aifp.cfg.)

It has just been reported that AIFP is not fully compatible with FSX-SE and, it turns out, that is the case. FSX-SE compatibility will be the cause of an early Version 15 development release.

Enjoy,
Don
 
Not surprisingly, a few hours after general release, a user reported a significant/annoying problem that had escaped detection during final testing. In this case, when you select a flight plan that uses a different aircraft than the one already selected, the previous selection remains in addition to the new selection.

I had planned to make a new development release today to accommodate a user's request for FSX-SE support (after the general release so as not to destabilize it). Development Release 3.1.15(a) is now available at http://stuff4fs.com. As well as the FSX-SE "stuff", it fixes the noted problem. (As it turns out, due to some changes I made a couple releases ago, the SE changes should not have destabilized anything.)

So, if this new issue bothers you, please download the development release. I'll make a new general release as soon as we know the SE changes don't have an unplanned side effects.

Don
 
Late yesterday I uploaded General Release 3.1.16 to provide independent FSX-SE support and to address a couple other minor issues. As usually happens, within hours, a problem was reported - I this case, one that was introduced several months ago. So, the next time you start AIFP, you will be advised that General release 3.1.16(a) is available.

The new general release may be obtained directly from http://stuff4fs.com.

Enjoy,
Don
 
Status
Not open for further replies.
Back
Top