Fantastic program thanks very much. I’m still playing around with it, some aircraft get to about 50-100 feet then get cold feet and go-around. 

After a few hours of running, planes are circling like 4-5nm near the airport, runway got locked by a landing cleared AI circling around somewhere with go arounds and no take offs taking place. Suggest not taking control of AI closer than ~10nm from landing runway and placing holding spot a minimum of that distance away to avoid landing clearance.

Program failed to detect ini when autostarted from p3d xml method, had to move the ini to sim root folder to be detected if that is normal?

Also does the program deal with AI destined for different runways distinctly i.e. ignore their separation? As the AI destination runway identifier is not mentioned only airport icao is in the information messages.

Edited May 2, 20206 yr by him225

Thanks for the utility. On may way to test AI separation.

Edited May 4, 20206 yr by DJJose

Roland @Clipper Ocean Spray,

Thank you very much for those tools. After trying them out  in the past weeks I have to say that they work very nicely and that they are a real enhancement for AI. Two ideas/observations for AI Ground that I came up with during my tests:

1) Could the control surface check be made optional via the ini? Right now, some models like the FSPXAI's will deploy their reversers during the check.
2) Could AI Ground also improve the pushback phase and extend the push to the taxiway. This would suppress the awful 180° turn of the AI aircraft.

This is like flying in real world (as much as possible)... I set these two programs within my .bat file for starting HiFi weather programs and P3D. Most interesting thing was (after reading that it did not matter if your programs were started before or after P3D) finding how in depth your programming is. In my .bat file I started you progs before P3d, and in the dos boxes I could follow the procession of your's, continuing to try to find the P3D program. It never gave up. Of course it couldn't find P3D because it hadn't set itself up yet. Finally P3D was established and your progs hooked in. I'll re-write my .bat and start your's after P3D has established itself in memory. No since in AIGround and AIFLow having to work so hard. Thanks for having the gumption to continue to work on these two programs!

Thank you so much for developing these programs...and for free!  They are a huge improvement.  I won't fly into a busy airport without them.  Thanks again

PS.  love the movement effect on landing aircraft.  Much more realistic

Edited May 5, 20206 yr by pads103

Sorry guys, been sort of slow getting out the updates.  I'm "unofficially" providing a link to the latest revisions, which should provide a fix to the go-around issue in heavy approach traffic.

I haven't tested as much as I want to yet (I usually do a lot of routine flights with no code changes before I upload to the lib), but I'm providing them to get the go-around fix out there.

If you download and something doesn't work, please let me know here or via my email contact (readme.pdf) because these files are essentially beta.  Thanks!

https://www.mediafire.com/file/rqrgmvnhy7nv4up/AIFlow_v110.zip/file

https://www.mediafire.com/file/zutcuqua4sqhnvj/AIGround_v110.zip/file

 

The versions linked above (1.10) also have some new features described in the readme.

thanks!!

Amazing job! Thanks. I've been AI spotting waiting for AS on V5.

Observation. Same 2 airplane have been put on hold for the same reason. In this case, if you knew that #2127 was but on hold because of #461, then don't put #461 on hold too

*********************************************************************************************************************
JERSEY Flight 2127 (G-FLBA) projected to be too close to SPEED BIRD Flight 461 (G-VIIC).
AI will be placed into temporary circling hold at altitude = 14000 ft.
Approaching airport EGLL.
*********************************************************************************************************************

/ User's aircraft is nearest EGLL.  ||Temporarily squawk 1234 to disable landings if departing a busy runway.  ||

*********************************************************************************************************************
SPEED BIRD Flight 461 (G-VIIC) projected to be too close to JERSEY Flight 2127 (G-FLBA).
AI will be placed into temporary circling hold at altitude = 20000 ft.
Approaching airport EGLL.
*********************************************************************************************************************

9 hours ago, jimcarrel said:

This is like flying in real world (as much as possible)... I set these two programs within my .bat file for starting HiFi weather programs and P3D. Most interesting thing was (after reading that it did not matter if your programs were started before or after P3D) finding how in depth your programming is. In my .bat file I started you progs before P3d, and in the dos boxes I could follow the procession of your's, continuing to try to find the P3D program. It never gave up. Of course it couldn't find P3D because it hadn't set itself up yet. Finally P3D was established and your progs hooked in. I'll re-write my .bat and start your's after P3D has established itself in memory. No since in AIGround and AIFLow having to work so hard. Thanks for having the gumption to continue to work on these two programs!

I've added them to my exe.xml file by adding the lines in bold below.

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>exe.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>as_btstrp_config_manager</Name>
    <Disabled>False</Disabled>
    <Path>as_srv\as_btstrp_config_manager.exe</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>AIGround</Name>
    <Disabled>False</Disabled>
    <Path>E:\P3D\AIGround\AIGround.exe</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>AIFlow</Name>
    <Disabled>False</Disabled>
    <Path>E:\P3D\AIFlow\AIFlow.exe</Path>
  </Launch.Addon>
</SimBase.Document>

MDFlier, do the programs find their .ini files that way? In my case, they don't.

On 5/5/2020 at 5:45 AM, Wolkenschreck said:

1) Could the control surface check be made optional via the ini? Right now, some models like the FSPXAI's will deploy their reversers during the check.
2) Could AI Ground also improve the pushback phase and extend the push to the taxiway. This would suppress the awful 180° turn of the AI aircraft.

Re: 1, that's in the latest version (110) that I linked to in the thread.  Re: 2, to do that right I would need to know the taxi nodes and links.  My prior AIController read all that data from the bgl(s), but it was a lot more complicated program and I wasn't sure it was worth all the extra fuss.  Maybe there is a way I can do it using a bare bones approach.  What would you think if the AI pushed back to its normal point, then sort of did a tear drop 180 so that the AI ended up in approx. the same location, but pointed out to the apron?

On 5/5/2020 at 7:47 PM, vincentrouleau said:

Observation. Same 2 airplane have been put on hold for the same reason. In this case, if you knew that #2127 was but on hold because of #461, then don't put #461 on hold too

*********************************************************************************************************************
JERSEY Flight 2127 (G-FLBA) projected to be too close to SPEED BIRD Flight 461 (G-VIIC).
AI will be placed into temporary circling hold at altitude = 14000 ft.
Approaching airport EGLL.
*********************************************************************************************************************

/ User's aircraft is nearest EGLL.  ||Temporarily squawk 1234 to disable landings if departing a busy runway.  ||

*********************************************************************************************************************
SPEED BIRD Flight 461 (G-VIIC) projected to be too close to JERSEY Flight 2127 (G-FLBA).
AI will be placed into temporary circling hold at altitude = 20000 ft.
Approaching airport EGLL.
*********************************************************************************************************************

I thought I noticed a tango during earlier development, but I couldn't reproduce it when I went back to double check.  Thanks for confirming it.  I've spent a day trying to reproduce it at EGLL with insane traffic densities, but I just haven't be able to.

Here's a link to a fix I'm pretty sure will work, unfortunately as mentioned, I can't reproduce the situation the new code is designed to fix. 😉  Please give it a try, maybe you'll have better luck.  One situation the new code won't handle:  the first AI causes a second AI to hold, and then a significant amount of time later the second AI causes the first AI to hold (rationale: good chance there will be a new traffic situation at that point instead of the earlier tango).

https://www.mediafire.com/file/n5gc9pwpug70fk2/AIFlow_v110HF1.zip/file

On 5/6/2020 at 2:04 AM, d.tsakiris said:

MDFlier, do the programs find their .ini files that way? In my case, they don't.

MDFlier and Dimitrios, thanks for the suggestions, very good point, here's a link to a fix:

https://www.mediafire.com/file/63z47i50t4mdsh9/AIGround_v110HF1.zip/file