WytchCrypt

Ya, that's the conclusion I came to when I realized the Su-33 had no clickabledata.lua :(

I do it both when I fly the Hornet and the Su33. It's a great way to initialize my aircraft to all the settings I want to begin a mission with (interior lights on high, exterior lights on, etc). In the Hornet I even use it to press the LDDI & RDDI buttons to setup waypoint mode on the left and radar mode on the right etc. Once I configure all my startup commands I set up template missions for the Caucasus, Nevada & Normandy then build my regular missions on top of them. Discovering the command ID for a given option really isn't that hard...you just change line 4 of the \Program Files\Eagle Dynamics\DCS World\MissionEditor\MissionEditor.lua file to true. Then start DCS and open the options->controls screen for your specific aircraft. Hover your mouse over any command and the popup tooltip will give you the command id... Anyway, here's a thread that explains how to make it happen :smilewink: https://forums.eagle.ru/forum/englis...-mission-start

What I meant was the display of Message, "smoke is on" isn't displaying no matter what min and max settings I try. Did more research and found a very strange thing. For the FA-18C, the code to trigger the landing gear command is id 68 (found by enabling "options_add_command_to_tooltip" line in MissionEditor.lua and observing command in FA-18C Options->Controls screen). When I begin a mission by triggering an execution of "X: set command ( 68 )" it does in fact lower the gear. But if I try to display a message of, "hey the gear is down" by next checking the condition "X: Cockpit argument in range (68,0,0.95,"")" it doesn't display. I then referenced the Mods/aircraft/FA-18C/Cockpit/Scripts/clickabledata.lua and found it defines a code of 226 for "LDG_Gear_Control_Handle". When I change my condition to ""X: Cockpit argument in range (226,0,0.95,"")" the message displays as expected! That's great for the Hornet, but I'm still stuck on the Su-33. I'm wondering if since it doesn't have a clickable cockpit (and therefore no, "clickabledata.lua") that there's no way to examine the "X: Cockpit argument in range()" condition for any of it's cockpit settings? If I'm wrong, where is the file that defines the cockpit codes for the Su-33? I've looked everywhere examining several *.lua files but none seem to be the correct one. I have a feeling this is in fact the case and that this type of logic won't work for the Su-33 (or anything without a clickable cockpit). At this point, the question is now is there a way to popup a message based on the state of a cockpit control of the Su-33? For example, if I hit "T" to enable smoke, is there a way to popup a message?

Hi all :helpsmilie: I've been using triggers to successfully set many cockpit switches and knobs on mission entry. Works great but there's something related I can't seem to get to work. I'd like to display a message when a specific cockpit control is activated/deactivated. For example, let's say I'm flying my Su-33 and want to display a message when I toggle the wingtip smoke. The ID of toggling wingtip smoke for the Su-33 is 78. I've been trying: Trigger, "Switched Condition" Condition, "X: Cockpit argument in range (78,0,1,"") Action, "Message to All (smoke is on,10,false,0) I've been trying several variations of this but can't seem to get it to work. Would anyone out there be so kind as to give me an example of how I could achieve this? Thanks!

Agreed! Thanks for documenting your work on this topic, I was originally trying to get my flight controller to send all these commands with what I called a "Mission Start" button, but this is a much more elegant solution :thumbup: I also try to use descriptive titles for my triggers and have a simple notepad file I wrote up with details on each startup trigger and what codes it requires (actually I write up my own procedures for everything I do in DCS so if I'm away for a few months I can pick up where I left off, but that's another story). The fanciest thing I do with startup triggers is enabling the AUTO waypoint mode on my left DDI at the start of the mission. It requires a simple, "X: cockpit perform clickable action (35,3026,1,"")". Unfortunately, you can't turn it on if the plane is at a complete stop so a MISSION START trigger does nothing. To handle that case I use a SWITCHED CONDITION -> Units Speed Higher Than 50kts...when my Hornet crosses 50kts the AUTO is caged. OTOH, if the plane begins the mission in the air the SWITCHED CONDITION is ignored so a MISSION START trigger does work. I just run the MISSION START command first which works if the plane is already in the air, then follow it with a SWITCH CONDITION command which enables AUTO when taking off but is ignored if already in the air :smilewink:

Just wanted to point out that besides being able to toggle on/off switches using the MISSION START trigger and X:Set Command Action(), you can also control rotary knobs like cockpit light dimmers! For example, changing line 4 of DCS/MissionEditor/MissionEditor.lua from false to true and viewing the tooltip popups on the Options->Control screen as described by Rudel_chw earlier in the thread allowed me to find that the F18 Console Light Dimmer was cockpit id 9, button press 3010. To change this dimmer rotary knob I added a MISSION START Trigger which executes the command: X: cockpit perform clickable action (9,3010,1,"") (note the "1" means move the knob +1 increment). I figured that the command would need to be repeated many times to move the dimmer knob throughout it's range of motion. Turns out it takes about 36 increments to turn the knob from completely off to completely on so I just repeat the command 36 times. Turning one of these cockpit light dimmer knobs halfway up requires repeating the command about 18 times. I'm also using the MISSION START trigger to setup my LDDI and RDDI the way I like by finding the codes for pushing the required LDDI & RDDI PB (push buttons) and also executing them with the X: cockpit perform clickable action() command. Now I'm able to begin every mission with my F18 configured just the way I like :thumbup:

Thanks, I'm currently running the F18Smokewinder, F18MFDColourMod, FLOLS Overlay Disable and Caucasus and NTTR ICLS mods through JSGME so will disable them, run a cleanup & repair and give it a try. I'll report back if the problem occurs with my DCS log - though it is kinda cool to see the model of the ocean floor :smilewink:

So I've noticed the past couple of days a strange situation where the ocean goes missing and I see the ocean floor instead. Seeing this both from the cockpit and from F2 view...graphics settings all high including water. Very odd to see the screws on the Roosevelt spinning in mid air :smilewink:...anyone else seeing this?

It's definitely returned on all my custom skins...most concerning is it's returned on the skins I offer as user file downloads. Any idea for a fix?

Never mind...I found it. I had the "historical list of units" icon selected at the bottom of the ME :smilewink:

Hi all, I'm having a totally strange thing happen in mission editor. When I select the aircraft icon and click on the map, the aircraft properties menu on the right is titled, "Aircraft Group - 2016" and gives me a drastically reduced selection of aircraft to choose from. I have no idea what the "2016" is about or how I might have set this. It even happens when I start a completely new mission on a fresh map. I have a 2nd pc that runs DCS and I begin a session with that one and go to mission editor and there's nothing about a group # and I have access to all aircraft as expected. Anyone have any idea what is going on? I ran a cleanup and repair and it made no difference. Thanks!

Fantastic! Thanks Chuck! I'm one of the crazies who likes a printed manual so I'm going through comparing new to old and updating my Hornet binder...it's also a great way to focus on the new content :thumbup:

Hornet. I'm a Blue Angels and Naval Ops fanatic so the choice is easy :smilewink:

I did, but it's dependent on my flight controller. I'm using a CH Products Eclipse and I assigned a button that I press to start a mission. That button is programmed through the Eclipse to enter a series of keystrokes representing commands that I want to execute at the start of each mission. I like the option that Rudel_chw just explained and will also give that one a try :thumbup:

Fantastic! Can't wait to see it :thumbup:

I couldn't believe it! When I watched there were 3 downvotes and no upvotes which made no sense to me as you did a great job. Just for fun, had another look and now you have 5 upvotes and still 3 down so you're on a roll now :thumbup:

Excellent! Maybe I'm gullible or easily impressed but there were sections of your vid that looked like real-life carrier ops footage. I'm shocked you had 3 downvotes on youtube so I made sure to give your vid the first upvote :smilewink:

So the mod described at the beginning of the thread, "I've created a handful of templates for 4, 8 and 16 spawns" isn't it? Oh well :smilewink:

I read about a mod yesterday in the SC forum that might do exactly that :smilewink: Have a look at this thread about half way down the first page: https://forums.eagle.ru/showthread.php?t=275082

I want to step in line and offer my congrats to ED well! As a former software engineer, what you've accomplished is simply jaw dropping amazing :surprise: Thanks for getting this 59 year old color blind guy as close to real world carrier ops as I could ever possibly get :thumbup:

That's what I did. I like having 2 completely independent parallel installs so I can switch back and forth from OB to Stable without having to torrent necessary files each time I want to switch branches :smilewink:

Same here but I setup an OB install a couple weeks ago as I knew I'd want to run it as soon as it arrived :smilewink:

It transmits a low voltage zap of electricity directly to the person at ED responsible for uploading SC to the servers. If we all keep hitting F5 it might get us SC a few hours earlier :smartass:

14 yrs as a software engineer and I wouldn't even know where to begin. To say SC is a major technical accomplishment is a huge understatement. Hats off to the codebangers at ED :worthy:

Great find...that is so cool! Looks like Christmas will be in May this year :xmas: