Wrecking Crew

Thank you, Flagrum, That looks to be the issue!

F/A-18C Radio 1 Preset 1 Paste Problem I have a list of F/A-18C radio presets that I paste into the 'mission' file (for Persian Gulf missions, and includes Minhad and Fujairah frequencies 121.8 & 124.6). The problem is that verifying these frequencies after pasting shows the Radio 1 Channel 1 still with value '305' instead of '380' that was pasted in. I load the same frequencies into Radio 2, and the Radio 2 Channel 1 has no problem - it accepts the pasted in '380'. Here is my preset list that I paste into the 'mission' file for F/A-18Cs - ["Radio"] = { [1] = { ["channels"] = { [1] = 380, [2] = 390, [4] = 280, [8] = 124.6, [16] = 261, [17] = 267, [9] = 255, [18] = 251, [5] = 296, [10] = 262, [20] = 266, [11] = 259, [3] = 277, [6] = 300, [12] = 268, [13] = 269, [7] = 121.8, [14] = 260, [19] = 253, [15] = 263, }, -- end of ["channels"] }, -- end of [1] [2] = { ["channels"] = { [1] = 380, [2] = 390, [4] = 280, [8] = 124.6, [16] = 261, [17] = 267, [9] = 255, [18] = 251, [5] = 296, [10] = 262, [20] = 266, [11] = 259, [3] = 277, [6] = 300, [12] = 268, [13] = 269, [7] = 121.8, [14] = 260, [19] = 253, [15] = 263, }, -- end of ["channels"] }, -- end of [2] }, -- end of ["Radio"]

I tested Slmod on Hollo Pointe on the dedicated server and it worked fine to show -admin commands and to list the available missions with -admin load. No problems as of yet.

I uploaded four updated missions with filename changes and deleted the older missions. Started the dedicated server and the old mission names were still in the list. I clicked to Run one of the deleted missions to see what would happen and it said "Loading" for a while before I killed it.

Sir Abu Nuayr Airstrip Problem Tu-22Ms land there when low on fuel. This airstrip is too short for these bombers. The bombers run off the end and explode if viewing in F2. If viewing in F10 the bomber icon will show as moving on the ground after landing but well past the end of the airstrip, then the crew ejects. It seems like the airstrip is presenting itself to the AI as being longer than its 2200' length.

Thanks! It was set to Russian.

My Gooogle Chrome keeps seeing Eagle Forums pages in Russian and wants to translate. Any way to stop this? I only want to see English. Спасибо

Iranian F-4E will not orbit WP1 unless ROE = Return Fire at WP0 There are several Iran F-4E groups in the attached mission. ALL Red attacking aircraft are supposed to hold at WP 1 for a circular orbit. The Iran F-4Es do not orbit at WP1 as directed - see groups Red AGrp62, AGrp621 and Red AGrp64. But if an Advanced Waypoint Action ROE = Return Fire is added to WP0 then the F-4Es will orbit at WP1! The aircraft should go into the orbit at WP1 regardless of the presence or not of ROE = Return Fire at WP0. Red Sky 254P0i.miz

This is the latest 2.5.4 Open Beta release. When I go to Fly from the Mission Editor, sometimes not all the aircraft are present. For instance, in the attached mission there are four aircraft groups of Su-24s in the lower left to attack the Blue carrier group. Sometimes not all four Su-s4s are present at the mission start. There is no apparent reason for the aircraft to be missing. This is very frustrating. Other aircraft will also go missing. There are no Late Activations, no delayed time for their Start, all a/c are in the air at mission start. Anyone else seeing these issues? Red Sky 254P0h.miz

Armor Sinks Into Bridge In Caucasus This is on a bridge west of Beslan - per the Status Bar - LOC: 43°16'00"N 44°16'11"E. The vehicles get stuck. The Combined Arms mission cannot continue.

ME Text Editing, Ext. ASCII 248 Incorrect The Extended ACSII 248 character should be the symbol for degree - ° In the mission editor it is a Phi-like character - like Ext Acsii 237 - φ See the screenshot. Happens in the Briefing panel and in event action Message To All.

With Mist - detect any Blue Plane in a zone - is this what you are looking for? mist.flagFunc.units_in_zones{ units = {'[blue][plane]'}, zones = {'01 Sukhumi Zone'}, flag = 90156, toggle = true, }

This is the result. Thank you Wes for the help to add the Player Name & Callsign to the code. And thank you Grimes, for always being there with answers. -- new, detect Client Takeoff with names, etc... do local function detectClientTakeoff(event) local function contains(tbl, val) for _,v in ipairs(tbl) do if v == val then return true end end return false end if(event.id == world.event.S_EVENT_TAKEOFF and event.initiator) then local airborneUnitName = event.initiator:getName() [color="SeaGreen"] local airbornePlayerName = event.initiator:getPlayerName() --Added Variable to store PlayerName. Note: This is the account name, not the MP Nickname. local callsign = event.initiator:getCallsign() --Added Variable to store the Callsign. Note: The dash for "1-1" isn't in this function. local airborneCallsign = string.sub(callsign, 1, string.len(callsign)-2) .. ' ' .. string.sub(callsign, string.len(callsign)-1, string.len(callsign)-1) .. '-' .. string.sub(callsign, string.len(callsign)) --Modified the above line to add the space and dash back with string manipulation. Dodge11 -> Dodge 1-1[/color] if(contains(aircraftClientRedNames, airborneUnitName)) then trigger.action.setUserFlag(10008, true) trigger.action.outText('Red pilot ' .. airbornePlayerName .. ', callsign: ' .. airborneCallsign .. ' just tookoff in ' .. airborneUnitName .. '!', 5) --Modified the above line to include the new variable, and reformmatted it to something quicker to read. end if(contains(aircraftClientBlueNames, airborneUnitName)) then trigger.action.setUserFlag(50008, true) trigger.action.outText('Blue pilot ' .. airbornePlayerName .. ', callsign: ' .. airborneCallsign .. ' just tookoff in ' .. airborneUnitName .. '!', 5) --Modified the above line to include the new variable, and reformmatted it to something quicker to read. end end end mist.addEventHandler(detectClientTakeoff) end This returns like: Blue pilot Wrecking Crew, callsign: Enfield 1-1 just tookoff in F-15C 01. Flag 5008 is set True and triggers mission activity to begin. This is for multiplayer missions so that a mission can advance in time until a client shows up and takes off. All of the activity that I want to have happen when clients are in the mission are delayed, but the time of day will advance normally, without the mission being paused.

That's an interesting solution, Hardcard. If I can grab a height/altitude value when any Blue plane is in a cylinder zone then it could work in Mist script. What I did was put a spherical (Mist) zone and a cylinder zone in the same spot. The spherical zone controls the height while the cylinder sets the radius from center. The spherical zone, in this case, has to be much larger than it would need to be if I could place the center of it at the desired altitude.

Yes an altitude setting would be a nice feature to use with a spherical zone. https://forums.eagle.ru/showthread.php?t=228642

The solution needs to be for any Blue Plane.

I'm getting CTDs since yesterday whilst doing mission editing in the Persian Gulf. Attached is the latest DCS log. Logs Wrecking Crew 20190102T1645.zip

Thank you Wrench, That is a good technique. My events are based upon a client takeoff event. It is really quite specific in this case to the particular client who takes off. In any case, I really do not know how to join these two attributes to the uName I have :-) I've had my head stuck in some other code recently, but will get to adding these Client Name & Callsign values in soon.

I'm having ME crash problems, too, while working on an F/A-18C mission in the Persian Gulf. The game will randomly exit to the desktop. Attached are the logs from the latest. Logs WreckingCrew 20190102.zip

Can a Spherical Zone have an altitude assigned to it? For instance, I want this small-diameter (~70 feet) spherical zone to be about 100 feet off the ground. I am using the zone to detect an aircraft flying through it. Is there a possible Mist solution? I'd like to use something like this - mist.flagFunc.units_in_zones{ units = {'[blue][plane]'}, zones = {'30 Keyhole Zone'}, flag = 93056, zone_type = 'sphere', [color="SeaGreen"]zone_altitude = 100,[/color] interval = .02, } Somehow the ground height is known. From my experience a spherical zone is centered at the 'x' and 'y' coordinates on the ground with half below and half above. The .miz file code for this zone is - [13] = { ["y"] = -114081.72458564, ["radius"] = 23.7744, ["zoneId"] = 253, ["x"] = -114237.40133295, ["color"] = { [1] = 1, [2] = 1, [3] = 0, [4] = 0.14901960784314, }, -- end of ["color"] ["properties"] = { }, -- end of ["properties"] ["hidden"] = false, ["name"] = "30 Keyhole Zone", }, -- end of [13] Is there a Height property or some other attribute that can be assigned in order to get a spherical zone completely above the ground?

This ^^^ script has been working well. The text output contains the client Pilot Name, like "F-15C 01". This value is assigned in the Mission Editor for the Unit within its Airplane Group - see the green arrow in the screenshot. The complete code is also attached. I need a little bit more help with this. I want to include two more values in the text output, but I don't see these values in the S_EVENT_TAKEOFF data or in the mist.DBs.humansByName table. The values are: The Client's handle, like "Wrecking Crew". The Callsign, like "Dodge 1-1" in the screenshot at the blue arrow. The result would be in the text out, something like this: trigger.action.outText('Blue Client ' ..clientHandle.. ' in ' .. airborneUnitName .. ', Callsign ' ..unitCallsign.. ' just tookoff!', 5) And would look like: Blue Client Wrecking Crew in F-15C 01, Callsign Dodge 1-1 just tookoff! My questions: Where do I get "Wrecking Crew" and "Dodge 1-1"? And how to link those to what I know which is the "F-15C 01" unitName? Blue Sky Scripts.lua

ME Unit of Measure for Zone Radius The values for Zone Radius should be the same in both fields, regardless of the measurement system. See the screenshot red arrows.

I heard that suggestion before :-) The values should be the same regardless of the measurement system.

ME Unit of Measure in UNITS SPEED LOWER THAN The Arguments include SPEED in 'kts'. In the screenshot it is set to 2 - see the red arrows. In the Conditions panel the value is shown as 1.02777..

ME Event Action MESSAGE...: Make a Comment by setting Seconds = 0 Enable a "Comment" capability in the Mission Editor Events simply by setting the Seconds to Zero for any Action of MESSAGE...