Oznerol256 Posted April 29, 2013 Posted April 29, 2013 (edited) I have found a problem that causes AI to ignore waypoints. Look at the attached image. The blue Stryker unit should drive to the airport and then turn and drive to the city right? Well, it usually does. However, i have added a hold condition to WP1. The Stryker will hold at WP1 until Flag 1 gets true, which is done using a Radio F10 menu option. When i wait until the Stryker stops at WP1 before i set the Flag, the Stryker will follow the complete route. However, when i set the Flag before the Stryker reaches the WP, the unit will turn at WP1 and will drive to WP3 directly. It just skips WP2. I also have done tests with advanced waypoint action. My tests show that the turning waypoint's (WP2 in the example without scripts) advanced actions a are executed, while the advanced waypoint actions of other skipped waypoints arent. This can be seen by the tracks with scripts. The zip contains the two missions (with and without scripts) and two tracks for each mission, one with waiting for the Stryker to stop (the CORRECT ones) and one without (the WRONG ones). I would like to read any comments on this bug.AI WP bug tracks and missions.zip Edited April 29, 2013 by Oznerol256 [sIGPIC][/sIGPIC]
Grimes Posted April 29, 2013 Posted April 29, 2013 Reproduced in the beta and reported. Thank you for the report. The right man in the wrong place makes all the difference in the world. Current Projects: Grayflag Server, Scripting Wiki Useful Links: Mission Scripting Tools MIST-(GitHub) MIST-(Thread) SLMOD, Wiki wishlist, Mission Editing Wiki!, Mission Building Forum
Oznerol256 Posted April 30, 2013 Author Posted April 30, 2013 :( isnt solved for 1.2.4. Well, i didnt really expect that this would be solved in a matter of hours. I hope this is going to be solved soon because it actually prevents my mission from working. Imagine a convoy trying to pick up a downed pilot. This convoy simply turns back home instead of rescuing the pilot :( [sIGPIC][/sIGPIC]
Grimes Posted May 1, 2013 Posted May 1, 2013 The bug occurs when stop conditions are true before they are evaluated. There are 3 known workarounds: 1. Add a new WP after WP2. They need to be a decent distance away from each other as close WPs are basically ignored. 2. Set a flag upon the arrival of WP2 followed by the hold command. Using triggers do a time since flag is 1 to set another flag. Use the 2nd flag on the stop condition. 3. Dynamically give them a new mission task via scripting. The right man in the wrong place makes all the difference in the world. Current Projects: Grayflag Server, Scripting Wiki Useful Links: Mission Scripting Tools MIST-(GitHub) MIST-(Thread) SLMOD, Wiki wishlist, Mission Editing Wiki!, Mission Building Forum
Recommended Posts