Please replace ALL files with the newest version.  If you have already downloaded the unified SayIntentions_AIFlow_AIGround_ConfigUtil_2100.zip file, you do NOT need to re-download this AIFlow update.

New for AIFlow ver. 2100:  I am honored to announce that SayIntentions.AI has acquired AIFlow, AIGround and the Configuration Utility.  This version has been updated to reflect the new ownership.  I will also develop for SayIntentions.AI. and their talented team.  Working together, we will be able to build on AIFlow and AIGround to deliver even better solutions for the flight sim community than would be possible if I continued working individually.  AIFlow and AIGround will remain free for the Microsoft Flight Simulator (MSFS) community, ensuring that flight sim enthusiasts continue to benefit from the tools’ renowned realism and enhanced simulation features

AIFlow is a MSFS simconnect utility designed to ease AI congestion and go-arounds at the airport the user is departing from and arriving at.  

As a first step, AIFlow will make all AI in the monitored area cruising at high altitudes maintain minimum speeds according to an altitude vs. speed profile that can be customized. 

Regarding the approach phase, AIFlow enforces spacing minimums between arriving AI aircraft to make the approach patterns more orderly, first by varying speed, then commanding holds if necessary. By controlling approach speed, AIFlow can also make approach patterns more uniform for differing AI aircraft (e.g., slower piston vs. faster turbojet).

AIFlow also detects and corrects poor AI approaches under the control of the MSFS AI engine (e.g., too high, indefinite circling, crashes into terrain, flying too slow).  The terrain and circling protections also apply to AI departing from monitored ICAOs.  

AIFlow can force inbound AI to land on user-specified runway(s) at an airport (Force Landing mode) to aid traffic flow. No limit on the number of airports (lists allowed), but two runways max per airport. Useful to force landing runways for expected weather or traffic at departure, destination and alternate airport or to build a personal list of airports and preferred landing runway operations. The airports and landing runway(s) can be changed while AIFlow is running (e.g., changing to adjust to different weather). AI will fly orderly traffic patterns, NOT go-around and flare properly at landing. When using this feature, AIGround must also be running at the SAME TIME as AIFlow. AIGround’s AILandingTargetTime option must also be enabled (it is default on). Additionally, at least 30 FPS in the MSFS sim must be maintained to ensure this feature operates smoothly.  Also added custom squawk code to temporarily stop landings on busy runway to giver user a depart slot (disabled by default).

AIFlow also supports a custom approach files (e.g., KJFK Parkway Visual 13L) as a specific type of Force Landing mode discussed above.  For example, if AIForceLandingRunway=KJFK,13L is included in the AIFlow.ini file, then AIFlow will look first for KJFK runway 13L custom approaches in the custom_approaches subdirectory that – if found – take precedence over the more general Force Landing approach discussed above.   Several example custom approach files are included in that directory, including the KJFK Parkway Visual 13L , KDCA (Reagan National) River Visual 19, LOWI (Innsbruck) Visual 8, LFLJ (Courchevel) Visual 22, TFFJ (St. Barth) Visual 10 and KEYW (Key West) Visuals 9 and 27 (VFR traffic pattern examples).  The KSAN RNAV 27 approaches for both the KLOMN and LYNDI IAF(s) are provided as provided as examples to show that AIFlow will support multiple custom approaches for a single runway (e.g., AIForceLandingRunway=KSAN,27). The is chosen based on how close the AI is to the IAF (e.g., KLMN or LYNDI). The KATL ILS 8L and 9R approaches are also included as examples to show that this concept can be extended to two runways (AIForceLandingRunway=KATL,8L,9R).

For added realism, AIFlow adds landing effects that scale up during crosswind conditions for either normal or Force Landing mode.

AI taxiing out to the same runway that AI on short final for can optionally be commanded to stop in order to reduce crowding (stacking) near the hold short line and to reduce the chance of incursions between AI attempting to land and AI attempting to depart the same runway.

While the user's aircraft is in flight, AIFlow enforces spacing spacing minimums between the AI aircraft and the user’s aircraft during all phases of the user’s flight (e.g., departure, enroute and approach).  This feature is default OFF and must be enabled.  AIFlow also optionally provides protection against AI incursion onto the runway (including AI that becomes stationary on the runway) when the user takes off and lands.  This feature is also default OFF and must be enabled. 

While the user's aircraft is on the ground and departing an airport, the user can also briefly squawk a custom squawk code in their aircraft to temporarily suspend AI landings so that the user can find a slot to depart a busy runway.  

If both AIFlow and AIGround are running simultaneously and their Force modes are active for the same airport(s)), then AIFlow will communicate with AIGround to perform automatic arrival/departure traffic load-balancing via a datalink at those airports. When load-balancing kicks in, in progress departures will be prioritized, pushback releases temporarily stopped and arrivals delayed. This is similar to manually entering the special squawk code (below) to temporarily stop landings discussed above.

AIFlow also supports a traffic density management feature called AICull that removes excess AI traffic in the user’s reality bubble according to several parameters (e.g., distance from the user, max number of AI aircraft, ground vehicles and boats in reality bubble, preferred ICAOs, aircraft type, etc.) in order to increase FPS. AICull is recommend for .bgl traffic (e.g., MSFS AI Offline), such as general aviation .bgl-based mods. Caution should be exercised using traffic injectors, such as FSLTL, AIG TM or Just Flight because traffic removed by AICull may be promptly “re-injected” by the injectors causing a traffic removal-injection loop. However, certain injectors may not exhibit this behavior.

AIFlow does not require a configuration file to run, however the configuration file AIFlow.ini is included, which contains several parameters that the user may change to suit personal preferneces.

AIFlow is designed to compliment the default MSFS AI program and thus is fully compatible with it.  Thus, AIFlow is compatible with any AI-related program that places AI mostly under control of the default AI program (SU14), such as MSFS live traffic, MSFS off-line traffic and external AI injection programs that mostly rely upon the default AI program after injection.   

AIFlow operates externally via simconnect and thus makes NO changes to the MSFS sim. 

See the included readme.txt and readme.pdf for additional details.