Apparently neither AIG or Simple Traffic are responsible for this annoying bug which has been in FS2020 since launch.
It is a problem that only Asobo can fix.
So much progress has been made (slowly) yet AI traffic cannot vacate runway at a reasonable speed forcing users to execute a go-around time after time.
According to the patch notes, No. This upcoming update is mainly to fix what was broken in SU7 (and SU5 with the colour banding), I wouldnât expect any AI fix for awhile yet perhaps SU8 if weâre lucky.
I think I might know why live traffic is so slow to vacate runways, though I donât know how (or even if) it impacts on AI traffic.
As a long-time user of Flightradar24 Iâve noticed that when an aircraft lands, the connection with it is often lost, and the plane seems to remain static on the runway (though in reality itâs long since vacated), or even disappears completely, popping up on a taxiway later.
Maybe the sim knows the plane should be moving, but itâs waiting for the data to show that.
Interesting theory but when referencing AI traffic, Iâm referring to Offline traffic, not Live traffic.
I should have been clearer. Thanks for your response.
I know what you meant and on the face of it, AI traffic shouldnât be affected by what I suggested. But in software as complex as this, who knows if theyâve applied the same algorithm to AI traffic as they did to live traffic?
Not saying Iâve got the answer, mind; itâs just an idea I had.
Well, you may be correct.
Only Asobo knowsâŠbut theyâre not telling.
This has been in the previous sims as well. It appears as though the AI traffic will land, brake as hard as possible down to taxi speed, and then continue at that speed until they get to the taxi way thats closest to their parking spot. They should be taking the first taxiway they possibly can and doing majority of their taxiing on, yâknow, the taxiwayâŠ?
Quite correct.
I believe the max taxi speed is set as part of the runway specification. It was in the fsx airport design program anyway.
If the same is true in MSFS 2020, it should be possible to change the relative parameter so that all default runways are corrected.
It needs fixing though because it screws up AI traffic and IFR approaches and landings.
I donât think they do. Thatâs why this is still broken a year and a half after launch.
Lol.
Good point well made.
I strongly suspect AI and live traffic are exactly the same, only difference is live traffic gets its flightplans from flightaware, (plus maybe heading, flightlevel and airspeed when it spawns), while the flightplans of the ai traffic are stored locally.
If i remember correctly there was an dll hack to increase taxispeed globally in fsx to max. 30kt. Would be nice if asobo would increase the taxispeed, which would probably just mean increasing that one taxispeed variable, and it would do much for now to improve the traffic situation till further improvements are implemented.
I opened a topic about this in the bugs section, in case you want to participate you may vote so it may find itself a place in the backlog 
https://forums.flightsimulator.com/t/can-we-please-force-ai-traffic-to-leave-runway-faster/487542
Thanks, went ahead and voted. It was up to 20, that should make them shake in their swivel chairs 
On a serious note, I (caution, personal opinion ahead) doubt that Asobo really cares about AI traffic to any great extent. I imagine their more of the mindset âyou can fly multiplayer online, why in the heck would anyone want to use offline ATC/Trafficâ.
Hence, as was previously said, going on two years since (pre-mature) release the AI traffic is exactly as blankâed up as it was on (pre-mature) release.
Unfortunately I agree 
To be honest, I donât really know how many go arounds I have encountered due to this problem. I donât fly online because Iâm a bit scared and I donât like when there is no ATC on the destination therefore I use the awesome addon by AIG and it works quite perfectly but this problem is something that Asobo should change. Thanks for the upvote, I hope we can get more for that and we can get a fix for this soon.
I tend to land anyway even if ATC tells me go around. I flew to RJTT and ATC gave a go around and the runway was empty. Nope my man i will drop that bird right here right now.
Thatâs probably the best idea 
But câmon this problem is there since FSX, and shouldnât be too hard to solve IMHO.
The problem is that the AI is a quite static system. It doesnât matter what weather, runway or exitâs you have the AI will always use the same landing speed, reverse thrust and brake power. After the AI has slowed down it is switching its state to âtaxiâ which results in the slow movement on the runway. Because the AI uses the same values all the time Asobo was forced to make it work on very short runwayâs. That causes problems on long runways where the exit is far away.
I donât think Asobo will create a dynamic AI so they need to do something that can work static. They could add an extra state before taxi so the AI will keep rolling at lets say 40 knots until exit.
Another thing they could do is to make every taxiway usable. At the moment the game is only using fixed exitâs for traffic. That means that the AI will pass multiple possible exitâs and stay on the runway until it reached the target. By making every taxiway usable as exit the AI would at least use the next possible taxiway and get out quicker.
Great explanation indeed!
Thatâs always what I thought. Yesterday I was plane spotting using AIG and I saw that once they land they reduced their speed to 5 knots and then increase it max 10 knots. If they moved faster Iâm sure huge portion of the problem would be gone.
I agree with everything you said.
Unfortunately, this problem really only affects those of us who fly IFR using procedures. For the VFR/scenery watchers itâs not a problem
My opinion is simply that itâs not a sufficiently important bug that Microsobo will ever fix it and, like you, I think the chances of a dynamic system are around 0%. Commercially that makes sense.
They wonât even talk about it in the dev Q&A streams despite many requests to do so.
AIG said in the forums that it is a problem that only Asobo can fix.
The choice is either to land anyway or to use the other sim and Traffic Global for serious flying, which is what I do.
A bit sad though.
As noted, there is an open Bugs report for part of this phenomenon. And the 1.12.18.0 was a targeted release to address specific defects which do not include AI Traffic behavior.
https://forums.flightsimulator.com/t/can-we-please-force-ai-traffic-to-leave-runway-faster/487542
Feel free to search for a matching one for Go Arounds in #bugs-and-issues but I couldnât find one. So someone may need to open it.