Qazplm

I don't understand either. It looks as if the function is set to trigger, once, continuously, with condition changes,...... Is it this function? I'm looking for a function that can determine the position after the player clicks the switch through the task script. Can it do it?

Thank you. Is this function a function of DCS? Or is it from MIST or MOOSE?

Hi, hello! Where is the function AddFileTriggerTempo obtained? Can it be used directly in the task script?

Hi, guys! Excuse me. Does anyone know how to monitor the clicking actions of players in the cockpit? Use scripts instead of in the task editor. That is to say, every time a player clicks a switch or a button, an action will be triggered. Or rather, does DCS have a function that can monitor the click actions of users

文 I can use scripts to read and set cockpit parameters, but I'm not familiar with programming. The scripts I wrote can only determine the current status of the switches and will not be written to make judgments after the player pulls the switches

Thank you. I understand this. What I want to say is how to implement this function with a script. Each time the player pulls the switch, a message is displayed.

I think every time the player pulls down the switch, there will be a message showing the current position of the switch. If I use scripts instead of triggers, what should I do? Can anyone help me? thanks

Hi, guys. I'm not familiar with the script and have a problem. I input return _G.c_argument_in_range(142,0,0.1,"") in the LUA console. It can return true or false, but how should I use it in the script? if net.dostring_in('mission', 'return _G.c_argument_in_range(142,0,0.1,"") ') then trigger.action.outText("very good! Please proceed to the next step" ,10 ) end But it doesn't work

very good

I see. They come from mission in the LUA console. But I don't have a LUA console. How can I obtain these functions?

Thank you for your answer. I already know this. I learned it from you! I mean to ask about this function Where is _G.a_cockpit_perform_clickable_action obtained and where can such functions be found? _G.a_cockpit_perform_clickable_action

Hello, could you tell me these functions _G.a_cockpit_perform_clickable_action(<) device id> , < button id> , < value> Where did ")) get it from? It feels much more convenient than in the ME trigger. Thank you very much!

ED's reply was to look in the manual, but I didn't find any explanation about the AVIONICS PLUGIN

Hello, could you tell me X: What does this AVIONICS PLUGIN under the cockpit trigger mean? I couldn't find the answer online

Thank you, I think I've figured out how to use the indicator, and I'll look into the parameters later。

Thanks, I found the indication for KA50 PVI waypoint number, please, is there any difference between indication and parameters? Sometimes they can be substituted for each other, in addition, the coordinates highlighted by the indicator are not on the indicator and deviate greatly. I've tried multiple planes and they're all the same Damn translation, I hope you understand what I'm talking about

Hello, is it possible for all pilotable aircraft to find parameters in this way? If yes, that's great By the way, man, can you find the format type for this value? Is it -1-1 decimal or string

Thank you for your help, I'm learning the use of cockpit triggers, it's been a great help to me

You should try it with it：COCKPIT HIGHLIGHT INDICATIO

Hello, may I ask if this works on KA50ll? I only have KA50ll now

You look at this picture of mine, I just aimed at a point on the ground, but all four GBU38s avoided this target point. The error is about 5 meters ……JDAM TOO targeting currently is not recommended for the F/A-18 aircraft due to inherent sensor/system inaccuracies, unless mission failure or collateral damage due to wide misses can be tolerated.…… This is what I saw on a PDF, which should be the reason. Only PP mode can be used, and TOO mode cannot be used to specify targets for small targets

JDAM TOO targeting currently is not recommended for the F/A-18 aircraft due to inherent sensor/system inaccuracies, unless mission failure or collateral damage due to wide misses can be tolerated.

Anyway, it's not a minor mistake, is it? Only one of the four bombs can hit the target. I opened Unrestricted SATNAV. Blue side aircraft

Yes, some deficiencies are also understandable, because this may involve military secrecy,

thank you