Ver. 2.0.22.3: Fixed user scrolling through AIFLow output console sometimes pausing AIFlow execution within sim. AIFlow.ini file does not have to be updated.
New for ver 2.0.22: (1) turns for general mode holds and altitude changes are now smoother (reminder: forced landing mode does not use holds, the AI is simply re-vectored back to the beginning of a known approach path). The AI will still exhibit the some shaking (as it fights against MSFS to execute holds), but when viewed from a distance the AI will appear much smoother during holds. If the user wants to completely eliminate the "shakes," set the new parameter AIGeneralPhaseLag = 1 (default = 3) at the expense of increased CPU usage; (2) general mode holding AI now performs brief inbound and outbound legs. Use the new AIHoldLegTime parameter (default = 20) (sec) to control the inbound and outbound leg time during general mode holds. Thus, setting AIHoldLegTime = 0 would result in tight, circular holds while setting AIHoldLegTime = 60 (sec) or higher would result in more standard holds at the expense of traffic appearing more chaotic near the monitored airport; (3) for forced landing mode, altitude changes during short final are smoother; (4) as previously discussed, the new AIGeneralPhaseLag and AIHoldLegTime parameters have been added, however AIFlow.ini does not need to be updated unless the user wants to tweak these new parameters; (5) dive-bombing AI protection deprecated (no longer needed).
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.
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.
13 days ago
11 days ago
ClipperOS
Caparzo86
17 days ago
17 days ago
ClipperOS
fennelda
3 months ago
20 days ago
AdamskiNZ
Sonosusto
3 months ago
ClipperOS
3 months ago
3 months ago
cteixeira
ClipperOS
3 months ago
3 months ago
ClipperOS
cteixeira
3 months ago
Corsten
4 months ago
4 months ago
ClipperOS
asegm08
4 months ago
4 months ago
ClipperOS
martijncoenen
4 months ago
4 months ago
ClipperOS
ThelynxPA
For those that aren't particularly interested in downloading a minor update, but want to use the new default values, change to the following in AIFlow.ini and save:
AIForceLandingFlareHeight=30.0
AIForceLandingTDDisplacement= 300.0
AIForceLandingFlareDisplacement=500.0
AIForceLandingMaxAltVar=9.0
Also, when using AIFlow Forced Landings, the AIGround landing target time value (mandatory for when using Forced Landings) can be set to 8 or even higher. So, also make the following change to AIGround.ini:
AILandingTargetTime=8 //9,10,11 will probably work too.
4 months ago
ClipperOS
https://youtu.be/2B8PPU7vyPw?si=CS4TiXnvGk-Va7VR
4 months ago
ClipperOS
it's a Top 5 mod in my book
5 months ago
efsenable
Both options get the job done, however do NOT you both at the same time!
(1) If using FSLTL to control arrival spacing, set the following to ZERO in AIFlow.ini:
AIArrivalSpacing=0
AITerminalAreaMinSpeed=0
AITerminalAreaMaxSpeed=0
AIBadApproachFilter=0
Note, Forced Landings should still be OK, however FSLTL spacing will be compromised slightly.
(2) if using AIFlow for arrival spacing, then turn off the arrival spacing option in FSLTL in the configuration/status window that pops up after FSLTL is started. NO changes to the AIFlow.ini file are required.
5 months ago
ClipperOS
As I haven't altered any configuration files, you might want to look into that. (Or wait until after the upcoming sim update anyway.)
In any case: thanks for the great work!
5 months ago
5 months ago
peacemaker0079
peacemaker0079