Bailey

I like this idea. Sounds like a v2 effort. In the meantime I have enabled a little key flash when the button is clicked.

Update to the Kiowa MFK Overlay project. On the left you can see the background with the button click zones enabled. On the right is what you would see ingame. You can see that in the overlay there is a big blank spot where the switches were. What do you think would go well there? The only thing I can think of so far is a logo, haha.

Awesome. I am glad you got that sorted.

The first mission is not night, nor does it have an observation point. Are you certain you installed the campaign correctly and started the campaign via the campaign menu?

Thank you! Thanks for letting us know it works great in VR. I got to thinking a while after the request and yes, it's possible to do that. I have since then made a proof of concept. I have completed the vertical slice. Things that are working is the app background, button presses via app to sim (with automatic release), semi-transparent buttons, button grid framework. Things to work on are making and assigning all the numpad and keyboard buttons in code, making the visual (transparent) representations of the buttons in the overlay, making the press length a config option, and of course, naming the app. So, basically all the tedious, but simple(r) stuff. The project has turned out to be both more difficult and easier than I thought it would be. I have already learned so much. Maybe this can open up a whole new direction in module accessibility!

Nice! WIP stands for Work In Progess. These are not yet coded or implemented. If you'd like to, please feel free to do so.

Updated to remove 99% of keybind buttons. I found a way to do the Barundus commands directly. Note that the art is not yet re-implemented. It is still a very WIP, but functional, profile. https://github.com/asherao/DCS-ExportScripts/blob/master/docu/StreamDeck Examples/OH-58D Kiowa by Bailey WIP.streamDeckProfile @salival007, I have found a way to call the jester commands without using keybinds which will allow the profiles to be sharable without extra steps. On the SD put in a Momentary Button/Display (UFC) tile from DCS-Interface. Open `DCS\Mods\aircraft\F-4E\Cockpit\command_defs.lua`. Scroll down to the JESTER_WHEEL section. Note that it is device ID 78. Put that as the Device ID in the Tile. You will see a list of commands in the JESTER_WHEEL array. The first one is a Button ID of 3001. The second is 3002, and so on. You can do some maths with the code line number to figure out the deeper ones. This number is what you will put in as the Button ID for the tile. Keep the Send Values as default (as far as I can tell). Doing the above will allow you to use all(?) of the Jester Wheel commands without keybinds. You don't even need the wheel visible. Examples: - Button ID of 3004 and a device ID of 78 will command Jester Option 1. - Button ID of 3078 and a device ID of 78 will command Jester to navigate with TGT 1. - Button ID of 3079 and a device ID of 78 will command Jester to navigate with TGT 2. Try it out! Looking forward how you get on with it!

Thank you for sharing your profile. The lua on the git is a bit newer. Can you backup yours and try this one (https://github.com/asherao/DCS-ExportScripts/blob/master/Scripts/DCS-ExportScript/ExportsModules/F-4E-45MC.lua)? Let us know if it works. If it does, would you like the SD profile to be added to the Library? I am not seeing much about the SAI in the lua

Np. A few hours ago I added a sound mod that some may find entertaining

Your wish is granted. Uploaded. https://github.com/asherao/DCS-ExportScripts/tree/master/Scripts/DCS-ExportScript/ExportsModules

Awesome. Updated to include Windex, or both de-greaser and windex!

Kiowa De-Greaser Mod, inspired by this very thread. Remove the Grease Pencil mark from every livery, liveries of your choice, or make your own mark! https://www.digitalcombatsimulator.com/en/files/3339241/

There's no list.

No. Does not exist. Requested in another thread.

Fly at speed and altitude. Throw a few rounds. Adjust. Confirm with a few more. Adjust. Don't have to touch it again. I have a custom reticle that will account for both 50 meters and whatever the heck I have at normal engagement range meters.

You can use my app called KIO-WA. You can define the number of feet to climb in baro or radalt modes and then execute it. Codewise, it tells the autopilot a discrete number (feet) for the action. https://forum.dcs.world/topic/351441-kiowa-integrated-overlay-warrior-automatis-kio-wa/

Does the issue fix itself if you toggle the Baro/RadAlt button 3 times? I'm thinking this may be a result of the initial state of the kiowa ai when turned on.

1) ty 2) The relative-ness of those buttons are based off what the barundus ai hud is showing. There are situations where things that seem odd may happen. I would have to see a video of the above to track down if it's a KIO-WA issue. For example, if you are at 500ft and do a relative increase by +100 ft, barundus will start flying to 600 ft. If while at 550ft you add another +100, the result will be 700ft, not 650 ft.

Wishlist. They know.

1) Great work documenting this! Does the middle mouse click override still work? 2) Haha, noted. Awesome! Thanks so much for your help and testing!

KIO-WA v0.6 is Live! https://github.com/asherao/KIO-WA/releases A lot of new features have been added. Please read the updated Readme. v0.6 Update Notes - Barundus will ignore CFIT (Controlled Flight Into Terrain) Baro altitude commands - Barundus will tell you that he does not agree with CFIT via audio - Altitude selection button will turn red if Barundus thinks it is a CFIT command - CFIT commands can be enabled via the config file - CFIT commands can be given with using the middle mouse button on the altitude button - Buttons moved around - Removed old relative heading feature - Added new relative heading feature - Enabled relative altitude button - Enabled relative knots button - Enabled drift button - Added config options for relative button step sizes - **Updated Readme**

The Readme has been re-written to include descriptions of all button and config options. This is looking like a good public version candidate... https://github.com/asherao/KIO-WA?tab=readme-ov-file#kiowa-integrated-overlay---warrior-automatis

1) Unfortunately, that is not how it works via the game controls. In DCS when you use the keybind, it increases/decreases the rate of the drift. 2) I have combined this into one button. Scroll will select the offset, clicking will apply the offset.

You are correct.

I have figured out how to do drift, increase/decrease speed and altitude, and incremental turns. How to best do this in the GUI from a user's standpoint? Should I set a standard increment in the code, or in the config, or add another button on the GUI for the player to change as they see fit?