Kiowa Integrated Overlays (KIO-WA AI and MFK Overlay)

[Bailey]

KIO-WA v0.4 Released! https://github.com/asherao/KIO-WA/releases

v0.4 Update Notes
- HDG2FACE Button - Barundus will turn the aircraft to the direction you are looking
  - Default HDG2FACE hotkey is Shift+Ctrl+F10
- Left click orbit button orbits left
- Right click orbit button orbits right
- Mouse wheel click orbit cancels orbit and flies straight
- If an orbit is commanded from a speed of less than 15kts, Barundus will orbit at 10 kts
- When you click Land, Barundus lands
- Made a different button green
- Added lots of notes and comments
- The Dial has been removed (It was fun while it lasted)
- Left/Right, Turn, and Drift buttons are not implemented

Hotkeys can be changed in `DCS Saved Games\Config\KIO-WA\KIO-WAConfig.lua`

[Gideon312]

18 hours ago, Bailey said:

KIO-WA v0.4 Released! https://github.com/asherao/KIO-WA/releases

v0.4 Update Notes
- HDG2FACE Button - Barundus will turn the aircraft to the direction you are looking
  - Default HDG2FACE hotkey is Shift+Ctrl+F10
- Left click orbit button orbits left
- Right click orbit button orbits right
- Mouse wheel click orbit cancels orbit and flies straight
- If an orbit is commanded from a speed of less than 15kts, Barundus will orbit at 10 kts
- When you click Land, Barundus lands
- Made a different button green
- Added lots of notes and comments
- The Dial has been removed (It was fun while it lasted)
- Left/Right, Turn, and Drift buttons are not implemented

Hotkeys can be changed in `DCS Saved Games\Config\KIO-WA\KIO-WAConfig.lua`

Awesome quick updates, so far it works like a charm, the only thing I can’t figure out is the drift!? What does it do? How to activate, and or give directions?

Whatever I do, left/right/middle/scroll it doesn’t change or react.

[Bailey]

3 hours ago, Gideon312 said:

Awesome quick updates, so far it works like a charm, the only thing I can’t figure out is the drift!? What does it do? How to activate, and or give directions?

Whatever I do, left/right/middle/scroll it doesn’t change or react.

I'm glad you are enjoying it. Note the update notes:

... - Left/Right, Turn, and Drift buttons are not implemented

The left/right button is an artifact from an earlier version. Hover drift is when Barundus is hovering and you want to slide to the left or right. Turn makes Barundus turn as long as you hold the button. The last two are still being worked out.  I have not yet found a solution for how to do those in KIO-WA. Hints, suggestions, and contributions are welcome. 

Edited June 19, 2024 by Bailey

[GrEaSeLiTeNiN]

1. Can the app be made to be off (hidden) by default? Also, after I hide the app, if I press the Pause sim key and then Pause again (to unpause), the app will reappear. 

2. HDG2FACE - If I position myself at the center between the two seats and look at where the aircraft nose is pointed after I command a HDG2FACE, it seems the final nose heading falls short by about 20 deg of where I was looking at. Is there a way to just add 20deg (or whatever the shortfall really is) to the command?  

Edited June 20, 2024 by GrEaSeLiTeNiN

[Bailey]

1 hour ago, GrEaSeLiTeNiN said:

1. Can the app be made to be off (hidden) by default? Also, after I hide the app, if I press the Pause sim key and then Pause again (to unpause), the app will reappear. 

2. HDG2FACE - If I position myself at the center between the two seats and look at where the aircraft nose is pointed after I command a HDG2FACE, it seems the final nose heading falls short by about 20 deg of where I was looking at. Is there a way to just add 20deg (or whatever the shortfall really is) to the command?  

 

1. No, I'd rather have it on by default to reduce the number of people thinking they installed it incorrectly. I can try to add more state tracking so that it stays on or off via the users requests. I'll consider putting a "hide on start" variable in the config for the user to modify. 

2. So when you use the feature in a position that is not possible for a human, it does not work as intended? I think I know what the problem is on that one . I do not have the knowledge to offset the direction based on location in the cockpit the players head is.

If you'd like to mod that in, you can find the relevant function, add + 2 to the direction right before the GetDevice command at the end of the function. Once you have done that you'll put in two more lines of code before that line. Make them if statements for 34 (or 340) to be 10 (or 010) and also 35 (or 350) to be 20 (or 020). Example:

If direction == 35 then direction = 2 end.

I'll consider putting in a heading2face fine tune variable in the config fir the user to modify. 

[swartbyron]

Quote

I'll consider putting a "hide on start" variable in the config for the user to modify. 

Thanks, I was just about to ask if you could make that an option.

[Bailey]

KIO-WA v0.5 Released: https://github.com/asherao/KIO-WA/releases

v0.5 Update Notes
- Hide on Launch option is available via the config file
- App window will no longer automatically re-show itself after game is resumed
- Heading 2 Face offset is available via the config file. Positive values are right, negative values are left, in degrees.
- Aircraft will fly straight when Course/Route button middle mouse clicked (DCS-ism improvement)
- Hotkeys can be changed via the config file
- Fixed a condition where when 000/360 was commanded, Barundus would set heading to MMS instead
- If you set the app window to be too big or small, it will be juuust right on the next DCS restart

[GrEaSeLiTeNiN]

2 hours ago, Bailey said:

KIO-WA v0.5 Released: https://github.com/asherao/KIO-WA/releases

v0.5 Update Notes
- Hide on Launch option is available via the config file
- App window will no longer automatically re-show itself after game is resumed
- Heading 2 Face offset is available via the config file. Positive values are right, negative values are left, in degrees.
- Aircraft will fly straight when Course/Route button middle mouse clicked (DCS-ism improvement)
- Hotkeys can be changed via the config file
- Fixed a condition where when 000/360 was commanded, Barundus would set heading to MMS instead
- If you set the app window to be too big or small, it will be juuust right on the next DCS restart

- Looks to me like the HDG2FACE was fixed? I mean it looks right now when I check from the 'center seat'. I like it.
- I note the Altitude adjustment is always in Baro. Without the HUD it's hard to know how many feet to set when flying low. Is there a way the Alt adjustment could correspond to Baro or Radar depending on the type of flight mode selected, ie. BARO vs RADALT? 
- Can the speed and degrees of turn be in increments of 5 instead of 10 (perhaps adjustable in config)?
- Can the Alt increment be in increments of 5 until 100, then in 10 until 500, then in 100s onwards (perhaps adjustable in config)?
- The app shows up if you press Ctrl+Shift+F9 when flying any module. Anyway to restrict it to just the Kiowa?
Sorry for making so many requests! Appreciate the effort in making this.
  

Edited June 20, 2024 by GrEaSeLiTeNiN

[Bailey]

11 minutes ago, GrEaSeLiTeNiN said:

- Looks to me like the HDG2FACE was fixed? I mean it looks right now when I check from the 'center seat'. I like it.
- I note the Altitude adjustment is always in Baro. Without the HUD it's hard to know how many feet to set when flying low. Is there a way the Alt adjustment could correspond to Baro or Radar depending on the type of flight mode selected, ie. BARO vs RADALT? 
- Can the speed and degrees of turn be in increments of 5 instead of 10 (perhaps adjustable in config)?
- Can the Alt increment be in increments of 5 until 100, then in 10 until 500, then in 100s onwards (perhaps adjustable in config)?
Sorry for making so many requests! Appreciate the effort in making this.
  

1) If heading2face was fixed, so be it! Yes, I did change some logic. 

2) I'm not quite sure what you mean by this one about the altitude. Are you asking that when Terrain flight is selected, that the altitude select changes to the lower selectable altitudes?

3) Unable due to Kiowa developer limitations. 

4) Unable due to Kiowa developer limitations. 

I appreciate the requests. It makes the app better for all!

[GrEaSeLiTeNiN]

18 minutes ago, Bailey said:

2) I'm not quite sure what you mean by this one about the altitude. Are you asking that when Terrain flight is selected, that the altitude select changes to the lower selectable altitudes?

Ok so when I change the Altitude button value, it is currently always with respect to barometric altitude. So if say I am 200ft above ground (AGL) and I want to go to 100ft, I have to know what it is in barometric altitude before I can change the value (granted the AI will not do it if I select a value that means flying into the ground).

My suggestion was:  Say I select RADALT flight mode (low level terrain flight profile), then the Altitude button value/increment now uses radar altitude (AGL) values. And if I select BARO flight mode (straight level flying), then the Altitude button value switches to use barometric values. Alternatively, and more simply, maybe a center mouse click could toggle between Baro and Radar values in the Altitude button. For example, when on a hill, say the Altitude value is currently set at Radar altitude of "R300ft" -> I click the scroll button and it coverts to -> "B1500ft" barometric.  

Another thing - The app shows up if you press Ctrl+Shift+F9 when flying any module. Anyway to restrict it to just the Kiowa?

Edited June 20, 2024 by GrEaSeLiTeNiN

[Bailey]

38 minutes ago, GrEaSeLiTeNiN said:

Ok so when I change the Altitude button value, it is currently always with respect to barometric altitude. So if say I am 200ft above ground (AGL) and I want to go to 100ft, I have to know what it is in barometric altitude before I can change the value (granted the AI will not do it if I select a value that means flying into the ground).

My suggestion was:  Say I select RADALT flight mode (low level terrain flight profile), then the Altitude button value/increment now uses radar altitude (AGL) values. And if I select BARO flight mode (straight level flying), then the Altitude button value switches to use barometric values. Alternatively, and more simply, maybe a center mouse click could toggle between Baro and Radar values in the Altitude button. For example, when on a hill, say the Altitude value is currently set at Radar altitude of "R300ft" -> I click the scroll button and it coverts to -> "B1500ft" barometric.  

Another thing - The app shows up if you press Ctrl+Shift+F9 when flying any module. Anyway to restrict it to just the Kiowa?

 

I don't have the same behavior you describe with baro vs terrain altitudes. Example: I load into the free flight on Caucasus mission. Click hover. Click hud. Click Baro to go into baro mode. Command 50 ft. Barundus will try to descend into the ground. Click radalt mode. Command 50ft. Barundus will climb to 50 ft. Do you not have the same behavior? (Which brings up an interesting point. Maybe I can check if Barundus will try to CFIT and prevent that....

I believe I could restrict it to the kiowa... it may have some effect of not being able to be seen in any game menu. I'll take a look. 

[Bailey]

CFIT avoidance will be in a future update. Currently seeing if I  can change the color of the button for commands that would result in CFIT. At the moment Barundus will just ignore your command. 

Spoiler

v0.6 (WIP)
- Barundus will ignore CFIT (Controlled Flight Into Terrain) Baro altitude commands
- Commands that would result in CFIT can be enabled via the config file
- Commands that would result in CFIT can be be given using the middle mouse button on the altitude button

 

[Bailey]

6 hours ago, Bailey said:

CFIT avoidance will be in a future update. Currently seeing if I  can change the color of the button for commands that would result in CFIT. At the moment Barundus will just ignore your command. 

  Reveal hidden contents

v0.6 (WIP)
- Barundus will ignore CFIT (Controlled Flight Into Terrain) Baro altitude commands
- Commands that would result in CFIT can be enabled via the config file
- Commands that would result in CFIT can be be given using the middle mouse button on the altitude button

 

This is currently live for people who want to test it before the v0.6 release. I also changed the location of some buttons. As usual, with updates remember to delete your config file.

Edited June 20, 2024 by Bailey

[GrEaSeLiTeNiN]

On 6/20/2024 at 10:29 PM, Bailey said:

I don't have the same behavior you describe with baro vs terrain altitudes. Example: I load into the free flight on Caucasus mission. Click hover. Click hud. Click Baro to go into baro mode. Command 50 ft. Barundus will try to descend into the ground. Click radalt mode. Command 50ft. Barundus will climb to 50 ft. Do you not have the same behavior? (Which brings up an interesting point. Maybe I can check if Barundus will try to CFIT and prevent that....

I believe I could restrict it to the kiowa... it may have some effect of not being able to be seen in any game menu. I'll take a look. 

Update:

1. In South Atlantic test: Altitude button works as you described whether in Hover, Cruise or Orbit. If I watch the HUD's AGL and Baro, AI will follow the set altitude value according to which flight mode was selected whether RADALT or BARO. And the AI will not stop a CFIT. 

2. BUT in Syria test: When reducing altitude nearer to ground, AI often says "You want me to do what?!" or "Hey I can't do that". I'm not sure why when it does not appear to be a CFIT. What am I missing? Here is a video recording I did. Whenever the AI says he can't comply to say 20ft RADALT (= 600ft BARO in this case) via the overlay, he will do it if I use the DCS bindings.  

Edited June 22, 2024 by GrEaSeLiTeNiN

[Gideon312]

4 hours ago, GrEaSeLiTeNiN said:

2. BUT in Syria test: When reducing altitude nearer to ground, AI often says "You want me to do what?!" or "Hey I can't do that". I'm not sure why when it does not appear to be a CFIT. What am I missing? Here is a video recording I did. While the AI it can't do say 20ft AGL, I can still do it manually using the DCS bindings.  

 

I’ve got the same issue in the Caucasus map, for example airbase Sukhumi.

[Bailey]

6 hours ago, GrEaSeLiTeNiN said:

Update:

1. In South Atlantic test: Altitude button works as you described whether in Hover, Cruise or Orbit. If I watch the HUD's AGL and Baro, AI will follow the set altitude value according to which flight mode was selected whether RADALT or BARO. And the AI will not stop a CFIT. 

2. BUT in Syria test: When reducing altitude nearer to ground, AI often says "You want me to do what?!" or "Hey I can't do that". I'm not sure why when it does not appear to be a CFIT. What am I missing? Here is a video recording I did. Whenever the AI says he can't comply to say 20ft RADALT (= 600ft BARO in this case) via the overlay, he will do it if I use the DCS bindings.  

 

 

1 hour ago, Gideon312 said:

I’ve got the same issue in the Caucasus map, for example airbase Sukhumi.

I have just realized that due to a last minute issue, I had actually commented out the CFIT feature. Oops. Sorry about that. Expect another update soon. If you could test again, that would be great. I'll let yall know when it is ready.

[Bailey]

@GrEaSeLiTeNiN, it should be good now. Give CFIT a shot when you have time.

[Bailey]

Here is what it is lookin' like. This version is on the Git right now (not yet officially released). Altitude will turn red when Barundus thinks the altitude change will result in CFIT.

Edited June 21, 2024 by Bailey

[GrEaSeLiTeNiN]

1 hour ago, Bailey said:

Here is what it is lookin' like. This version is on the Git right now (not yet officially released). Altitude will turn red when Barundus thinks the altitude change will result in CFIT.

 

Deleted old Config file. Replaced with updated (raw) lua and dlg files. Tested in Syria map.
- RADALT seems to be working fine.
- Ground level is about 525ft BARO in my test. When BARO is selected, selecting 500ft turns the button white (not red) so I can't see the text. I guess it's working just that the button colour isn't right. There is no speech from Barundas when he does not accept the value (when button is white). Maybe he could say "Can't do that" for some audio feedback. But I note that if using DCS bindings, Barundas also doesn't say anything and he actually proceeds with CFIT values.  

Edited June 21, 2024 by GrEaSeLiTeNiN

[Bailey]

11 hours ago, GrEaSeLiTeNiN said:

Deleted old Config file. Replaced with updated (raw) lua and dlg files. Tested in Syria map.
- RADALT seems to be working fine.
- Ground level is about 525ft BARO in my test. When BARO is selected, selecting 500ft turns the button white (not red) so I can't see the text. I guess it's working just that the button colour isn't right. There is no speech from Barundas when he does not accept the value (when button is white). Maybe he could say "Can't do that" for some audio feedback. But I note that if using DCS bindings, Barundas also doesn't say anything and he actually proceeds with CFIT values.  

 

Correct, I cannot find a "No can do" sound clip. If I get a clean one, there is a chance I can add it to the profile in a similar way that I can play sounds using DCS-Walkman. 

It's good to hear that everything is working, except the color. That is an easier fix for the future. 

Edited June 22, 2024 by Bailey

[Bailey]

11 hours ago, GrEaSeLiTeNiN said:

Deleted old Config file. Replaced with updated (raw) lua and dlg files. Tested in Syria map.
- RADALT seems to be working fine.
- Ground level is about 525ft BARO in my test. When BARO is selected, selecting 500ft turns the button white (not red) so I can't see the text. I guess it's working just that the button colour isn't right. There is no speech from Barundas when he does not accept the value (when button is white). Maybe he could say "Can't do that" for some audio feedback. But I note that if using DCS bindings, Barundas also doesn't say anything and he actually proceeds with CFIT values.  

 

Red button made red.  It is available.

[Gideon312]

1 hour ago, Bailey said:

Red button made red.  It is available.

Is the new version available? Can’t find it. Looking forward to try the latest one. I really enjoy the mod.

[Bailey]

23 minutes ago, Gideon312 said:

Is the new version available? Can’t find it. Looking forward to try the latest one. I really enjoy the mod.

It is available to those who want to download the source code and try things out before the public version release. While it is updated more often, there are times when unexpected things could happen. If you would like to be at the forefront of development assistance, go ahead and download the source by going here https://github.com/asherao/KIO-WA, clicking the CODE dropdown, and downloading the zip. 

12 hours ago, GrEaSeLiTeNiN said:

Deleted old Config file. Replaced with updated (raw) lua and dlg files. Tested in Syria map.
- RADALT seems to be working fine.
- Ground level is about 525ft BARO in my test. When BARO is selected, selecting 500ft turns the button white (not red) so I can't see the text. I guess it's working just that the button colour isn't right. There is no speech from Barundas when he does not accept the value (when button is white). Maybe he could say "Can't do that" for some audio feedback. But I note that if using DCS bindings, Barundas also doesn't say anything and he actually proceeds with CFIT values.  

 

Speaking of, I have uploaded a new source version titled "added Barundus CFIT audio". When Barundus does not agree with an altitude command, he will say so! Make sure to download the whole zip because there are audio files now. 

Thanks for this idea!!!

Unless something else pops up, I don't mind making this a public release soon.

Edited June 22, 2024 by Bailey

[GrEaSeLiTeNiN]

Tested the latest build in the same Syria environment where ground level is 525ft.
- In BARO mode, all is good. Button turns red for anything at or below 500ft with AI speech feedback.  
- But in RADALT mode, AI won't agree to anything at or below 500ft. The button does not turn red but there is AI speech feedback. I think this happens because the app thinks it is still in BARO mode. 

[Bailey]

1 hour ago, GrEaSeLiTeNiN said:

Tested the latest build in the same Syria environment where ground level is 525ft.
- In BARO mode, all is good. Button turns red for anything at or below 500ft with AI speech feedback.  
- But in RADALT mode, AI won't agree to anything at or below 500ft. The button does not turn red but there is AI speech feedback. I think this happens because the app thinks it is still in BARO mode. 

1) Baro mode working, awesome.

2) Ater getting no agree from the AI, try using the same keybind. In the app I don't run any logic for RADALT because any RADALT change should not result in CFIT. I can try when I have time. Would you like to attach the miz?

Note: The app cannot track the modes of the AI. The app can only track itself. This may cause issues...

Edited June 22, 2024 by Bailey