1 hour ago, Clipper Ocean Spray said:

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

I downloaded the dotnet stuff you suggested trying. When I click AIFLOW the first time while looking at Task Manager, I see an ai.exe flash briefly and then disappear. Nothing else.

1 hour ago, Rob G said:

I downloaded the dotnet stuff you suggested trying. When I click AIFLOW the first time while looking at Task Manager, I see an ai.exe flash briefly and then disappear. Nothing else.

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.

 

 

 

Can AIFLOW and AIGOUND co-exist with FSHUD? Or even when using FSLTL too?

 

Yes with FSLTL, but there's a caution when changing separation parameters and maybe others, you'll need to read through the documentation on both.

not sure about FSHUD.

Thank you @christb 👍

Yes been watching a few bids and looks like it's tailored primarily for use with default MSFS AI.

I presently use 2 ATC solutions, FSHUD which I purchased a year ago for P3d and then started using with MSFS 2020 too, and Beyond ATC which I purchased in the full version to get early access to their AI injection.

I used FSLTL with FSHUD but just as I disable photogrammetry I can also perfectly live with default MSFS backed liveries so I am using FSHUD with traffic injected using the default MSFS models.... I want the best possible performance for my low-end rig.

But sometimes the traffic injected by FSHUD gets a bit out of control, so, I might really give AIFLOW a try...

Well, I sure do appreciate the support I have gotten regarding this issue I was having. Many thanks to Clipper Ocean Spray. It turns out that the theory that the problem was coming from Windows Security was accurate. Once I went into Windows Security settings and put the AIFLOW/AIGROUND folder into the exclusion list, then things started working as they should.

Yes sir, that's a must.