How to prevent unrealistic AI behaviors at busy airports?

[Dirk98 354]

6 minutes ago, fs1 said:

I am looking for testers for my ATC Application, to test this new re-worked traffic conflict algorithm. So anyone interested please PM me with Skype/email details. Thanks!

Is it a stand-alone separation tool for AI Traffic or does it need the other ones installed as well, like those from here: 

Or will they benefit your tool, and does it work on a client PC like those that I've mentioned?

Thanks!

 

[fs1 295]

3 hours ago, Dirk98 said:

Is it a stand-alone separation tool for AI Traffic or does it need the other ones installed as well, like those from here: 

Or will they benefit your tool, and does it work on a client PC like those that I've mentioned?

Thanks!

 

It is a standalone tool. Regarding interaction with other applications, I am in contact with Roland and I sent him some code to test as there are some synergies.

[JoeFackel 760]

Only tested an hour, but seeing planes taking off at RWY18 of EDDF and their fast entering of the RWY when the plane before is still on its T/O run brings me already tears of joy 😃

Edited July 14, 2020 by JoeFackel

[fs1 295]

14 hours ago, JoeFackel said:

Only tested an hour, but seeing planes taking off at RWY18 of EDDF and their fast entering of the RWY when the plane before is still on its T/O run brings me already tears of joy 😃

That is good to know! Thanks

[jonezy10 1]

Any update on this? I would like to know how it impacts on the arrivals logic of AI - especially at larger airports. 

[chapstick 2,757]

I'm curious as well. Tonight I spawned in at KSAN and watched the AI taxi to wrong end of the runway, as usual, and thought about this thread.

[Urmel81 189]

It depends also a lot to the ADE File.

some updated ones (mostly for v4):

https://jcai.dk/category/afcad/

 

Regards Urmel

[jonezy10 1]

Does it improve landing patterns reducing the number of go arounds?

Edited August 5, 2020 by jonezy10

[Ronaldo1978 26]

Very important to me is, keep care of your aircraft.cfg files!

Keep them simple. I even avoid special characters in all of the entries.

Look for errors and mismatches. Especially look for typical errors like this:

atc_parking_code= should be atc_parking_codes=
atc_parking_type= should be atc_parking_types=

Using capital letters for the parking codes and types is recommended. Also avoid this: Gate instead of GATE, Ramp instead of RAMP and so on.

Also avoid GATE,RAMP. This is needless. Just use GATE or RAMP.

atc_airline= entry should also be in capital letters all the way. e.g. UNITED instead of United or FLYDUBAI instead of FlyDubai

You can use Notepad++ for searching of these errors in all aircraft.cfgs.

After that, AI ground ops and approach works pretty smooth in most cases.

Edited August 5, 2020 by Ronaldo1978