nosaMtrevoC

where would one get the zip file? I have the installer from their site which is saying it can't find the 2.5.5 open beta branch. I have 2.5.6 branch installed.

There are a number of methods that I use depending on a number of factors, but a good start would be to read the DCS-ExportScripts manual: https://github.com/s-d-a/DCS-ExportScripts/wiki/Documentation-in-English These methods will not always give you what you are looking for on some modules. Keep in mind every module can and many times does use differing methods that make discovery just that... discovery. Anyways, the above is a great start.

Don't want to start a rant thread, but I'm just wondering if there are plans in place to fix or re-work the current replay system. I like to make DCS Videos and replay my campaign missions afterwards, and although I have some limited success with this system sometimes, lately I can't even get a single replay working. Usually, crash into the ground immediately etc.. Anyways, again I don't want to jump into specifics, just wondering if there are plans to fix this in the near future.

Are there DX buttons that are not available on keyboard map? Is there another reason that you want to refer to a DX mapped button over the keyboard map? I'm guessing I'm missing something.

stream deck can send key presses without a joystick emulator. This plugin although awesome is not needed for simple keystrokes or send commands. You may be able to do what you are looking for without any additional software.

Out of curiosity, what are you using this for in VR?

More testing: 6b - Need the VDI Caution lights tested located on 6b graphic on second post; 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. (see picture below of items on HSD that need testing)

would buy a herc or hawkeye in a second

Thanks davidp57, I haven't written off the idea, but we'll see how much enthusiasm I have for the project after the cockpit. I'll keep you in mind if I get to that stage for testing as that is the biggest roadblock for me is knowing the seat enough to test it. I'm guessing I could re-use a certain amount of code from the cockpit, so we'll see. Ideas not off the table.

Thanks for the find, made the change.

a VTOL SR-71 with glass cockpits and weapons... that's mind melting.

that being said, there have been a lot of addition of ID's in v0.10 and the next as this has been some of my focus after phoenix mentioning the loss of functions. That is the problem with releasing an "In Development" project.

Thanks Chacal, yeah unfortunately there are a ton of ID's in the 14. Focusing on trying to get most of them included in the Cockpit soon. A rough guess is around 350 in the Cockpit that are actually used, but there are around 3 times that in ID's available used for other things as you may know, plus the RIO seat. Takes a while to really sort and find the proper ID's and test them. I could just add all of the ID's I have in my excel sheet (over 1,700) to the script and all existing would work, but I'd like to only add ID's that have been confirmed and tested in the cockpit in a very methodical manner to ensure I don't have an incorrect, duplicate etc.. as out of almost 2000 ID's, the cockpit clickable and indicators probably use less than half of them. I'm already adding overhead with the custom output, so don't want to export more data than I need. Not sure if many people use the RIO seat, but don't have current plans to model it on stream deck right now, just the full cockpit, so if you use the RIO seat on your stream deck, then my script most likely will break something. That being said, I might just add all the RIO ID's as an option to use at the beginning of the script so it can be turned on/off etc... (maybe I'll add a config script to enable/disable certain aspects like this).

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.

Just wondering if anyone has played around with deleting certain assets in the DCS directory on a laptop for instance to reduce the installation size for Mission Editor only operation. I'm guessing there are many files unneeded if I only plan on using the Mission Editor. Do I need to install each of the terrains to create missions for them? and which assets are needed if I will never actually load anything but ME? We could probably get a pretty small minimum installation with many unnecessary files deleted. has anyone done this?

3 way buttons and all of the output for the most part is done programatically in the script. Can't currently do it on the stream deck itself.

Just an update, finished the ACM Panel for the F-14 in v0.10 ACM Panel Video: Official thread: https://forums.eagle.ru/showthread.php?t=278252

Just an update, finished the ACM Panel for the F-14 in v0.10 ACM Panel Video: Official thread: https://forums.eagle.ru/showthread.php?t=278252

Just an update, finished the ACM Panel for the F-14 in v0.10 ACM Panel Video: Official thread: https://forums.eagle.ru/showthread.php?t=278252

ACM Panel Done. Packing it up for upload to here as v 0.10 soon.

slip / ball indicator

thanks guys, just got the rest of the panel working, including a working slip/ball indicator which I'll show you tonight sometime. Just need to package it all up (lots of icons) and create a stream deck profile for you guys so you don't have to set it up as each button is very different in how it operates.

to be clear, allowing or distributing a SDK or documentation on an API does not make software open source. The two are not related in any way.

Air Combat Maneuver Panel Teasers

Abril, worked perfectly. More than half done a complete ACM panel with all items working. Only thing left is the left and right fire lights, master caution button and the slip/ball indicator which I will finish tomorrow. All other items have custom icons and stream deck functions including working three way switches, weapon status flags that work identically to F-14, triple status indicators on one button and more. Will post some teaser videos later tonight after my videos finish processing on google.