King Abdullah II missed ATC runway detection for crosswind situation ? and AIs fail formation landing with winds

[western_JPN]

Testing in DCS World 2.9.3 .51704.

Two different bugs, but each are related to winds' direction or speed about King Abdullah II's AI takeoff / landing / taxi.

---

1. AIs don't takeoff (not begin to taxi from parked spots) in crosswind situation.

From any spots 01, 02, 03-06 or 07-09, 20s - 80s - 110s .... AI don't begin to taxi with crosswind (Mission Editor's "wind blows to" values are 020 or 205).

About No wind default , AIs taxi and takeoff normally.
When wind directions are against to the runway (ME's "wind blows to" values are 140 or 295) , also OK.

Sample mission files in attach zip are in those four different wind directions OK or NG.

Perhaps Muwaffaq Salti airbase has similar AI no takeoff problem with specific wind direction, but I've not tested there yet.

---

2. AIs stop taxing after formation landed with any wind directions with speed 10 m/s.

Single AI aircraft normally taxi-in the spot after landed with each wind directions for RW 13 landing or RW 31 landing.

And with No wind default (RW 31 is used), AI formation landing and taxi to the spots are OK.

Only the situation "ATC decides landing runway direction by wind" + "AI formation landing" brings AI aircrafts stop taxing on the runway.
Two mission files in attach zip named "twotwo" show this bug.
When you change numbers of the formations into 1, they don't stop.

---

KingAbd2_takeoff_NGOK_winds.zip