Sedlo

not sure, but I have some ideas, though.

@Reflected, the guy behind Zone 5, has a new F-14 campaign coming out very soon!

I would like to see some sort of toggle for enabling ATC for a particular ship, too. In the meantime: @emibat, if it's single player, or coop PVE, set the ships to the opposite coalition, that will eliminate them from the list. Otherwise, consider setting the ships as static objects instead of units. They won't move, but it will give you some eye candy.

Keep in mind the parameters get a bit screwed up sometimes if there are more than one digit to the right of the decimal. Best to keep it the decimal to 1/10th.

@Mistermannthose values would be for the clickable actions. So if you wanted to force the parking brake out (without pilot input), you'd go device ID 5, command 3005, value 1 (or -1, as the case may be).

-edit.. Rudel beat me to it. You can also find some info in this file: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\mainpanel_init.lua

I’m away from my computer right now, but you might consider looking at the cockpit argument in range condition. If no one chimes in before I get home, I will walk you through it in about six hours

@Nealius, although the frequency is listed as red, it will still work in game. Sounds like a UI error in the mission editor. See attached mission, tanker will be on 135.5 and will respond to the player. test refueling vhf.miz

Hey, @ghostsp3ctrecool! Can you share what you've come up with, I'm always interested in seeing how this might be done.

Hey @ghostsp3ctre! Are the clients set to invulnerable? I had experienced a similar thing with the EVENT_HIT handler. might be related? I am just re-reading what I wrote. Obviously, if they’re set to invulnerable, they won’t get killed. Stupid me

Hello! I would like to put a request in to have the list of cockpit parameters include the MIDS radios. Just like the regular communications frequency parameters, including MIDS will open up a load of potential mission editor goodness. Thank you! Sedlo

Hello! I would like to put a request in to have the list of cockpit parameters include the MIDS radios. Just like the regular communications frequency parameters, including MIDS will open up a load of potential mission editor goodness. Thank you! Sedlo

Hey @luza! Thanks for the kind words, I'm glad you enjoyed the campaign. I do have a 13 mission Hornet campaign in the works for the Persian Gulf map and the Supercarrier. I also have a couple of other Hornet missions in the user files section if you're interested.

Creech, too. Track and screenshots attached. creech runway markings.trk

They can be different, but many use COMM1_FREQ or COMM2_FREQ, such as the Hornet, Harrier and Viper.

@applepiefrost The parameter for the F-16 VHF radio is COMM2_FREQ UHF is COMM1_FREQ

In-flight the slash key will not work to bring up the radio menu. You have to use the key binds for COMM1 or COMM2 transmit. I am mobile right now, so I don’t remember exactly what it is, but I think it is either write out/or write control/. Have a look in your control set up for the correct key binds in your situation

Bomb in zone Condition is looked at once per second, and your trigger zone seems to be fairly small. i think what may be happening is the bomb is zipping through the zone so fast, and detonating, that the once per second trigger zone isn’t catching it. Try it with a larger zone.

@JovenTrollthe exact same thing happened to me... Doing a repair didn't help, but I turned the PC completely off, then on, then they seemed to work again. Not sure what happened, or what I did to fix it.

Glad it worked out!

Hey @Peter33! OK, first all, don't be too hesitant about scripts, they're complex to see at first glance, but after some practice, working with them is not so bad. Lots of people here on the forums can help, too. What you'll need to do is incorporate a X: Cockpit Indication Text Equal To in your trigger. Finding the proper element name and value will require you to use DCS BIOS (and a bit of scripting) to find out the values that you need for a given task. I've created a test mission that you can go into and see how it's put into use. Situation is you are flying towards an SA-3. Once the radar spikes you, it will set a flag (10). Two seconds after the spike, you'll get a radio message from "your wingman" saying you've been spiked. One the SA-3 is fired, you'll then get another radio message. SA3 TEST.miz

Which aircraft are you flying and which threat/spike do you want to happen for your trigger?

If you want to make it only appear for a specific unit killing another specific unit, you can do this: Handler = {} function Handler:onEvent(event) if event.id == world.event.S_EVENT_KILL and event.initiator == Unit.getByName('GoodGuyUnitName') and event.target == Unit.getByName('BadGuyUnitName') then trigger.action.outText(event.initiator:getName().." killed "..event.target:getName(), 2) end end world.addEventHandler(Handler) No MIST required, but you have to edit the GoodGuyUnitName and BadGuyUnitName to the specific UNIT name of the units you want to reference.

It's not technically a second hand, but a stopwatch like function. But you can make it work like one. You kind of have to "uncage" it.... There is a hidden button just above the dial under the dashboard. Wait until the sim time gets to the top of the minute and then press it.