ShadowDragonCZ

Good to know. When I am off vacation, I can try installing some of the mods and discover them using folders specifically instead of parsing entry.lua file.

This program needs entry.lua to be in root folder of the aircraft and the modules are searched for in the mods/aircraft folder. Removing the entry.lua wont help. If you place the folder and entry.lua correctly, is it seen by the app? I havent tried this with any moded plane so far.

DCS Data Export Tool GitHub: DcsDataExportTool What can this tool do for you? This console application will allow you to export DCS Clickable Data with IDs into CSV file for later use with DCS Stream Deck interface (might be usable by other DCS tools I am not aware of). Most of the modules and clickable data info can be looked at directly in the DCS SD plugin, but some of them can't and display empty table. With release of the Mirage-F1 and the fact, that DCS SD plugin wasn't updated for quiet a while, I have decided to write my own tool to get such data. Instead of going through the scripts manually while mapping SD buttons to DCS, you can use this tool to get them exported into CSV without all the unnecessary info noise around the LUA scripts. This tool is in early stage of development, it's not perfect and can only get better. It was tested only on my machine and few other machines of friends. If it's not working for you, crashes or does not export some of the module data, let me know so I can fix it. GitHub repository doesn't build the versions automatically yet, so only source code is now available. This will be done in future. Please, read the disclaimer on the GiHub page. If you don't feel like running some 3rd party app from unknown source, DON'T and wait for the GitHub released binaries. Supported modules (I was able to test) A-10C II Tank Killer A-10C Warthog AH-64D BLK.II AJS37 AV-8B N/A F-14 F-16C bl. 50 F-5E Tiger II F/A18C Ka-50 Black Shark M-2000C Mi-24P Mi-8MTV2 Mig-21bis Mirage F1 NS430 TF-51D Mustang UH-1H Huey As I do not have access to some other modules, any feedback is appreciated. If something doesn't work or is not right, feel free to contact me or creating Issue on the GitHub page directly. How to use You can find the instructions HERE Download LINKS DCS Data Export Tool Win-x64 ZIP file DCS Data Export Tool Win-x86 ZIP file Special thanks: Charles Tytler for the DCS Stream Deck plugin and ideas I have used for my tool NLUA Interface for making the development and interfacing with LUA possible Feel free to get in touch if you find bugs or need any help.

Oh, that's something different, yes. I have tried searching all the LUA scripts in the game folder for declaration of tis LUA function and haven't found anything. I am affraid that this method is somewhere in DCS binaries and not available to us, but only as part of SDK. I might be wrong, but wasn't able to find it.

Hi! I am also playing with LUA scripts of DCS for my project that exports the devices, controls and their values and IDs. I belive, that you need to pass the parameter, number of the devise as it can be seen in other modules. Example given: local ale39 = data.base.GetDevice(5) Also each module contains script called devices.lua. This LUA script contains list of all devices, their names and indexes.

I have managed to make the F1 export script work, there was a problem with Encoding of the lua and probably also Line endings. Cant really modify the original code of StreamDeck interface. Might have a look at it later and change the lookup path for Mirage in my own fork. Because of pure interest, I am writing my own tool for exporting the Button IDs from DCS modules. As I am C# developer not used to work LUA, it's a chance to learn. I was already able to get some data for Mirage F1, so will be working on formatting those into CSV or HTML page. If the project goes well, I might publish it for everyone. This tool could also be in form of DLL to be used by other projects. I have also looked at StreamDeck development examples and Elgato doesnt provide C# toolkit, which is a pitty. As StreamDeck DCS interface doesnt seem to be updated, I wanted to check, how much work it would be to recreate it from scratch and add some ideas. For now, not an option for me. I just would like to ease some work for others in looking up those damn Button IDs for their SD profiles.

Hi Everyone! Bailey, did you manage to get Stream Deck Interface list the DCS Interface values after clicking refresh? I have copied the Mirage-F1CE.lua to export scripts folder and get no output in SD. Other modules and scripts work just fine. Also, is the DCS Interface plugin still in development? It cant read the DCS IDs, cause the tool used to extract them, which is part of the plugin, cant read the clickable data thanks to the fact, that the folder structure is different for F1. It doesnt have exceptional case for F1, as it does for L-39 or C-101. It would be fairly easy fix for the developer, event I could do it myself, but looks like the plugin development is dead, which is a pitty.

Blu, adopted the method, put into Export.lua, still no ODU or UFC texts are displayed.

Hi, Blu, Thanks for the updated export. But looking at the first part, where list is parsed for the ODU values, I still doubt this is going to work, because my export already contained this part and texts were still not exported. I also haven't any luck catching these using Wireshark. I am at work now, but will try your updated Export.lua once I am back home.

I swear I was trying to find the image used in the control, but have not. Isn't it embedded in the Helios DLLs? Or is it sitting somewhere on the disk and Helios uses it as *.png ?

Thanks for the advice, will have a look at the debug option and might have a look at Wireshark too! For the source, will abandon the Master and have a look around the codebase. Might join the team, but there is always some learning curve. Thanks for the response, BlueFinBima, was hoping to see your message. Problem is, thatI have used the built in AV8 panel with UFC, without the cut-outs, where texts and letters are supposed to be displayed. I have setup the viewports for ODU and UFC and got it to second monitor, but the AV8 ODU and UFC parts do not display these, cause they do not seem to be transparent. If that is the case, is there some easy way to introduce ODU and UFC with cut-outs, so that the viewports below can be displayed?

Hi guys. Having problems with making the Harrier's ODU and UFC display the text values. I have followed all the possible instructions to get the right Export.lua and also checked that it contains line to parse ODU and UFC text values, but the text is not comming to my profile composed from the AV8 ODU and UFC controls. All the other buttons work flawlessly, but the text. I have also tried placing the text controls and binding it it Display text changed for ODU with no luck. I would happily exchange few messages and provide any possible lua script I have including my Helios profile. Displaying ODU values and controlling the UFC from second monitor was the main reason to get Helios up and running, but now I feel desperate. As I am C# developer in real life, I have also decided to fork and download Helios code to see if I can run it and maybe debug it, but haven't had enough time yet. Is there a way how to force Export.lua or other scripts to write into any debug file to see if the ODU files are comming from DCS?