Rudel_chw

The only way I can think of, is to draw a circle or polygon that matches the trigger zone, and make it visible only to your coalition or player.
 
 

Not clickable, but the binding can be detected on a trigger, it is command 3019 of device 7. The only problem is that it is a toggle ON/OFF, so you are forced to use a Flag to remember the status of the smoke pod (active or inactive) and flip-flop the flag each time the user executes the smoke command ... it looks like this:
 

 
I'm attaching this test mission so you can try it and then adapt the technique to your own mission.
F-18C - Test Smoke (by Rudel-chw).miz

Seems that there is a small error on the trigger that checks the flight stick left movement .. try this corrected version of the mission.
Disclaimer: I'm not related to Aviodev, and I tested just the step affected, didn't test the whole mission as it has no way to skip long voiceovers ... a bad design decision in my opinion, as it discourages repeating the mission if the user was left with any doubt, as it becames tedious hearing the whole thing again.
C-101FA-Lesson-01-Start-Up-V4.miz

(1) is my preferred approach 
 
 
it works, no changes needed for dcs. More info:
 
 

I use Mods, while I wait for the new Caucasus lighting:
 

 
 
I never understood the need of some user to play the jockster everytime they see a chance ... it's rarely funny 🙄

perhaps you didn’t clear the metashaders2 and fxo folders, I always clear them whenever I change the gpu drivers or update dcs.

Anapa is a blue airport, set it to RED and then they will land.

1. MISS
3. TAC
 
dont remember where to adjust the RWR  😞
 
Edit: I've been reminded that the RAP+CME controls the  RWR volume.

You have the historic filter enabled (the clock thingy at the status bar) but your mission’s date is not on the ww2 date range. Either change the mission date or disable the filter.

Both set of missions have voiceovers, the F-5 has an odd russian-accent instructor, while the Mirage has a french accent one. Both are fairly comprehensive, but I liked that the Mirage had more of a storyline, that then continues onto the built-in campaign.
 

 

 
 

use the "SHOW HELPER GATES FOR UNIT" trigger action.

I completely understand the frustration, but I believe a great part of the problem is the incorrect "saved games" folder. Here is a batch file that can re-create the saved games folder on its original location (c:/users/your-user/saved games):
 
 
once recovered, use its location tab to point towards your current saved games, things will look the same afterwards, but the folder will now be the special folder it is, rather than a standard one. That should fix most of your dcs problems.

Hi, 
Don’t  use clickabledata.lua for that, instead use the way explained here:
 

best regards

Yes, I wish ED would expand on the Static Templates concept, to include triggers and triggers zones .. that would make it easier to setup a Template for a specific aircraft, with all the triggers needed to set the cockpit however one wants, it shouldn't be hard to implement.
 
 
The values work like this: 1 Moves the knob CW, while -1 moves it CCW. The amount of movement is small, so it is hard to notice.
 
 
You just have to repeat the COCKPIT PERFORM CLICKABLE ACTION several times (actually, a lot of times) to get a meaningful movement. See my sample mission below.
 
 
Prepare Mission works only for the A-10C and Ka-50. Seems the feature was abandoned after those two modules.
 
 
No, sorry, I have never seen an equivalent of the CLICKABLE ACTION on a Script, not sure if it is even possible.
L39 - Test RMI Set.miz

Just add wind at the different heights ... you can use time acceleration to test the effect, with Ctrl+Z, shift Z to return time to normal.

Strange, I have the same DCS version and the icon is there:
 

 

 
You could try to rename the whole /Saved games/DCs World.openbeta/ to openbeta.bak and let DCS rebuild a default settings folder, just to discard that it is not something within your current settings folder causing this.

You can use the Save Profile and Load Profile buttons of the Controls Window. On my experience this is only practical with FC3 style aircrafts, the full fidelity modules are better served by manually binding what you need, as each aircraft controls design is very different from the others.

Check your pc date/time, sometimes windows changes to summer/winter time unexpectedly 
 
https://www.digitalcombatsimulator.com/en/support/faq/authorization/#3314963
 

most likely you have the historic filter enabled (the clock icon on the status bar):
 


either disable the filter or set a mission date to 1944-45.
 

But you don't need to mess with the standard view keys, DCS provides customizable SnapViews just for that purpose, for example on this aircraft (A-29B) I have binded the snapviews as follows:
Lwin + Num 8 = HUD
Lwin + Num 2 = UFCP
Lwin + Num 4 = Left MFD
Lwin + Num 6 = Right MFD
 
It looks like this when in use:
 
 
(give it a few minutes for YT to finish the HD quality processing)

Providing accurate help is not easy with so little details about exactly what was done to your config .. but I can tell you that SnapView configuration is stored on the Snaviews.lua file located at /Saved Games/DCS World/Config/View/  ... so, of course a reinstall of DCS would not touch that location. 
 
You can always just delete the file (or rename it, if you want a backup of its current state), the next time you define a Snapview for any aircraft, DCS will re-create the file as needed (with default views of course, any view customization has to be done by the user)-

Hasta el momento, que yo sepa, no es posible 😞
 

It's easier to just open the mission from the Mission Editor, like this (don't have that Campaign yet, but the idea is the same):
 

 
This way you wont be duplicating files nor run the mission from a different folder than the designer intended. You can't make any edits to the mission, just run it.

To select the green radio, LCtrl + LWin + V
To select the red radio: LCtrl + LWin + U

Hi, For me it works as expected, this is running the mission for the 1st time:
 

 
next, I exit DCS, start it again and run the same mission again, the skin is still the same:
 

 
What may be happening is that if you are running the mission directly from the Editor, you may be changing the livery without noticing it, like this:
 

 
note that the ME resets the selected livery on the list, if I'm not careful the helo might change the livery to this italian default. This is an Editor bug that was already reported.