Clipper Ocean Spray

Thanks! Re: MSFS ATC communication with the user aircraft, AIFlow/AIGround does not affect any ATC communications with the user aircraft. Have you tried MSFS Assistance Options -> ATC enforce flight plan ON (favor user's flight plan or world map flight settings over the current conditions)? Re: MSFS ATC communication with AI, there will be no MSFS ATC communication with AI in an AIFlow/AIGround "Forced" mode (AIFlow/AIGround is doing the vectoring, spacing, etc) except in situations where an AI was switched over from MSFS default mode to a Forced mode while an MSFS ATC instruction was pending (in which case you may hear the MSFS ATC repeating instructions to that AI for a bit).

Hi! If using for the first time, make sure to use the new, included config utility (Config_Utility_AIFlowAIGround.exe) rather than editing the .ini files manually. Check out this video playlist: Config Utility for AIFlow and AIGround Youtube Video Playlist First video is the basics. Forcing takeoff and landing runways is a more advanced topic that begins with the second video. The engine and beacon lights do not affect forced takeoff. Rather, an engine and beacons off signals to AIGround that the user aircraft is parked and AI can pass closely behind the user aircraft in a cramped parking or gate area. Starting an engine or turning beacons on signals to AIGround that the user aircraft is ready for pushback or taxi. AIGround then starts enforcing normal user-AI ground separation (if that option is enabled) for the taxi out/in including preventing AI from passing too closely behind the user's aircraft during pushback.

Looks like it might be a false positive by (probably) Windows Defender based on the additional info you provided in the message (thanks!). The Flightsim.to files are clean, you can restore from quarantine and/or exclude the folder from scanning. I've reported the false positives to Microsoft Defender, but I'm such a small-fry, I'm not sure my feedback is noted. Paying for a digital certificate is outside my price range as a freeware developer. BTW, I just updated the Config Util to ver. 1.02.1 because that system tray icon checkbox was still stuck "checked" (ugh) even the .ini file was updating correctly (keeping the system tray default OFF). Since you do NOT want to enable the tray, you don't need to re-download unless you want to. Just make sure SystemTrayActive=0 and StartMinimized=0 in both the AIFlow.ini and AIGround.ini files. Here is the Virus Total hash for latest AFlow2250_AIGround2270_ConfigUtil1021.zip (passed all scans) on Flightsim.to: a796d296e8af2e77f6016e9068e5511027b4c5e690d5357f6bed51fe58e195c7 You can search on that hash at the website and Virus Total will report the filename and that all scans were passed or you can actually scan your downloaded file and it should report the same hash and results.

Hi,please download the new version AIFlow2250_AIGround2270_ConfigUtil102. There was a bug in the older config util that prevented the user from disabling the tray option. Also, you can add this to the .ini file for both AIFlow and AIGround manually: SystemTrayActive=0 //set BEFORE starting, 0 no tray, 1 tray, 2 tray&hide console StartMinimized=0 //1 console minimized on start That should cause the output console window to start in a normal size window without being minimized and without being put into the system tray. Please let me know it that fixes the error. If not, it could be a .Net support file issue. The config util uses .Net Core 3.1, which is an older version that should be installed on most Win10 machines and later. If not however, the support files can be downloaded from an official Microsoft.com site: https://dotnet.microsoft.com/en-us/download/dotnet/3.1

Hi, it is starting to the system tray by default. Go to the tray, right click on the program icons, and select "restore console." I probably should change the default to just run minimized. Update out tomorrow with that and some other fixes. Also, I would use the config utility to configure/launch AIFlow/AIGround.

Good suggestion. Some of these airports I only know about the real word flows from Vatsim, whose controllers often simulate them. KDCA is my "local" airport. Sometimes I'll look a flight radar or the like, which will give me a basic understanding of what runways are being used for takeoffs and landings and sometimes even taxi flows.

Please give 40 seconds or below a try. The results may be satisfactory. Anyway, I am thinking about changing the default takeoff time to a higher value. The intent behind the small value was for MSFS controlled takeoffs: it helps get the AI off the runway quickly reducing the chances that a landing AI will go around. Although a short takeoff roll is not needed for forced takeoffs/landings because there are no go-arounds, I've always assumed a substantial number of users do NOT routinely use the forced takeoff/landing feature, so a default short takeoff roll would be helpful. However, the feedback on the default, short takeoff roll has been mostly negative. So I'm at the point where I'm thinking I need to heed public opinion.

Thanks!! I probably should have clearly labeled the Forced Takeoff and Landing tabs as optional. I think some users that are new to AIFlow/Ground are getting the impression from the GUI that forcing runways is required. Oh well...it is a struggle to sometime keep a broad view while programming stuff like this. 🙂

That should work! If you want to Force the takeoffs to a runway, that is in the second tab "2. Force Takeoff Rwys".

AI Takeoff Target Time down at the bottom left of your screen grab. Similar setting for landing target time in the fourth tab "4. Land." The default values are low (quick takeoffs and landings) to reduce MSFS go-arounds, but they can be increased or simply disabled at the expense of more go-arounds. If you are using Forced Takeoffs, the takeoff time can be increased substantially (e.g., 35) because go-arounds are not an issue. For Forced Landings however , be careful going past 9 seconds de-accel time because AI will start having problem vacating the runway properly.

Hmmm...should work...I'll take a look. Make sure you are seeing cull messages in the output console window. In the meantime, try a simpler setting to see if that works more as expected (leaving aside AICullMaxAIAllowedRandomSort which is a newer feature). E.g.: OptInMode=1 AICullEnable=1 AICullMaxAIAllowed=50 Regards, Roland.

Brian, Just checked KL71 with AIConv.exe and the file converted ok. Make sure you're using AIConv.exe version 1.4.11 dated 3/6/2015. Also, what is the file date of your KL71.txt file? The date I'm using is 1/6/15 (AIRAC Cycle : 1501) (navigraph). -Roland

Thanks Matias, much appreciated! I'll package it up with revision B and include instructions that the latest revision of AIConv.exe is included in the AIController main installation directory. -Roland

Thanks, a new version 1.4 with significantly more capability will be available any day now, so if you're checking the program out for the first time, it might be worth it to hold off for a few days. Regards, -Roland

Yes, the KDCA runway 19 river visual approach for AI is included in that package, as well as some other special approaches and departures associated with this airport. Latest version is 1.3B. -Roland

Hi everyone, I've just made available the latest beta version 1.3A, which now support AI jet routes and includes Matias's SID/STAR conversion utility. The program now controls the AI through all phases of flight from takeoff, SIDs, jet routes (new), STARs, final approach and landing. The old name (AISIDSTAR) gave a limiting impression of the program's capabilities. Thus, I've renamed my AI control utility from AISIDSTAR to AIController. I've started a new beta thread under the new name to avoid confusion: http://forum.avsim.net/topic/447974-ai-controller-sid-jet-route-star-and-final-approach-beta/ The old thread was very long too. Thanks everyone for your help and I hope you give a look and continue sending me excellent feedback and suggestions. The final released "old" AISIDSTAR version 1.2QR19 can be found in the avsim library under the file name: aisidstar12.zip -Roland

Abraham, The SIDs are selected based on the weighting the distance (including turn angle) from the AI to the SID entry point and from the SID exit point to the destination. So, a SID that has an entry point close and straight ahead of the AI and an exit that's "close" to the AI's destination may get selected even the the middle waypoints in the SID take the AI on a circuitous path. I would just remove some of the SIDs you don't like (de-activate). This is a problem when generating SID/STARs from nav data, sometimes to just get too many of them. You mention that you have 8 active SIDs now for that runway...I would deactivate about 4 or 5 of them (you can copy the files you don't want to used into a subfolder of the SID directory called "inactive" or the like). AICircleUntilAssignedRunway = 3000, AICirclingTimeNoRunway = 120, and AIHoldForRunwayPattern = 1 will cause AI that has exited a STAR, but not been assigned a landing runway by FSX, to begin a circular holding pattern in an attempt to eventually get a landing assignment. The circular pattern seems to help the AI's chances of getting assigned a landing runway. If you don't like the circular pattern, just remove those options and the AI will perform a downwind, base and final pattern after STAR exit. Yikes, that a huge separation distance, I would recommend =2 (the program is pretty strict about the separation distance in holdings modes 2-4 (AIholdingallowed) when the AI(s) join final, so a 5 nm separation distance will cut down landing rates dramatically. I actually think a 1 nm separation works pretty well. Yep, one video is worth a million words....oh well...but thanks for looking at it. I wish VoxATC had an option to turn off their airborne traffic (or at least the arriving VFR traffic lacking departure/destination data), but an option like that may be difficult and time-consuming to implement. -Roland

Nice, I haven't thought of that combination! Glad to see people experimenting with the options. There's several way to address the issue. You could add AIMaxSpawnDistanceFromAirport=30 to your .ini file. That will prevent any arriving AI spawned within 30 nm of the destination airport from being assigned a STAR. Also, if you're using the SIDSTARConverter program to creates STARs, make sure the "Create Short STAR" box has the number 30 or lower in it. You can also edit the STAR files yourself to achieve the same result. For example, if one STAR has five waypoints, where the entry waypoint is 40 nm out, the second waypoint is 30 nm out, etc., you can create two (or more) STAR files having the same basic STAR, but different entry points. E.g., the first STAR has the normal entry waypoint 40 nm out, the second STAR has the second waypoint as the first (entry) waypoint 30 nm out. Interesting idea, I'll look into it! One problem might be that many STAR(s) only have altitude ranges associated with the waypoint. -Roland

Bernd, AISIDSTAR uses its own configuration data and makes no permanent changes to FSX/P3D. AISIDSTAR is an external program that interfaces through the FSX simconnect and FSUIPC interfaces. If you don't run AISIDSTAR, FSX won't know it ever existed (there will be no trace of AISIDSTAR in FSX). The default AISIDSTAR.ini file only covers a few metro areas in the U.S., not the "whole North American area." Certainly, you can add SID/STAR files to cover most airports in North America, but that is something you have not done, correct? The default AI doesn't use navdata, the flights are direct. There are a lot of reasons why your AI might be missing. Have you downloaded and accidentally installed FS9 .bgl traffic files associated with North American airlines, thus disabling FSX airline traffic in North America? Did you check your recycle bin for deleted FSX files (e.g., *.bgl)? Have you installed/removed any traffic add-on packages recently? Sometimes that can cause problems, like leaving the "SimObjectPaths.X=SimObjects\Airplanes\AI Airplanes" statement out of your FSX config file. -Roland

Enzzo, can you email your custom STAR to me at my support address listed in the readme and I'll give it a look. Ahh...this is a separate issue from Matias' utility, but this is also a very good suggestion that's adds flexibility (people can still start AISIDSTAR after FSX the old way if they want to) and is easy for me to implement. Thanks for the idea (and to Onyx too). This would be especially useful to me (and others with a similar config) who run a networked laptop for Simconnect and Wideclient programs and don't mind letting AISIDSTAR "run" waiting for FSX/P3D to get loaded on the main machine (similarly to how I keep ActiveSkyNext running all the time). I think it would be useful for those running all programs on one machine as well. Good to hear, are you using the "AIImmediateForceLandAll" option? I actually have a new feature in the works...automatic jet route vectoring for ALL enroute AI (not just monitored airports) based on shortest path calculations from departure to destination. The jet route vectoring is basically working right now on my most current build, but I was thinking about adding an option where the user could enter average flight level wind information and the AI jet routes are chosen for shortest path taking into account the average winds. Do you (or anyone) think average winds is a useful option? -Roland

Enzzo, there are several options. The easiest is probably just add a single, additional exit waypoint to the STARs that generally places the AI on the side of the field that would have the left traffic pattern. That will trigger the program to execute a left pattern. Another option (more complicated but gives you more control over the pattern), add multiple custom waypoints to the STARs (with altitude restrictions) that extends the STAR into a left traffic pattern up to the endpoint of the downwind. After the AI exits this "extended" STAR at the end of the downwind, the AI will turn to base and final by themselves thus completing the left pattern. Another option, disable the traffic pattern and just have the AI directly intercept the IAF after exiting the STAR (add AITrafficPattern=0 to your .ini), in which case the AI will maintain a minimum AGL altitude (AIpatternalt in the .ini). Thank Matias, very nicely thought out utility! -Roland

Matias or Graham, Could you give the AICull feature a try and see how that works? Add AICull=2 and AICullHeight=18000 to the .ini. That should delete all airborne VFR traffic below 18000 feet near all airports monitored by AISIDSTAR. The best case result would be VoxATC detects the VFR traffic is no longer present and proceeds normally. -Roland

Yes, the AI should not have landed without clearance. Can you email me the aisidstar.ini file you're using? Maybe its a combination of different parameters causing unexpected results. Also, if you get a chance, add debugatcid1=TF-AMT to your .ini file (this is a new option I added to selectively debug specific AI aircraft). Then, zip up the aisidstar.log file and email it to my support address listed in the readme. Thanks! RC4 works fine with AISIDSTAR from personal experience. I think Pro-ATC/X and Pro Flight Emulator will work as well. Your aircraft and the AI traffic should follow the same assigned SID or STAR if both you and the AI are approach the STAR entry point from a similar position and landing on the same runway(s) covered by the STAR. However, if there are dozens and dozens of STARs active for a monitored airport in AISIDSTAR, the chances go down that you will end up on the same STAR as the bulk of the AI. One solution is deactivate excessive STAR files by moving them into a backup (inactive) directory (e.g., aidstar12/Chicago Metro Area Airports/KORD/inactive). Regarding SID(s), you're more likely to end up sharing the same SID with an AI because only a few usually correspond to a particular takeoff runway. Yes, there was some discussion of this before. If I remember correctly, departing AI work fine (when assigned SIDs at departure by AISIDSTAR). You can use AISIDSTAR for SID(s) only. As for arriving AI, the problem is VoxATC injects VFR AI for a circling approach with no departure or destination data, so AISIDSTAR doesn't control them (can't determine whether they're departing from and arriving at a monitored airport). It might be ok just to let VoxATC do its own thing regarding these arriving VFR aircraft. You could also try AISIDSTAR's AICull traffic density options (see the quick reference guide, p. 2 or the readme, p. 13), which delete AI not found to be departing from or arriving at monitored airports (i.e., the VFR VoxATC AI with no departure or destination data). However, I'm not sure what effect this would have on VoxATC (e.g., would it still think the deleted VFR AI are there?). -Roland

The latest AI monitor is expecting data (aitelemetry.txt) in a slightly different format. Make sure to replace the aimonitor.exe, aisidstar.exe and aitelemetry.txt files with the latest versions. A good approach might be to unzip the latest version into its own directory, test it to see if it the vanilla install works, then copy over your custom files/folders from your old installation. -Roland

AISIDSTAR has been uploaded to the AVSIM library and should now be available (aisidstar12.zip). Thanks everyone for your feedback and suggestions! Revised: Improved AI separation, so much so that you will have to adjust downwards the separation numbers you're used to entering. For example, AIseparationdistance=2 (nm) is now the "normal" separation number. To squeeze the AI tightly together on approach, I now recommend setting AIseparationdistance=1 (nm) in your AISIDSTAR.ini file. On the other hand, AIseparationdistance=3 (nm) now represents conservative spacing virtually eliminating all go-arounds regardless of traffic density. Note: Holding modes 2,3, or 4 must be active to see the enhanced holding (AIholdingallowed=2,3 or 4). New: If the user only wants AI with “official” FSX clearance to land, add AILandWithoutClearance = 0 to your AISIDSTAR.ini file. Background: AISIDSTAR will land any AI that fails to receive timely landing clearance provided an autogen or custom final approach file exists, however such AI must be deleted after the landing rollout because any AI that lands without clearance receives no taxi service to the gate. This new option avoids this problem. Fixed: Not establishing FSUIPC link in Prepar3D v 2.x. Various other fixes/revisions were also made. Important Revision: A registered version (4.9x or later) of Peter Dowson's FSUIPC utility is recommended to use the full functionality of AISIDSTAR. For example, the new AICull function requires FSUIPC. For networked configuration users, Peter's WideFS (ver. 6.9) is also recommended. Important New NOTAMS! ENTERING FINAL APPROACH COORDINATES. Do not use FSX when entering final approach coordinates for runway positions (e.g., touchdown, rollout) as the FSX in-game coordinate display (shift-Z) lacks the necessary precision (significant digits). Use the freeware Airport Design Editor X (or similar) instead. ENTERING RUNWAY DATA. Ensure the runway number corresponds to the FSX runway description (for whatever airport scenery you are using). Often, the latest FMS data will reference changed runway numbers that do not correspond to stock FSX runway descriptions. For STAR files, if the runways do not match, AISIDSTAR will choose the STAR based on the waypoint having the closest entry point to the AI’s current position (i.e., not based on runway data), which often is satisfactory, but not always. For Final Approach files, if the runways do not match, AISIDSTAR might choose the final approach file having the incorrect runway data. Please consult the following video documentation: Overview of What's New in Version 1.2Q: Thanks! -Roland