Page MenuHomeFeedback Tracker

setWaypointStatements issue
Need More Info, WishlistPublic


Dev Branch update 1.47.131174, scripted "setwaypointStatements" take around 2 minutes to execute.
This has not been an issue in prior updates.
Scripted setTriggerStatements is working properly.


Legacy ID

Event Timeline

KDN set Category to Scripting.Jun 13 2015, 2:39 PM
KDN set Reproducibility to Always.
KDN set Severity to None.
KDN set Resolution to Open.
KDN set Legacy ID to 1477448612.May 8 2016, 12:13 PM
Adam added a comment.Jun 15 2015, 12:27 PM

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.

KDN added a subscriber: KDN.May 8 2016, 12:13 PM
KDN added a comment.Jun 15 2015, 4:02 PM

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

KDN added a comment.Jun 16 2015, 12:39 PM

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.

KDN added a comment.Jun 17 2015, 12:19 AM

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?

KDN added a comment.Sep 2 2015, 12:44 AM

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