Bailey

Try this. https://forums.eagle.ru/topic/266840-cant-get-stream-deck-hotkeys-to-be-recognized-in-dcs/?do=findComment&comment=4813510

It is working for me for the F-14B. You can use "Hotkey" to do the binds. If that does not work you can try this below. It's basically a more feature rich Hotkey feature. https://github.com/BarRaider/streamdeck-supermacro/blob/master/README.md

Np. All you need is a little more lua knowledge. Let's take the F16 lua for example (https://github.com/asherao/DCS-ExportScripts/blob/master/Scripts/DCS-ExportScript/ExportsModules/F-16C_50.lua). Starting on line 1076 you can see: ExportScript.Tools.SendData(3004, "CH " .. CMDS_CH_Amount .. "\nFL " .. CMDS_FL_Amount) ExportScript.Tools.SendData is the way that ExportScript uses its library to format the data to be sent to the streamdeck. 3004, is the ID that ExportScript assigns the following data "CH " .. CMDS_CH_Amount .. "\nFL " .. CMDS_FL_Amount is the data that will be sent to the SD. Let's break it down a bit more. It is "normal lua" so you can google all of these concepts. Anything in quotes can be considered a string. What you write is what you get. Anything not in quotes is a variable that was defined earlier in the code. The double dots are what combine the strings and the variables. Consider them as the tape that holds the two together. The "\n" is the way you tell lua that you want a NewLine. It essentially simulates the EnterKey. That's all there is to it! For practice, try making something like this in one of your export luas. I haven't tried this ingame, but it will get you used to the concepts. Take a look at some of the other luas like the hind and mossie to see these kinds of tiles in action. Keep the questions coming! local testNumber testNumber = 12345 ExportScript.Tools.SendData(9999, "TEST\n" .. testNumber)

I agree, its a headache. After clicking this link (https://github.com/asherao/DCS-ExportScripts), click the "Code" square/button and then click "Download Zip" in the dropdown. Then unzip/install as other mods/scripts. You can also navigate to the lua you want and copy/paste the code into the lua file already on your pc.

I personally use the first module main page as common buttons and systems like gear, flaps, etc. On that main page, if necessary, I’ll put sub system folders like comms, gps entry, etc. I don’t bother with startup stuff bc I use autostart for simplicity. I have not gotten Pages to work with anything other than the main Elgato first screen. Shortcut to folders may be an interesting alternative to using different profiles, but I haven’t seen or used it.

F-16C Update (https://github.com/asherao/DCS-ExportScripts/wiki/F-16C) - Removed F-18 code (haha, idk how it got in there) - Fixed CMDS readouts - Added more CMDS readouts - Added fuel totalizer readout - Added fuel flow readout - Added Media Pic This update was inspired by this post:

Concerning your first question: https://github.com/asherao/DCS-ExportScripts/blob/master/Scripts/DCS-ExportScript/ExportsModules/F-16C_50.lua https://github.com/asherao/DCS-ExportScripts/wiki/F-16C You can tinker with the rounding if you like by changing "totalFuelFlowCounter = round(totalFuelFlowCounter, -1)" to "totalFuelFlowCounter = round(totalFuelFlowCounter, -2)", if you like.

1. In the F16 you will have to find the IDs for the fuel totalizer (730, 731, and 732) and then make a function that extracts that data into numerical values for the button. The other way to get the fuel value is to call list_indication(6). In the lua code "if" you can read "["TOTAL value"]", "then" export the fuel value. Unfortunately this method will only work when the DED is on the BINGO page. 2. Kinda/yes/maybe, but it would be pretty complicated (imo). The best video that would expose you to how its done is this one. You will need to find the correct list_indication, the associate the MFD readout to the export text per button. P.S. I have found some errors in my F16 lua file. I'll update it and try to incorporate your first concern.

Nope. But I can put it on my project request list if you like.

Requesting the ability to get to the "Jester TPOD Menu" via the Jester Main menu. A few people have noticed that the "Jester TPOD menu" is only reachable via the contextual menu. Having it reachable from the Jester main menu will standardize its use, similar to the other menus and will be more reliable when used with a program such as VoiceAttack.

I may be able to, but no promises. What are things you would like to see?

Why do you use linking profiles instead of folders or pages?

(See wiki for details https://github.com/asherao/DCS-ExportScripts/wiki) F-86F Sabre - Added UHF and ADF frequency and channel export (3000-3003) Mi-24P Hind - Added following radios and channel exports (3031-3034) - R-863 - JARDO 1 - R-828 - R-852

Please share to prevent the same fate for others.

1. Yes 2. No, unless you have modded it. 3. Most don't release with support info, but it would be appreciated.

I don't use that part of DCS-BIOS that you have pictures. There is an updated method if using the reference page that leans on Google Chrome. I would uninstall all dcs Bios things and do a fresh install by following these instructions https://github.com/DCSFlightpanels/DCSFlightpanels/wiki/Installation

In the post you quoted the most recent version in within the link that ends in /releases.

Remember to press "OK" at the bottom right.

how?

Let's say you wanted to use the Sam Light. Copy your working master caution light button on the stream deck to a different location. Go to the Lua, line 104. You see that the argument is [38]. Put "38" in for the Image State Change for the master caution light button you copied. Niw when you do a lights test you should see your button light up. Change the button images to what you want. Also Clear the "Press" event if it's a non-button light.

Mossie Update - Added "°C" to temperatures - Fixed typos - Moved "Fuel Tot" to the bottom of its Tile - Made radio frequency detection more accurate - Changed "mbar" to "hPa" - Added commas to RPM values above 999 - Added kts2mph function - Converted all knots to mph

Thanks for the input. At the moment this utility has the same aircraft as DiCE. If I have the time and if there is demand, I'll update this one to.

I responded to the other thread. Hopefully it helps. As for the F18, from what I have seen so far, the status of FPAS (as an example) seems to only show when the FPAS page is up, which kind of defeats the point. For the left screen it seems that the things located on it are in list_indication(2). I used this in the DCS-BIOS to get that info, and that of others. local a = "\nList Indication 0\n" .. list_indication(0) .. "\nList Indication 1\n" .. list_indication(1) .. "\nList Indication 2\n" .. list_indication(2) .. "\nList Indication 3\n" .. list_indication(3) .. "\nList Indication 4\n" .. list_indication(4) .. "\nList Indication 5\n" .. list_indication(5) .. "\nList Indication 6\n" .. list_indication(6) .. "\nList Indication 7\n" .. list_indication(7) .. "\nList Indication 8\n" .. list_indication(8) .. "\nList Indication 9\n" .. list_indication(9) .. "\nList Indication 10\n" .. list_indication(10) return a

I'll reference the F-18C lua located here so that we are on the same page: https://github.com/asherao/DCS-ExportScripts/tree/master/Scripts/DCS-ExportScript/ExportsModules Go to line 72 and you will see that the status of many of the cockpit lights are exported. Typically they are from 0 to 1. If you dont find a light, you will have to use Model Viewer and use the argument animator and random guessing to find the correct argument. You'll then add it to the lua file itself. When you want to use it in the DCS Interface app create a Momentary Button. Image 1 will be the "Light is off", and image 2 will be "light is on". For the image change a crossover of 0.50 is usually fine.

Ah, I see. Nice! I think the next step is to get familiar with "list_indication" exports using the DCS-BIOS console. Do you know how to do that? It is in a few of Charles Tytler's videos.