Levinsky

Great find, much appreciated. Ken.

Lol this is quite clever LunaticFringe :smilewink: once I saw his other posts and understood found this very amusing. Never intended to respond to the OP message but your response was too good not to.

Looking good Pete - time to take it flying and cause some virtual mayhem :)

Pete, mate! that looks awesome. Well done - weekend well spent yeah? :) Ken.

Hi Gus, also - unfortunately I couldn't find a complete listing of functions (spent a lot of time looking :)). I use "strings" and "grep" a lot when trying to solve a particular problem. If I find any others I will post them up. I should probably start a thread for my cockpit build. Ken.

Hi Gus, yeah it's simple now.. but simple was not the right word when working it out. No documentation around this unfortunately. I installed cygwin and ran the Unix commands "strings" and "grep" over every file in the DCS folder looking for references of "chaff" and "flare". In the original export.lua (it's about 39KB) there is a section towards the end that has the code: LoGetSnares = {chaff,flare} Then through a bit of trial and error with that function I found out that it returns a table. If you put the code from original post into the processafternextframe function of Export.lua it just constantly sends you the chaff and flare count. Tested it by dropping chaff and it decrements along with what the cockpit was telling me. So for the CMSP panel. Pretty much everything is a known state from start except how many chaff and flares. My intention is just track when the switches or buttons are used on the panel and update both the sim and my own values driving the LCD display. You can also get the error/damage state of the counter measures and ECM gear so you can put the correct error message on or shutdown the display/panel if the sim is reporting your counter measures are out. I think with this I can avoid either exporting the display and chewing up another monitor port or using OCR. But will see. Will be cutting and engraving the panel soon so will report on how it works out. Definitely going with the Arduino for driving the LCD as I have more experience coding and working with Arduino. Ken.

Found the answer Hi guys, turns out it is pretty simple to get the chaff and flare count. local CM = LoGetSnares() default_output_file:write(string.format("Chaff count = %d \n",CM.chaff)) default_output_file:write(string.format("Flare count = %d \n",CM.flare)) Of course you could push this out to external app via UDP or whatever you want. I intend to use this for the counter measure panels to write to an LCD via probably an Arduino board. Ken.

Hi guys, anyone know of a way to get the current number of chaff and flares on a given aircraft? I can't see anything. I found this below but its rather cryptic and not sure it means anything. LoGetSnares = {chaff,flare} Ken.

Hi, try this from Staffi Ken. http://forums.eagle.ru/showpost.php?p=1863464&postcount=8

Hi guys, Personally myself I'm building mine partly just for the fun and challenge of the build. Certainly flying in it (even in a half baked stage) is pretty cool as well. :) Ken.

Hi Tacno and Mike, appreciate all the information guys - its very helpful. I have been testing with my standalone install of DCS A-10C and not my DCS World so I don't break the setup I fly with. :). Looks like I will need to start testing with 1.2.6 though as I wasn't aware they changed it. Will test out what you both have provided - thanks. Ken.

Hi Duckling, thanks for the point in the right direction. Managed to get an Open Cockpits radio card interfaces and working nicely with DCS A-10C. I handled most of the smarts in my C# app as I also use that for the Open Cockpits CDU. Thanks, Ken.

Hi guys, been playing with exporting and setting the VHF AM radio through Export.lua and a C# app I'm testing with. The radio wheels/thumbs - They appear to work by sending the value you want to set them to. i.e. if you want the fourth dial to say "25" you need to send "0.25" to button 3016 on device 55. So I have a couple of questions I guess: Why does each dial for the radio have 2 buttons (is this for forward and back? If so I can't seem to see a difference in the values you send through) Is the only way to set the correct value is to have your application keep track of the value you want to set and just hard set it using a direct value? Any help would be appreciated. Thanks, Ken.

Hi Dooom, I put together a quick video showing the Open Cockpits 737NG CDU in action under DCS World/A-10C. It's not the best video (my first youtube upload) but you'll get the idea. I hope to add a better video soon. I am working on integrating the CDU back lighting into DCS as well and this should be working in the next few days - you flick in the in-cockpit lighting switches and the CDU back lighting is enabled. I also plan on using a CNC laser engraver to redo the buttons that control the CDU pages to the correct A-10C buttons. I will then remove/blank out the unused buttons so there wont be any confusion during flight :). Ken.

Hey Pete, I'm still excited over the ILS bars on the ADI. For some reason I didn't think it had them. The gauges seem to respond super quick too. I noticed the altimeter QFE display works as well. Ken.