Wrecking Crew

This *might* be helpful... How to make a Follow Me Jeep -- http://forums.eagle.ru/showthread.php?t=133566 WC

Hey JohnnyQ, A couple of posts of mine in this thread link show a technique to get a unit's position and then do something with that (drop off a Stinger team). You may be able to use the position getting part of the script to place a beacon... http://forums.eagle.ru/showthread.php?t=132583 WC

Yep. Here's a post about getting them going after a Hold. http://forums.eagle.ru/showthread.php?t=140015 WC

With regular events: Use the Radio to set a flag to 1 (True). Then use that flag to do what you want... like activate a group or turn on AI, etc. WC

I keep a revision number at the end of each iteration of the script file, ie: 01, 02, 03, .. When I make a change, I increment the rev, and point the Do Script File to the new revision. This way I have all the old versions if I need them. WC

I'm not sure why you need a moving zone? Curious here,,, I had a Moving Zone in a mission and was going to attach it but it isn't used in that mission anymore. The moving zone is placed off to the side somewhere on the map. It is referenced and attached to a Unit (or Group?) to be able to detect when other units or groups enter it AFAIK. WC

I considered one of these to add axis for the F-15C Antenna and Elevation knobs. Someone said that the rotaries on them are return-to-center, so I did not go any further. Hope you get it sorted, Echo38! WC

I think it's figured out... The Flag 90177 triggered in the above script is used next in events with condition Time Since Flag 90177. These mist scripts will fire their flags to true each second as long as the condition is true, units in zones in this case. The flag fires every second and the Time Since Flag never reaches its setting. I knew this, took a bit to figure it out again... WC

Same mission, updated with above improvements. These ^^^ infantry groups capture a bridge and their presence in zone '01 Zugdidi Bridge' should set Flag 90177 in a script: mist.flagFunc.units_in_zones{ units = {'[g]BLF VGrp11 Commandos','[g]BLF VGrp12 Commandos','[g]BLF VGrp13 Commandos','[g]BLF VGrp14 Commandos','[g]BLF VGrp15 Commandos'}, zones = {'01 Zugdidi Bridge'}, flag = 90177, zone_type = 'cylinder', req_num = 6, } Any issues with this script? I'm continuing to test it... WC

Naw, don't say that. Been doing this for many years and still learning stuff. WC

The Stop Condition worked. if trigger.misc.getUserFlag(90115) == 1 then return true end WC

Thanks, will try these ^^^ WC

Attached mission has five Blue infantry groups that each go to a Hold state at WP1. These Blue infantry commandos are sposed to go (Advanced WP) Hold -x (off Hold, continue on) once a zone is cleared of Red. I've tried Task Push and Task Set but the five infantry groups do not progress forward. like: BLF VGrp11 Commandos A test Radio Item will set the Flag 90115 to 1 (True) to force this and it should work after 15 seconds or so once all the Mission Start stuff is loaded. Please look at the mission in SP -- let it start for 30 seconds and the Blue infantry will move forward to their Hold positions. The Flag 90115 should release these five infantry groups to continue on their paths but they will not advance. I'm at a loss as to why they will not go 'off hold'. A Radio Menu choice is available to set Flag 90115 to On but nothing happens... WC

FYI this is fixed with the 1.2.15 update. WC

Did you insert any scripts into your mission? You can post a link and PM me and I'll look at it later... WC

What would this code look like to get a Group patrol instead of a Unit? Different? Thanks, WC

I was thinking of adding a Radio command to show the status, too. It wouldn't be hard to do, I'll put one in this Back Of The Hand mission for showing the status, but prolly not for disabling the repeating messages. Right now the repeating status message comes on every 23 minutes, until one of the two objectives is destroyed, then the interval is every 17 minutes. I have added more flag logic to reduce the length; it was quite a block of text at first, still is... Another idea is to break that stuff up. Hmmm, it would be neat to use a text-to-voice converter and have the JSTARS send an audio message. I use broadcast messages to inform players of on-going mission success. If there are more than two objectives, I'll use Boolean logic to message that this or that objective is still left, so someone doesn't go flying off to a destroyed target. I've never thought of carrying results over to the restart. When Blue or Red wins a mission, I'll start a countdown from 15-5 minutes before the mission reloads. Messages countdown every few minutes, until 5 minutes when a message will appear each minute. These messages let everyone know the restart is coming, and to say who won (Red or Blue) and who needs to go back home to their mommies. WC

From a vehicle that you are in control of, bring up binoculars and you can pop smoke around you. I'll use that to mark my own position for the pilots above. WC

YES

As long as there are plenty of airbases to base out of I'll be fine with the 'location'. I'll prolly just continue on with two made up opponents, like the Red Democratic Republic and the Blue Liberation Front. This guy might just end up as the rouge colonel --> WC

Ah! There you are... I hope you get it fixed soon! WC

hee hee thanks, wanted to be sure it wasn't *me*, but geez spent a lot of time today. WC

The reason this has come up for me -- A AI aircraft has to get some place, but if it is destroyed then the mission is compromised. If this a/c is destroyed then an Is Dead Flag will be set to True. Consider that the AI a/c lands and taxis to its parking slot. Twenty or thirty minutes later the a/c is automatically deactivated and that triggers the a/c Is Dead flag which is incorrect. To insure that an a/c has completed its objective I will deactivate it and set a Deactivation Flag that prevents the Is Dead Flag from triggering. WC

Hmmm, maybe that will help with cleanups. Any change with Deactivated Groups are Dead? (I'm of the opinion that Deactivated should not be the same as Dead.) WC

Hi, found this new problem -- Clients get disconnected and cannot rejoin when the following script executes from a Do Script File action. The new Mist v3.5.37 did not solve the problem. What the script does: When a Huey lands then a Stinger Team is deployed ~30 seconds after landing. The script is triggered through regular events that determine when the Huey is landed. It clones a Stinger Team and places the team on the map at the location of the Huey landing. An AI Huey (HGrp11) will land at about 10:23 into the mission, or Client Hueys can be used. The script runs fine in singleplayer. In multiplayer a window pops open and closes too fast to read it and then a disconnect window appears. As a Client I could not re-join the server until the mission was stopped and restarted on the server. I used Witchcraft to execute the script locally and that works OK, except for a nil value return on getting the unitNameHelicopterPlayer at the end -- since that is a MP Player (Client) Name I did test commenting those lines out but in MP the disconnect still happens. local grpNameHelicopter = 'UH-1H 03 FARP London' local grpNameTeam = 'BLF VGrp90 Stinger' local unitNameHelicopter = Group.getByName(grpNameHelicopter):getUnit(1):getName() local basePos = mist.getLeadPos(grpNameHelicopter) local baseHeadingRad = mist.getHeading(Unit.getByName(unitNameHelicopter)) local baseHeadingDeg = baseHeadingRad * 180 / math.pi local newGroupTeam = mist.getGroupData(grpNameTeam) local newCoords = { [1] = { x = basePos.x + ((75 * math.cos(baseHeadingDeg)) - (0 * math.sin(baseHeadingDeg))), y = basePos.z + ((75 * math.sin(baseHeadingDeg)) + (0 * math.cos(baseHeadingDeg))), heading = baseHeadingDeg, }, [2] = { x = basePos.x + ((-75 * math.cos(baseHeadingDeg)) - (75 * math.sin(baseHeadingDeg))), y = basePos.z + ((-75 * math.sin(baseHeadingDeg)) + (75 * math.cos(baseHeadingDeg))), heading = baseHeadingDeg + 40, }, [3] = { x = basePos.x + ((-75 * math.cos(baseHeadingDeg)) - (-75 * math.sin(baseHeadingDeg))), y = basePos.z + ((-75 * math.sin(baseHeadingDeg)) + (-75 * math.cos(baseHeadingDeg))), heading = baseHeadingDeg - 40, } } for i = 1, #newGroupTeam.units do newGroupTeam.units[i].x = newCoords[i].x newGroupTeam.units[i].y = newCoords[i].y newGroupTeam.units[i].heading = newCoords[i].heading end newGroupTeam.clone = true mist.dynAdd(newGroupTeam) local unitNameHelicopterPlayer = Group.getByName(grpNameHelicopter):getUnit(1):getPlayerName() trigger.action.outText(unitNameHelicopterPlayer .. ' just dropped off a Stinger team!', 20) The mission is attached. This mission was working a few months ago on a downlevel DCSW version. Watch the Blue Huey HGrp11 for ~10 minutes or fly the Client Huey 03 and take off and go land it to generate the error. WC