nosaMtrevoC

I also use the stream deck extensively and build profiles for it. Created the p-47 profile recently and now working on an F-14B profile specifically for the stream deck. f-14B example of tape gauge on stream deck: How I use the stream deck for my p-51:

Example of the Exhaust nozzle position indicator on panel A3 (left knee panel) along with two different hydraulic pressure gauges.

Added: AFT & L Gauge (bottom left in pic) FWD & R Fuel Gauge (bottom Center) Added both above to Fuel Multi-Gauge (botton right third line) Added Accelerometer (top right, posMax/current/negMax) Added Clock and Timer (top center) Added references to panels in code and documentation: For instance all of the above gauges are in the Cockpit (A) and Right Knee Panel (9) so A9 RIO fuel gauge is in RIO Cockpit (B) and (7) The number (7) and (9) are referenced in the F-14 manual on pages 10 and 11 A9 - Cockpit Right Knee Panel is almost done, just the reset switches and knobs left.

_________________________________________________________________________________________________ ▀▀▀█ Needs Testing █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Items listed below need your testing because I am not familiar enough with the F-14 to find these systems and see if they relate to the ID I believe they belong to. 6b - Need the VDI Caution lights tested located on 6b graphic above on left and right of VDI and also located on pg. 58 picture and pg.59 description of the f-14 .pdf documentation. You cannot use the master test panel to test these as then all indicator lights are lit and I do not know if I have the correct ID's or not. I found the proper grouping of ID's, so even if a number of them get tested and are correct, I can confidently assume the rest are correct. 6c - Need the HDG and CRS Knob tested. I can spin them, obviously, but I do not see any type of change on HSD (heading change etc..) I need the F-14 HSD or hud or whatever put in the proper mode (maybe some type of nav or course mode) to see these knobs changing something. Also the BIT indicator at bottom right, I'm not sure how that works. Does it light up? and if so, I need a replay where it does. _________________________________________________________________________________________________ ▀▀▀█ Changelog █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Version 0.11 - Matched most of the missing ID's, fixed error in ACM Panel (Chacal IX) Version 0.10 - Matched many more ID's (not tested) for panels: A6b/A6c/A7, Created All Graphic Icons for panel A6a ACM Panel, App. Indexer Icons Custom Station Weap. Flags output for ACM, ACM Switch, Master Arm Switch, Gun Rate Code, code for SW Cool/MSL Prep/MODE stp switch testing ACM Panel items on Stream deck and creating profiles, Triple Indicator code and icons, Master Caution Button/Light, L & R Fire Lights, Slip/Ball Indicator Gauge, fill icons for stream deck, testing, A6a ACM Panel completed w/StmDeck Prof. & Icons Version 0.09 - Created 298 conifg Arguments and documentation for all pilot panels Left: A1a/A1b/A2/A4/A5/A6a/A6b/A6c/A6d/A7/A8/A10/A11a/A11b/12 Formatting, Matched most DCS ID's (not tested) for panels: A1a/A1b/A2/A6a Version 0.08 - Formatting, Arresting Hook handle/emerg.Handle/Light, Gun Ammun. Counter knob, gun rounds counter Version 0.07 - Create tape function for vertical tape displays, created engine RPM Tape and BG Icon, EIG Eng. Temp on A3, EIG Fuel Flow on A3 Version 0.06 - 2 Hydraulic Press. Gauges on A3 (51023 & 51063), added Engine Nozzle Tape A3, engine oil press. gauge Version 0.05 - Formatting, Added Bingo Knob, Accelerometer Reset, Clock Wind, Clock Start/Stop/Reset, fixed error in Timer, A9 Panel Complete Version 0.04 - More formatting, added Aft&L/Fwd&R fuselage fuel info, added Accelerometer gauge, added clock and timer gauge, Added Cockpit Refs. Version 0.03 - Organization of Cockpit and RIO areas in this file for organizational purposes (ease of use) Version 0.02 - Added formatted fuel output for location A9 Version 0.01 - Initial Layout and formatting of .lua file along with organization outside this file of all functions ID's calls etc..

Currently broken the work down into the F-14B Cockpit Layout Sections according to the F-14B manual found in the C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F14\Docs Directory (F-14B Manual 1.0.pdf) pages 10 and 11 These Sections are referenced in the .lua script as A for Pilot Cockpit and B for RIO Cockpit and the number in the picture to describe the section. Table below: [Ref]_ [Position]_____ [Description]________ A1a Pilot Left Side Console A1b Pilot Left Side Console A2 Pilot Left Vertical Console A3 Pilot Left Knee Panel A4 Pilot Left Instrument Panel A5 Pilot Left Windshield Frame A6a Pilot Center Panel A6b Pilot Center Panel A6c Pilot Center Panel A6d Pilot Center Panel A7 Pilot Right Windshield Frame A8 Pilot Right Instrument Panel A9 Pilot Right Knee Panel A10 Pilot Right Vertical Console A11a Pilot Right Side Console A11a Pilot Right Side Console A12 Pilot Canopy Control Handle NOTE: Areas below highlighted in RED in the picture are currently in need of testing. Please see the appropriate post (page of post listed in table above) to provide testing for these modules. Picture below shows completed sections in green:

Don't want to take over this thread with F-14B related information when it's more of a general thread about ctytler's plugin. For further discussion about the work on the F-14 Script please see this new thread: https://forums.eagle.ru/showthread.php?p=4387597#post4387597

Specific thread for the progress of my F-14B ExportScripts file with special considerations of nicely formatted output for the Stream Deck (see an example video of fuel outputs below) Newest version attached version 0.11 Date: June 30, 2020 Stream Deck Profiles and Graphics Included NOTE: ITEMS NEED TESTING If you are interested in helping test this script, please see "Needs Testing" area in the third post of this thread (below) for more information. Along with the pic in the second post describing which modules currently need testing. All testing related posts and information are in RED below. Example of FULL Working ACM Panel: Example of F-14B fuel output to stream deck: Example of RPM tape: Random Examples on Stream Deck XL See Section Progress in 2'nd Post below See Changelog in 3'rd Post below ---- for use with these two great projects: DCS-ExportScripts: https://github.com/s-d-a/DCS-ExportScripts DCS Stream Deck Plugin by Ctytler on ED: https://github.com/charlestytler/streamdeck-dcs-interface Example of how I use the two scripts on my stream deck (p-51 example): The Script is a Work in Progress. Thanks, GunSlingerAUS & Phoenix FR for providing me with the F-14 Module, it was a nice jester (sic). There will be changes and modifications to the file that I will post here and keep the latest version on this page. This can be used as a standard DCS-ExportScripts file for the F-14B when complete without a stream deck (use as you see fit), or has extra formatted id's that allow you to show nicely formatted live information on the stream deck. e.g. 250mph instead of 0.45048 (which might indicate needle position) see youtube video above for examples. If you have any questions feel free to ask. enjoy! F-14B v0.11.rar

i'm running logitech software installed, but I don't use it at all. just installed it for the drivers. In DCS I had no problem using the pinkie as a modifier. You do need to add it to the modifiers on the left before it will work though. I'm not using any workarounds whatsoever and pinkie works great for modifier. X-52 btw.

I don't mind posting my p-51 file in its entirety, but I don't like posting things like this that were not created entirely by me as it may look like I'm taking credit for doing the p-51d.lua file as a whole. Instead I just posted the portion of the code that is above. If I knew who originally created the P-51D export file I would give appropriate credits at top and then make my additions at bottom, but I do not know who did this originally. It's kind of a sticking point for me with open source work. Credit for others work is important.

keep in mind with altitude warning, it only works at 50' if proper pressure is set. the reason it shows - after 0 even though you are still at altitude is because if you go below 0 feet (because the proper inHg is not set) it shows 99999 and then 99998 etc... I didn't like the look of that on the gauge so as my code reflects if altitude is less than 0, just show - usually, you would not set your altimeter to Sea-level anyways, so this problem will always present itself if flying low over the channel for instance. The altitude warning is meant to be a visual that you can see out of the corner of your eye that changes to yellow at 50 and then red at 10, for instance, to assist with landing and when to flare etc...

Exactly (set air pressure, inches mercury) What you need to understand about the data exported is that it's cockpit or gauge information, not actual altitude (this goes for most of the data in this script) If you want to show 0 at sea level then you would need to set the altimeter to the proper at sea level pressure value for the location. Not exactly sure what you mean, they are listed in the lua file (green text is the description of id) These high ID's were created by me for formatted information. not sure what you mean by the "DCS Comms list" I haven't created a list of my "high number" id's in the .lua file, because I didn't create the original lua file, I just offered my high id code so that someone can integrate it in their original lua file easily and use it. It's formatted nicely like 10500 feet instead of some cryptic value from the export. The stream deck plugin is not my project, and adding my high id's to it would be simply editing the files in the stream deck plugin. Easy enough I'm sure, but a separate project altogether. I'm guessing first ctytler would want to make sure my code was included in the p-51 exportscripts project, which it isn't. No sense adding my ID's to his project if 99% of the people using exportscripts havent' seen this post. If you did add my code from here hopefully this will help: 2012 - True Heading 2002 - Command Heading 2025 - Altitude (from gauge) 2096 - Low altitude warning (if altitude is below 50' then this value is 1, otherwise 0) 2155 and 2156 - left and right fuel tank 2160 - Fuselage tank 2011 - Indicated Air speed 3011 - Overspeed warning (if speed is < 455 value is 0, if 455 or more value is 1) 3033 - multi-gauge shows temps and pressure gauge information for 5 things. 3032 - multi-gauge warning (if any of the above values from 3033 are out of range this value is 1 otherwise 0) All of the above descriptions are in green if opened in a proper .lua editor or after a double dash in my code, but not necissarily as descriptive or easy to read as above. I wrote this for me, and shared it with the community. In my post I stated this is not a "HOW-TO", but rather just me wanting to share what I have done so others can use it. It is the exact code I need to get it working as shown in my youtube video example. I had no intentions of re-writing the p-51D script to be easier or anything else for that matter. Just got it working and that's good for me, then shared it. the P-47 script and the upcoming F-14 script were written by me from the ground up and will be very descriptive. Hopefully you can get something from the above. Feel free to ask if you have any questions.

thought it was just me, but replays seem to be broken version to version. your replays work (kind of) as long as you don't upgrade.

Don't have one yet. the video is showing the raw output from the exportscript file and using the OP's stream deck plugin to use the 3'rd option to change or monitor text (can't remember what the title is) and using the ID's above like 56010 to monitor total fuel. I do not have a sD proifle though. First step is to build the output properly in the form of the exportscript.

Here's an example of the above fuel indicators for the Stream Deck with the F-14B

GunSlingerAUS and Phoenix FR, It's going to be a large undertaking, but well on it's way. Sent you both a PM regarding your email address' to keep you updated. If I post the in progress script here I'll end up answering more questions than its worth. Never like posting in progress code/scripts. Either way, I will post the original question posed by Phoenix which was doing the fuel output for the F-14 on the stream deck, completed that today along with documenting over 1000 and filtering about 2000 of the f-14 arguments or DCS ID's that relate to the cockpit including their functions, calls and appropriate variables. If you want to see an example of the fuel output I'll post a youtube video later on tonight (still processing), but to add the fuel outputs to your stream deck do the following: replace the ExportScript.ProcessIkarusDCSConfigHighImportance function (might look like below for you if you were testing with me, might look different if you were not, but you need to replace from the "fundtion ExportScript.ProcessIkarusDCSConfigHighImportance(mainPanelDevice)" line to the "end" function ExportScript.ProcessIkarusDCSConfigHighImportance(mainPanelDevice) --Test fuel 10k output local ourVariableTotalFuelRIO10k = mainPanelDevice:get_argument_value(2117) local ourVariableTotalFuel10k = mainPanelDevice:get_argument_value(6010) local ourVariableBingoFuel10k = mainPanelDevice:get_argument_value(6020) ExportScript.Tools.SendData(2600, ourVariableTotalFuelRIO10k) ExportScript.Tools.SendData(2601, ourVariableTotalFuel10k) ExportScript.Tools.SendData(2602, ourVariableBingoFuel10k) end with: function ExportScript.ProcessIkarusDCSConfigHighImportance(mainPanelDevice) -- every frame export to Ikarus -- FUEL Exports Formatted -- NOTE: In case you are wondering to the weird methodology used below to derive fuel totals, I'll try to explain. -- A combination of how the f-14 module is using this fuel data (e.g. 0.9 might mean 900 lbs, 0.0 would mean 000 lbs and 1.0 would mean 000 lbs also which effects the total if you use math to add them all together, so we can't use a simple method) -- And also playing into this is the non-existance of certain math functions in lua language like concatenation or rounding. You need to convert to string and back which is slow -- Because of this (not fully explained) it will create strange output for the total fuel when it rolls between whole values e.g. 15000 to 14900. -- So instead we convert them to strings right away and extract the portion of the string (3'rd charachter) that is always correct (e.g. 1.0 is always 0 and 0.0 is also 0 and 0.4 is 4 etc...) -- we then take the 10k, 1k, 100's etc.. 3'rd charachter and combine them like 15000 -- There is still a strange behaviour at first site that is exhibited, that is not so strange once explained: -- When rolling over from 15000 to 14900, it will show 15000, then 15900 for a second or two, and then 14900. The reason is that the hundreds dial on the f-14 rolls quicker than the thousands dial therefore getting updated first instead of at the same time. -- the above strange behaviour cannot be corrected unless there is a variable that stores the total fuel value instead of the fuel cockpit dial value which are two different things. (In my experience most dcs mods only give you access to the latter) -- Therefore, we first concatenate the number to 0.X by converting it to a string and formatting it as such, and then extract the 3'rd character (I get it, nasty work around, If you have a better solution I'd love to hear it.) local RIOFuel = string.sub(string.format("%.1f", mainPanelDevice:get_argument_value(2117)), 3, 3) .. string.sub(string.format("%.1f", mainPanelDevice:get_argument_value(2118)), 3, 3) .. string.sub(string.format("%.1f", mainPanelDevice:get_argument_value(2119)), 3, 3) .. "00" local leftFuel = string.sub(string.format("%.1f", mainPanelDevice:get_argument_value(6000)), 3, 3) .. string.sub(string.format("%.1f", mainPanelDevice:get_argument_value(6001)), 3, 3) .. "00" local rightFuel = string.sub(string.format("%.1f", mainPanelDevice:get_argument_value(6004)), 3, 3) .. string.sub(string.format("%.1f", mainPanelDevice:get_argument_value(6005)), 3, 3) .. "00" local totalFuel = string.sub(string.format("%.1f", mainPanelDevice:get_argument_value(6010)), 3, 3) .. string.sub(string.format("%.1f", mainPanelDevice:get_argument_value(6011)), 3, 3) .. string.sub(string.format("%.1f", mainPanelDevice:get_argument_value(6012)), 3, 3) .. "00" local bingoFuel = string.sub(string.format("%.1f", mainPanelDevice:get_argument_value(6020)), 3, 3) .. string.sub(string.format("%.1f", mainPanelDevice:get_argument_value(6021)), 3, 3) .. string.sub(string.format("%.1f", mainPanelDevice:get_argument_value(6022)), 3, 3) .. "00" local multiGauge = "BINGO " .. bingoFuel .. "\nTOTAL " .. totalFuel .. "\n\n L | R \n" .. leftFuel .. " | " .. rightFuel ExportScript.Tools.SendData(52117, ExportScript.formatFuel('RIO', RIOFuel)) ExportScript.Tools.SendData(56000, ExportScript.formatFuel('left', leftFuel)) ExportScript.Tools.SendData(56004, ExportScript.formatFuel('right', rightFuel)) ExportScript.Tools.SendData(56010, ExportScript.formatFuel('total', totalFuel)) ExportScript.Tools.SendData(56020, ExportScript.formatFuel('bingo', bingoFuel)) ExportScript.Tools.SendData(56024, multiGauge) end and at the end of the file where you see Custom Functions area looks like: ----------------------------- -- Custom functions -- ----------------------------- Create some new lines below it and add: ----------------------------- -- Custom functions -- ----------------------------- function ExportScript.formatFuel(fuelType, fuelValue) -- Return Requested Fuel totals formatted (You can change the formatting here) local returnFuel if fuelType == "RIO" then -- Return Total RIO Fuel Qty Formatted like F-14 Gauge returnFuel = "TOTAL\nFUEL QTY\n" .. fuelValue .. "\nLBS" elseif fuelType == "left" then -- Return Total Left Fuel Qty Formatted like F-14 Gauge returnFuel = "L\n" .. fuelValue elseif fuelType == "right" then -- Return Total Right Fuel Qty Formatted like F-14 Gauge returnFuel = "R\n" .. fuelValue elseif fuelType == "total" then -- Return Total Fuel Qty Formatted like F-14 Gauge returnFuel = "FUEL\n" .. fuelValue .. "\nQTY" elseif fuelType == "bingo" then -- Return Total Bingo Fuel Qty Formatted like F-14 Gauge returnFuel = "BINGO\n" .. fuelValue end return returnFuel end save file and for reference ID's use the following: (note: this doesn't need to be added to the file) [Formatted for Stream Deck] [iD]______ [Description]__________________________ [status]_______ [Output e.g.]___________ 52117 RIO Total Fuel Gauge in lbs working 15000 lbs 56000 Left Fuel Gauge in lbs working 4000 lbs 56004 Right Fuel Gauge in lbs working 4000 lbs 56010 Total Fuel Gauge in lbs working 15200 lbs 56020 Bingo Fuel Guage in lbs working 04000 lbs 56024 Multi Fuel Guage Custom working Shows all relevant fuel output totals in a single stream deck button Figured I'd get your original question out of the way first. Next step is maybe the fuel warning lights? Still familiarizing myself with the f-14, need to figure out which lights go on and when and where etc... (diving through the manual) Then back to all the other ID's If you have a request about formatted or specialized output to the stream deck let me know and I'll prioritize them. more to come....

What information are you looking for?

And what would happen to the $1k in modules (and much more for many) that we've already spent? I now have to pay monthly for a product I already own?

Thanks olddog, made the changes, added the switch cover id's, version 0.14 or later should reflect these changes.

Wasn't sure, thanks, I'll take a look at the script for this and make any changes.

I'm guessing this list is a manual reference that the developer inputs into his plugin for your reference. He probably just hasn't gotten around to doing this yet. That being said, I have documented my P-47D export script extensively and it can easily be used for the same purpose by opening it in a text editor and looking through the descriptions of each and their id's in brackets [56] < like that is id and description is after -- hope that helps

For clarity, are you finding that the ID's are wrong or don't relate to the covers and switches, or are you just saying it would work better if you could just use one switch to uncover and arm? The export script is designed to make available all clickable data in the cockpit to external applications, not necessarily to make it easier to use. If the planes model restricts the use of the switch when the cover is down (even with key bindings in the controller setup) then that is by design. Doesn't mean you are out in the cold with this, You could write a script that: Checks the state of the arm switch (armed|off) If off and you click arm, open cover and arm OR if armed and you click off, move to off and close switch cover etc.. You could also probably just write a script to set the default switch cover values to up. Probably a few ways around this, but is definitely outside the scope of the export script specifically unless you are saying the ID's do not match their respective descriptions.

I will when I do one. I mostly fly the p-51, but will make a p-47 panel soon and share here.

removed attached file and moved it to the user file area so that there is one area to keep it updated.

Glad it's resolved, there is a specific order for your export.lua that works and does not. I remember running into this when installing exportscripts.

Also, this may be the problem (please report back if this is): According to their site: Windows 10 May 2020 Update Requires Elgato Stream Deck Software Update to 4.7 https://help.elgato.com/hc/en-us/articles/360044140571-Windows-10-May-2020-Update-Requires-Elgato-Stream-Deck-Software-Update-to-4-7