Hello, we are unable to reproduce the issue. Could you please provide more info on how to reproduce it? Is it Singleplayer / multiplayer / modded / unmodded version of the game? Thank you.

Multiplayer, unmodded and through a script e.g

			_wp = trnspGrp addwaypoint [ getPosATL hpad, 0 ];
			_wp setwaypointtype "TR UNLOAD";
			_wp setWaypointBehaviour "AWARE";
			_wp setWaypointCombatMode "BLUE";
			_wp setWaypointCompletionRadius 5;
			_wp setWaypointTimeout [ 1,1,1 ];
			_wp setWaypointSpeed "FULL";
			_wp setWaypointStatements [ "true", "this land ""GETOUT"";tobase=true;"];

The Heli is created further than hpad position. Heli reaches the hpad position area and then hovers high for approx. 2min before hovering low for units to getout and tobase to turn true. the variable tobase=false: prior to this script execution

I have tried originally without the timeout just in case a default delay has snuck up on us but it did not make any difference with the timeout or not

The reason I noticed it is because this same exact code has been working perfectly for months. I have been following the dev branch updates on a daily bases and did not notice any changes that would relate to that. The closest that I could spot was maybe the AI changes in awareness. However, I run the script in a non-threat environment also with no change on the 1.48 sec delay. When the "setWaypointStatements" is commented out the Heli moves without delay.

I have discovered something.
When I set the "_wp setWaypointCompletionRadius 5;" to 0 and the heli is over land, everything works fine, as before.

If heli is over water sometime the setWaypointStatements execute fine and sometimes not, either I set the completionRadius to 0 or leave it at 5.

So, I am guessing that the problem is not on the setWaypointStatments but how the AI reads that it reached its destination?

This issue seems to have been resolved lately. Cannot reproduce this problem anymore. Running latest Dev ver. 1.51.xxxxx