ExoLight

The map looks awesome, thak you for your hard work! With that said, a lot of French friends and I are sad not to see a single French airbase in phase 3... Simply Colmar or Nancy would be awesome and unlock a great deal of Cold War scenarios from our end.

Hey all, With the current sales on Winwing's website, I'm also considering getting the ICP, but the DED only supporting the F-16 is a bit off-putting. I've seen @prestonflying's GitHub playground repo, but is anyone planning on taking this on and making a utility that could be used in conjunction with Lua export scripts? Or has anyone figured out another way of displaying stuff on the DED? If not, and if I ever get the ICP, I could give it a shot, but I never touched NodeJS (or JS for that matter) - so if I make it work, expect something botched.

Thank you Bailey for the help and finding all the IDs! Hope my small profile has been useful to some of you. I'll keep working on it when I can, but as Bailey said, I'll be fairly busy with work the next few weeks. Contributions or suggestions on what to implement next are of course welcome!

Thanks for the merge! Streamdecks are an awesome tool for DCS, I'm happy to share whatever tidbits I make on my spare time.

ed_fm_enable_debug_info would only show you one force vector (plus velocity vector) anyway, since the ed_fm_add_*_component functions aren't used. You won't see individual force vectors (stuff like airbrakes, control surfaces, gear, etc), only their sum as one big vector. If you want to see individual forces, you need to apply them in ed_fm_add_local_force_component instead of in ed_fm_add_local_force. One easy way to do it is to collect each force in a container (std::stack works very well for this), and each time ed_fm_add_local_force_component is called, apply the force at the top of the stack, pop it, and return true. When the stack is empty, return false. This way, you can easily visualize and debug them without having them merged in one big vector that's located inside the airframe, at the center of mass. It doesn't change anything about the MT problem though, you still need to run it in ST.

That's odd, it works with my friends. You sure you've got the latest export file and streamdeck profile ? Just in case, I zipped them (they're even more recent versions, these are only on my fork and not on the main repo yet) and attached them to this message. Please try these ones. M-2000C.zip

Hi again everyone, I flew the F-5E a few times these last few days, so I made myself a profile for it. Would be a shame not to share it, so as usual, PR opened. For those who would want to download it, when my PR is merged, head to the repository and download the latest master source. Although, @Bailey, maybe we should tag a version and make some new releases? Last one is from four years ago. Pictures of what it looks like :

On GitHub too, my changes have been integrated in the main branch. I just modified the M-2000C.lua file to add what I needed. If you haven't modified your own export scripts, you can just download the whole repo and update all export scripts. Otherwise, just download the latest script at "Scripts/DCS-ExportScript/ExportsModules"

CCRP and CCIP are merely terminology to describe the calculation method for delivery, that it, either showing the pilot where the bomb will land, or showing him where they need to be for the bomb to land on given coordinates. The Mirage 2000 and F-14 have completely different avionics and philosophies of employment. Thus, both guides are correct.

It's been merged in the main repository, you can download it now. Here's a direct link.

Hi all, A while back I made myself a Mirage 2000C profile. It occured to me that this project doesn't seem to have a M-2000C StreamDeck profile, so I thought I'd clean it up a little and upload it to the repo. It handles PCA, Green V/UHF control panel, some radar controls, and 4-state lamps (instead of just 2-state) for AP & master caution/warning operations. PR opened. In the meantime, here's how it looks like:

Do we know where the problem comes from in StreamDeck DCS Interface exactly? Is it getting confused somewhere in parsing, and if so, isn't there a way to patch it so it handles these edge-cases rather than hard-coding them?

I don't have BS3 installed, so I can't do it for you, but you could probably just copy paste command_defs.lua in a Lua interpreter and get the number associated to whatever command you need. Something like "print(device_cmds[your_cmd])". You could also dump all of the table, if I remember correctly: for key, value in pairs(device_cmds) do print(key.." => "..value) end Of course, having the StreamDeck plugin fixed would be best, but I have no idea how to do that, and that bug seems to have existed for a while.

Thanks, fixed. Also adjusted the WSO UFC's indicator index from 20 to 18, although I don't think there's ever a case where pilot and WSO's UFC have different states, so having a second export for that might be useless?

Hey guys, I noticed the F-15E script crashed midway through, which made some exports unavailable. Fixed it, PR opened. Problem was located in the UFC functions, called a method on a nil object. On another topic, for those who would want some StreamDeck icons for the Strike Eagle's master modes, I quickly made some. The archive is attached, and here is a screenshot of how they look: F-15E master mode SD icons.zip