Wrecking Crew

You could use a combination of Unit In Zone and Unit's Altitude Lower Than or Higher Than, but you would need to specify each enemy unit. Yes, to answer your question. Now,,, you could use the Mist function to detect any plane in a zone and specify a spherical zone type over the airfield. Of course, it won't be flat on top. mist.flagFunc.units_in_zones{ units = {'[blue][plane]'}, zones = {'Test Zone'}, flag = 50207, zone_type = 'sphere', toggle = true, } WC

Sorry, did not open the other miz -- the w/e was focused on a new F-86F campaign build... WC

I'll take a look this w/e,,, have it dl'd WC

Removed the old Mission Start event completely. I don't see anything else that might cause an issue. If it fails to load try an Alt-Tab to see if there is a script error dialog box hiding in the background. Later! WC

give this a try.

well there are two scrip calls -- let me remove them.

Blooze, I changed the Briefing to use the Radio instead of chat. Changed the Mission Start event to Radio Adds. Added a Radio Remove for when Flag 6 goes True. Changed the top events for Mission status Action Message To All to say use the Radio instead of chat. -- I did not check the last half of all the events to see if more Messages To All needed this change. This is saved in DCS World 1.2.16. From the slmod manual -- 9.2.1- slmod.chat_cmd slmod.chat_cmd ( string cmd_text, number flag, number stopflag, string coa ) Quick Description: The function sets a flag when a specific line of text is entered as a multiplayer chat message. The function only needs to be told to run once, after which, it will continuously evaluate the chat history until either stopflag becomes true or the mission ends. Quick notes: If stopflag is not specified, then the function can never be stopped from executing its search for the chat message cmd_text (which will hardly ever be a problem). coa has allowed values of 'red', 'blue', or 'all'. If coa is not specified, it defaults to 'all'. When you want to specify coa but do not want to specify any stopflag whatsoever, a good value to use for stopflag is -1 (negative one). Examples: slmod.chat_cmd('-Axeman resume patrol', 1101, -1, 'blue') --[[After this script is first run, if anyone on blue team says "-Axeman resume patrol" in chat, the flag 1101 will be set to true.]]- WC

Give me a few minutes and I'll attach a solution. WC

Attach the example here and I will take a look. I don't do Dropbox. WC

:D

This is an excellent suggestion! WC

I clicked on the get serial number button and saw the SN yesterday, today I have a confirmation email of it. That email did go into my spam folder... WC

YIKES that's different. (In v1.2 and lower) I code a difference into missions to detect an AI a/c landing, and follow that with an event to deactivate the a/c group at 29 minutes after In Zone and Unit Speed < 1, and I set a flag to indicate that this group was Deactivated vs Dead, because a Dead a/c will have a different outcome. I get that you know how to do this, here it is for others... But I do have some missions that will time out based upon the auto-deactivation of a landed a/c and the Dead condition that results 30 minutes later, so if this is a real change those missions will need to be adjusted. WC

Many A-10C pilots do not appreciate air defense missiles in the missions. When they are included, and this goes for MANPADS as well, it is a good idea to list these Threats in the briefing. "Possibility of MANPADS at the Truck Park target." "Old SA-3 site at Red Kutaisi Airbase." The A-10C is capable of taking on these missile threats, and can engage SA-3's, -6s, -11s and -15 TORs, especially when loaded out with Mav H's in daylight. The -11 BUK is a tough one, and the -6s are fun if two A-10Cs are flying with one acting as a decoy. The SA-10 is something to stay away from but can be approached if there is terrain masking. You will certainly hear folks say the A-10's job is NOT SEAD (not realistic); but heck, it is your mission to make -- just be clear in the briefing what the objectives are and are not, so if that Kutaisi SA-3 is not an objective then the pilots can go around it. You can include SEAD flights of F/A-18s, Tornados, and artillery or ships to engage the enemy missile sites, and that can be part of the mission that must be done before the Hogs are able to move on the target. You can use the Radio F10 menu to call in these strikes, too. I've had more success at making fun missions when the objective is straightforward and can be accomplished in 1-2 hours. You have to find a 'balance' to the story of the mission in a campaign that makes it challenging but not too tough (impossible). For instance, I'm helping on a six mission campaign where the first three are against three different a/c types, and the last three are air to ground. All of these missions are fairly simple and involve two Client aircraft. There is eye candy built in with civilian aircraft and that SA-3 at Kutaisi. Good luck on your missions. Check out my sig and site for mission examples and ME resources. WC

What baltic_dragon said. Yes about the orbiting waypoint to stage the bombers. You can also use the Advanced Waypoint Actions to set up multiple, optional Bombing targets. Open any of those and then open the Condition... dialog. You can use an Is User Flag to Condition the action and that flag is set to 1 with the Radio F10 menu. I like to use five digit flags so I put this code into the Condition... 'Condition (LUA Predicate)' dialog box and check that box: if trigger.misc.getUserFlag(90115) == 1 then return true end You can use this ^^^ for Stop Condition... as well. WC

OK in MP for Red, broken for Blue, because the binding to the transport is missing. http://forums.eagle.ru/showthread.php?t=138812 WC

When all the wheels are blown off like that, you can pretty much set it down right on the parking spot, runway is not needed. :D

v1.2.16 Keep Advanced Waypoint Actions dialog box Open at Last WP Do not close the Advanced Waypoint Actions dialog box when advancing the ME WAYPNT to the last waypoint. WC

Very nice! Having done this by hand, this tool is wonderful. WC

At an early waypoint, set the ROE to Weapons Hold. Put down all the waypoints you need and at the last one set ROE to Weps Free. What is happening is the infantry are getting into a detection range of the enemy and preparing to fire. They will stay there. Setting ROE to Weps Hold will prevent the infantry from this engaging. WC

v1.2.16 The Yak-40 tail/wing number is set to RA-87999. Fix this such that the displayed number incorporates ME setting so there is a visual distinction for a visual ID on each aircraft. WC

ST -- check out my Wrecking Crew Projects site where you can download the missions. Lots of examples in them to follow; say what you want to accomplish and there might be a scenario in one that you can study. WC

Put a waypoint for the trooper at the aircraft. Use an Advanced Waypoint Action to Hold. Include a Stop Condition with a Duration for the time you want the guy to stop for. WC

Look in my mission called Erl Sis -- available on my Wrecking Crew Projects site. Look at the events that control an ambush of a Blue convoy, and the infantry firefight that ensues. There is some Immortal and some group activations to keep the battle going. WC

v1.2.16 The F-86F skin for U.S. Air Force FU-178 has a fixed tail number of '178' instead of picking up the Tail # setting in the ME. WC