JohnMclane Posted December 5, 2024 Posted December 5, 2024 I'm trying to use the current frequency of a channel to enable a F10 menu option. Is "cockpit param equal to" the right trigger to use? Is this information located in this image? Someone could save me alot of time before I start trial'n error this stuff... Any kind of point me in the right direction would be greatly appreciated. Thank you!
Kinkkujuustovoileipä Posted December 5, 2024 Posted December 5, 2024 Sorry, this is not something I'm able to help with directly, but have you tried looking at how SRS gets this information? 1
JohnMclane Posted December 5, 2024 Author Posted December 5, 2024 (edited) 10 hours ago, Kinkkujuustovoileipä said: Sorry, this is not something I'm able to help with directly, but have you tried looking at how SRS gets this information? I've posted the question in the ME forum, got an answer showing me where the args are listed but none of them involve the radios... So SRS are probably doing it in a way that cant be used in the ME triggers interface. Edited December 5, 2024 by JohnMclane
SloppyDog Posted December 9, 2024 Posted December 9, 2024 (edited) Ok, if you are trying to set a trigger based on a radio frequency set in the Remote Frequency Indicator, I think I have this figured out. It was an interesting challenge to learn how to do it. In order to detect a parameter from an indicator in the cockpit you need to use the function X: COCKPIT INDICATION TEXT IS EQUAL TO. This function asks for three parameters to be filled in order to work correctly: INDICATOR ID ELEM NAME VALUE ---------- INDICATOR ID Indicators are anything that present a value to the crew. In the case of the Remote Frequency Indicator (RFD), or any indicator, you have to find its ID. The ID for indicators are normally inside the Cockpit folder for the module, referenced in the device_init.lua file. For the Kiowa, this file can be found in the \Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\OH-58D\Cockpit folder. Inside the device_init.lua you have to look for the indicators section. I am using the Notepad++ software to open the lua files, and I recommend that you use it too, as it identifies the line numbers. I'll be referencing the line numbers from now on. The indicators section starts at line 82. The RFD is listed on line 91. From the DCS User Manual, page 166, it is stated that the indicators ID start at 0 and increase by 1 with each subsequent line. So, if you count from line 83, "OH58D::ccControls Indicator", considering it as 0, to line 91, "OH58D::ccRFD Indicator", you will end up with 8. This is the INDICATOR ID you are looking for. ----------- ELEM NAME This is the tricky part. You have to look for the Main_page.lua file inside the indicator folder. For the RFD it is inside the Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\OH-58D\Cockpit\RFD\Indicator. As you are looking for a frequency showed in the RFD, you have to look for the Frequency section inside the file. Using Notepad++ it is on page 134. The ELEM NAME is always listed as "Something.name". In the case of a radio frequency, on line 140 we found Freq.name. Freq.name = "Freq".. string.format("%i", i) So, we have the first part of the ELEM NAME, Freq. The Freq is inside a for loop, counting from 1 to 5, as shown on line 136: for i = 1, 5 do So, as we are interested on Frequency 5 on the RFD, the string.format("%i", i) will be 5. Thus, the ELEM NAME is Freq5 ----------- VALUE This is the easy part. It is a simple string. Sometimes it requires the dot,sometimes it doesnt. In the case of the A-10C it was not necessary to input the dot; in the case of the Kiowa it was needed. Pure trial and error to find out. I chose 055.000 Mhz as the desired frequency to activate the trigger, thus the VALUE in this case will be 055.000. -------------------- Now, you can get in the Triggers section of the Mission Editor and input the parameters For the Triggers I created a Switched Condition, so that every time you input the right frequency the trigger will be activated. The Condition is the X: COCKPIT INDICATION TEXT IS EQUAL TO, with the following parameters INDICATOR ID = 8 ELEM NAME = Freq5 VALUE = 055.000 The Action is a Message to All ----------------------------------- I made a mission using two A-10C as testbeds and a Kiowa. For the A-10s, every time you input: Preset Channel in the UHF radio equal to 02 or; A frequency of 255.000 Mhz in the UHF radio, a message will appear. For the Kiowa, every time you input 055.000 in the Radio 05, a message will appear. Attached is a track file showing the operation in the Kiowa and the mission I used for the tests. Oh-58D Kiowa RFD Frequency Trigger.trk A-10C-Radio Text Test.miz Edited December 9, 2024 by SloppyDog 2 3
JohnMclane Posted December 9, 2024 Author Posted December 9, 2024 14 hours ago, SloppyDog said: Ok, if you are trying to set a trigger based on a radio frequency set in the Remote Frequency Indicator, I think I have this figured out. It was an interesting challenge to learn how to do it. In order to detect a parameter from an indicator in the cockpit you need to use the function X: COCKPIT INDICATION TEXT IS EQUAL TO. This function asks for three parameters to be filled in order to work correctly: INDICATOR ID ELEM NAME VALUE ---------- INDICATOR ID Indicators are anything that present a value to the crew. In the case of the Remote Frequency Indicator (RFD), or any indicator, you have to find its ID. The ID for indicators are normally inside the Cockpit folder for the module, referenced in the device_init.lua file. For the Kiowa, this file can be found in the \Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\OH-58D\Cockpit folder. Inside the device_init.lua you have to look for the indicators section. I am using the Notepad++ software to open the lua files, and I recommend that you use it too, as it identifies the line numbers. I'll be referencing the line numbers from now on. The indicators section starts at line 82. The RFD is listed on line 91. From the DCS User Manual, page 166, it is stated that the indicators ID start at 0 and increase by 1 with each subsequent line. So, if you count from line 83, "OH58D::ccControls Indicator", considering it as 0, to line 91, "OH58D::ccRFD Indicator", you will end up with 8. This is the INDICATOR ID you are looking for. ----------- ELEM NAME This is the tricky part. You have to look for the Main_page.lua file inside the indicator folder. For the RFD it is inside the Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\OH-58D\Cockpit\RFD\Indicator. As you are looking for a frequency showed in the RFD, you have to look for the Frequency section inside the file. Using Notepad++ it is on page 134. The ELEM NAME is always listed as "Something.name". In the case of a radio frequency, on line 140 we found Freq.name. Freq.name = "Freq".. string.format("%i", i) So, we have the first part of the ELEM NAME, Freq. The Freq is inside a for loop, counting from 1 to 5, as shown on line 136: for i = 1, 5 do So, as we are interested on Frequency 5 on the RFD, the string.format("%i", i) will be 5. Thus, the ELEM NAME is Freq5 ----------- VALUE This is the easy part. It is a simple string. Sometimes it requires the dot,sometimes it doesnt. In the case of the A-10C it was not necessary to input the dot; in the case of the Kiowa it was needed. Pure trial and error to find out. I chose 055.000 Mhz as the desired frequency to activate the trigger, thus the VALUE in this case will be 055.000. -------------------- Now, you can get in the Triggers section of the Mission Editor and input the parameters For the Triggers I created a Switched Condition, so that every time you input the right frequency the trigger will be activated. The Condition is the X: COCKPIT INDICATION TEXT IS EQUAL TO, with the following parameters INDICATOR ID = 8 ELEM NAME = Freq5 VALUE = 055.000 The Action is a Message to All ----------------------------------- I made a mission using two A-10C as testbeds and a Kiowa. For the A-10s, every time you input: Preset Channel in the UHF radio equal to 02 or; A frequency of 255.000 Mhz in the UHF radio, a message will appear. For the Kiowa, every time you input 055.000 in the Radio 05, a message will appear. Attached is a track file showing the operation in the Kiowa and the mission I used for the tests. Oh-58D Kiowa RFD Frequency Trigger.trk 134.28 kB · 2 downloads A-10C-Radio Text Test.miz 11.03 kB · 2 downloads Man you basically took the time to write a how-to instead of just telling me the results, Thank you very much for this! You just taught a man how to fish! (like not literally, I've been fishing my whole life but you know what I mean). 1 1
SloppyDog Posted December 10, 2024 Posted December 10, 2024 (edited) No problem, man. Thanks for the compliment. As a teacher in real life and a curious by nature, it was a good challenge to learn all this. I'm glad you liked the way I explained it. It was very useful for me as well, because I'm trying to do the very same thing, but for the F-15E. Edited December 10, 2024 by SloppyDog 2
Qazplm Posted May 14 Posted May 14 2024/12/9 PM5点09分，SloppyDog说： Ok, if you are trying to set a trigger based on a radio frequency set in the Remote Frequency Indicator, I think I have this figured out. It was an interesting challenge to learn how to do it. In order to detect a parameter from an indicator in the cockpit you need to use the function X: COCKPIT INDICATION TEXT IS EQUAL TO. This function asks for three parameters to be filled in order to work correctly: INDICATOR ID ELEM NAME VALUE ---------- INDICATOR ID Indicators are anything that present a value to the crew. In the case of the Remote Frequency Indicator (RFD), or any indicator, you have to find its ID. The ID for indicators are normally inside the Cockpit folder for the module, referenced in the device_init.lua file. For the Kiowa, this file can be found in the \Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\OH-58D\Cockpit folder. Inside the device_init.lua you have to look for the indicators section. I am using the Notepad++ software to open the lua files, and I recommend that you use it too, as it identifies the line numbers. I'll be referencing the line numbers from now on. The indicators section starts at line 82. The RFD is listed on line 91. From the DCS User Manual, page 166, it is stated that the indicators ID start at 0 and increase by 1 with each subsequent line. So, if you count from line 83, "OH58D::ccControls Indicator", considering it as 0, to line 91, "OH58D::ccRFD Indicator", you will end up with 8. This is the INDICATOR ID you are looking for. ----------- ELEM NAME This is the tricky part. You have to look for the Main_page.lua file inside the indicator folder. For the RFD it is inside the Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\OH-58D\Cockpit\RFD\Indicator. As you are looking for a frequency showed in the RFD, you have to look for the Frequency section inside the file. Using Notepad++ it is on page 134. The ELEM NAME is always listed as "Something.name". In the case of a radio frequency, on line 140 we found Freq.name. Freq.name = "Freq".. string.format("%i", i) So, we have the first part of the ELEM NAME, Freq. The Freq is inside a for loop, counting from 1 to 5, as shown on line 136: for i = 1, 5 do So, as we are interested on Frequency 5 on the RFD, the string.format("%i", i) will be 5. Thus, the ELEM NAME is Freq5 ----------- VALUE This is the easy part. It is a simple string. Sometimes it requires the dot,sometimes it doesnt. In the case of the A-10C it was not necessary to input the dot; in the case of the Kiowa it was needed. Pure trial and error to find out. I chose 055.000 Mhz as the desired frequency to activate the trigger, thus the VALUE in this case will be 055.000. -------------------- Now, you can get in the Triggers section of the Mission Editor and input the parameters For the Triggers I created a Switched Condition, so that every time you input the right frequency the trigger will be activated. The Condition is the X: COCKPIT INDICATION TEXT IS EQUAL TO, with the following parameters INDICATOR ID = 8 ELEM NAME = Freq5 VALUE = 055.000 The Action is a Message to All ----------------------------------- I made a mission using two A-10C as testbeds and a Kiowa. For the A-10s, every time you input: Preset Channel in the UHF radio equal to 02 or; A frequency of 255.000 Mhz in the UHF radio, a message will appear. For the Kiowa, every time you input 055.000 in the Radio 05, a message will appear. Attached is a track file showing the operation in the Kiowa and the mission I used for the tests. Oh-58D Kiowa RFD Frequency Trigger.trk 134.28KB · 16次下载 A-10C-Radio Text Test.miz 11.03KB · 16次下载 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
SloppyDog Posted May 14 Posted May 14 10 hours ago, Qazplm said: 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 Yes, it is available for aircraft. Although, the files locations and parameters may vary from one to another. But the logic is the same. For the 1-1 I believe it is a string. To find the format types of the values, and the functions of cockpits arguments, you can refer to page 165 onwards of the DCS User Manual. There is a treasure trove of information in that and most people don't know nothing about it.
Qazplm Posted May 16 Posted May 16 2025/5/15 AM1点14分，SloppyDog说： Yes, it is available for aircraft. Although, the files locations and parameters may vary from one to another. But the logic is the same. For the 1-1 I believe it is a string. To find the format types of the values, and the functions of cockpits arguments, you can refer to page 165 onwards of the DCS User Manual. There is a treasure trove of information in that and most people don't know nothing about it. 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
SloppyDog Posted May 17 Posted May 17 Well, I don't know much about the Ka-50 PVI, maybe you should ask in the Ka-50 Mission Editor forum. They can help you better. Regarding indication and parameters: indications is everything that is shown to you on a screen, on a instrument, on a HUD. Parameters are related to the aircraft attitude. Meaning altitude, speed, bank angle, etc. As you said, sometimes they can be confused with each other, not exactly replaced. Let's say you want something to happen when the helicopter speed reaches 200 kph. You can make a trigger based on the real helicopter speed (parameter) or from a indication showed in a instrument or HUD (indication). The difference is in the fact that the parameter takes the real speed of the helicopter. If you have a problem with your instruments, and they show you 200 kph while the real is speed is 100 kph, you may trigger an action at the wrong moment. Indication also work to trigger actions based on a warning light inside the cockpit. Let's say you want something to happen when the oil temperature light comes on, that's an indication. Also, if you trying to trigger an action based on the PVI visor, that's an indication too. Regarding the coordinates, the first thing that comes to mind is if you are using the same coordinates system. Make sure the PVI is in Latitude/Longitude (lat/long) and you are using lat long to check the coordinates. Other reason may be the difference between the real coordinates and the Inertial Navigation System (INS) coordinates for the helicopter computer. One of the characteristics of INS systems is that they drift, they deviate from the initial position with time. And they deviate fairly quickly. To fix this problem you need to make a manual fix, and this procedure is different to each aircraft. And some aircraft in DCS does not even allow for a INS fix. The best and easiest way to avoid INS drift is to set your missions after 1996 in the Mission Editor and/or set the mission options to include the option "SATNAV available for all sides" or something like that. Doing this will allow for GPS or GLONASS to be available in the mission, and these system will automatically correct any drift that the INS has. Try doing this and then checking the computer position and the real aircraft position. Just be sure to be in the same coordinate system. 1
Qazplm Posted May 21 Posted May 21 2025/5/18 AM12点06分，SloppyDog说： Well, I don't know much about the Ka-50 PVI, maybe you should ask in the Ka-50 Mission Editor forum. They can help you better. Regarding indication and parameters: indications is everything that is shown to you on a screen, on a instrument, on a HUD. Parameters are related to the aircraft attitude. Meaning altitude, speed, bank angle, etc. As you said, sometimes they can be confused with each other, not exactly replaced. Let's say you want something to happen when the helicopter speed reaches 200 kph. You can make a trigger based on the real helicopter speed (parameter) or from a indication showed in a instrument or HUD (indication). The difference is in the fact that the parameter takes the real speed of the helicopter. If you have a problem with your instruments, and they show you 200 kph while the real is speed is 100 kph, you may trigger an action at the wrong moment. Indication also work to trigger actions based on a warning light inside the cockpit. Let's say you want something to happen when the oil temperature light comes on, that's an indication. Also, if you trying to trigger an action based on the PVI visor, that's an indication too. Regarding the coordinates, the first thing that comes to mind is if you are using the same coordinates system. Make sure the PVI is in Latitude/Longitude (lat/long) and you are using lat long to check the coordinates. Other reason may be the difference between the real coordinates and the Inertial Navigation System (INS) coordinates for the helicopter computer. One of the characteristics of INS systems is that they drift, they deviate from the initial position with time. And they deviate fairly quickly. To fix this problem you need to make a manual fix, and this procedure is different to each aircraft. And some aircraft in DCS does not even allow for a INS fix. The best and easiest way to avoid INS drift is to set your missions after 1996 in the Mission Editor and/or set the mission options to include the option "SATNAV available for all sides" or something like that. Doing this will allow for GPS or GLONASS to be available in the mission, and these system will automatically correct any drift that the INS has. Try doing this and then checking the computer position and the real aircraft position. Just be sure to be in the same coordinate system. Thank you, I think I've figured out how to use the indicator, and I'll look into the parameters later。 2
SloppyDog Posted May 22 Posted May 22 5 hours ago, Qazplm said: Thank you, I think I've figured out how to use the indicator, and I'll look into the parameters later。 Nice! It's a amazing feeling of accomplishment when we get to discover the inner workings of DCS.
Qazplm Posted May 25 Posted May 25 (edited) 2025/5/22 AM11点13分，SloppyDog说： Nice! It's a amazing feeling of accomplishment when we get to discover the inner workings of DCS. Hello, could you tell me X: What does this AVIONICS PLUGIN under the cockpit trigger mean? I couldn't find the answer online Edited May 25 by Qazplm
Rudel_chw Posted May 25 Posted May 25 2 hours ago, Qazplm said: could you tell me X: What does this AVIONICS PLUGIN under the cockpit trigger mean? no idea, I’ve never found how to use that feature For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
Qazplm Posted May 25 Posted May 25 14小时前，Rudel_chw说： no idea, I’ve never found how to use that feature ED's reply was to look in the manual, but I didn't find any explanation about the AVIONICS PLUGIN
SloppyDog Posted May 26 Posted May 26 20 hours ago, Qazplm said: ED's reply was to look in the manual, but I didn't find any explanation about the AVIONICS PLUGIN The manual doesn't say anything about it, but I believe these are for when you have an external equipment that inserts data into the sim. Example, a GPS or data cartridge with data that was taken during a real flight. Then this data can be inserted into the sim to redo a flight in sim in order to review it for debriefing. I believe it is for the military contractors that use the military version of DCS for training purposes.
Recommended Posts