Ciribob Posted October 14, 2015 Posted October 14, 2015 (edited) I've managed to track down a bug with setTask on a newly spawned unit which was causing an issue in some of my scripts. If you spawn a group using a script and immediately give the group a waypoint to go to using setTask, the unit will run roughly NW forever, regardless of where you told them to go. If you instead spawn a group, and then order the group to move using a separate function with a delay the group moves correctly, so its looks like an initialisation issue when the group is first created. I've attached a sample script which runs in the attached mission. It relies on Mist 4.0.55 but i've pulled out the relevant parts to show the issue. If you start the mission, and jump in the Huey, you'll get 3 radio commands to run the 3 tests. The units should move East towards the blue smoke but only tests 1 and 3 will. Tested on: DCS v1.5.0.45655 and DXDiag attached Edit: Further to this, if you set the delay on the move order to less than a second, the troops move NW and ignore the orderDxDiag.txtwp-bug.mizwptest.lua Edited October 16, 2015 by Ciribob Scripts: Complete Transport And Logistics Deployment - CTLD / CTLD Examples - Lots of example of how to use CTLD CSAR Script - Downed Pilot Rescue / Dedicated Server Script - Automatically launch DCS Multiplayer server at startup Range Scoring Script - Get scores and counts hits on targets for gunnery or bombs / SimpleSlotBlock - Multiplayer dynamic Slot Blocking Script Projects: DCS-SimpleRadio Standalone - DCS Radio Integration for All Aircraft - NO TeamSpeak Required! :) DCS-SimpleRadio Troubleshooting Post / DCS-SimpleRadio Free Support Channel on Discord
Recommended Posts