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