Using the "Execute Code Module" to import a mission SQF, a unit with a simple "1: MOVE 2: CYCLE" order will be given an extra 0: MOVE order after they hit the first move waypoint. The location of this new MOVE point is [0,0,0] and is usually unreachable which causes the patrolling unit to stop.
Description
Description
Details
Details
- Severity
- Minor
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 10 x64
- Operating System Version
- Windows 10 Home, OS Build 14393.479
- Category
- Zeus - Missions
Steps To Reproduce
Place a unit down in Zeus.
Alt+Left click some distance away to give the unit a cycling move order.
Click "Copy Mission SQF" to export this patrolling unit.
Copy the generated SQF
Delete the unit.
Click "Execute Code Module" and paste in the SQF that you exported from the copy.
Wait for the unit to hit their move order and the new 0,0,0 move order will be created.
Additional Information
Deleting the move orders and restarting the patrol cycle corrects the issue but it's a huge pain when you have multiple units all with waypoints suddenly pointing off of the map. Also, sometimes units think they can get there so they start wandering off towards 0,0,0 and will leave the AO if you don't catch them.
This is reproducible whether running the server locally or when operating Zeus on a remote server.
Here's a very basic SQF that I exported for testing (on Altis):
_newGroup = createGroup east; _newUnit = _newGroup createUnit ['rhsgref_ins_crew', [2969.61,9932.12,0.000785828], [], 0, 'CAN_COLLIDE']; _newUnit setSkill 0.5; _newUnit setRank 'PRIVATE'; _newUnit setFormDir 272.187; _newUnit setDir 272.187; _newUnit setPosWorld [2969.61,9932.12,47.754];_newGroup setFormation 'WEDGE'; _newGroup setCombatMode 'YELLOW'; _newGroup setBehaviour 'AWARE'; _newGroup setSpeedMode 'NORMAL';_newWaypoint = _newGroup addWaypoint [[2717.98,9957.3,4.57764e-005], 0]; _newWaypoint setWaypointType 'MOVE'; _newWaypoint = _newGroup addWaypoint [[3000.75,9915.76,0], 0]; _newWaypoint setWaypointType 'CYCLE';