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

[Bailey]

38 minutes ago, Bailey said:

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...

 

Confirmed that using a mix of the app and keybinds for AI may cause a conflict. This "confusion" is correct when using the app again. 

As for the Baro issue you have seen, I tried on that map and I'm not seeing the same thing. Can you post a video?

[Bailey]

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?

[GrEaSeLiTeNiN]

On 6/22/2024 at 2:26 PM, Bailey said:

Confirmed that using a mix of the app and keybinds for AI may cause a conflict. This "confusion" is correct when using the app again. 

As for the Baro issue you have seen, I tried on that map and I'm not seeing the same thing. Can you post a video?

After some puzzling tests, I found the problem why RADALT works and then something happens and Barundas refuses to oblige. The problem happens when you click AI ON, then OFF, then ON. The problem is reproduceable but I can't get it corrected once it happens.
 

Edited June 24 by GrEaSeLiTeNiN

[Gideon312]

6 hours ago, Bailey said:

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?

For me:

Drift (=slide?) --> left mouse click hold --> drifting left --> left mouse click release --> stop drifting back to hover (visa versa)

Speed / altitude / incremental turns --> scroll mouse wheel --> add an extra button on the GUI to select the value

[Bailey]

17 minutes ago, Gideon312 said:

For me:

Drift (=slide?) --> left mouse click hold --> drifting left --> left mouse click release --> stop drifting back to hover (visa versa)

Speed / altitude / incremental turns --> scroll mouse wheel --> add an extra button on the GUI to select the value

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.

[Bailey]

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

[Gideon312]

1 hour ago, Bailey said:

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

Just tested this latest version, and it works like a charm. Awesome job and thanks for making it!

[Bailey]

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**

[GrEaSeLiTeNiN]

11 hours ago, Bailey said:

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**

1. AI Pilot ON -> OFF -> ON will still cause the Altitude setting in RADALT mode to be denied by Barundas if that requested setting falls below ground level BARO value. (App thinks it is in BARO mode.) << See video >> Once that happens, it cannot be corrected other than restarting the mission or selecting another Kiowa. When this problem happens, it sometimes turns the REL ALT button red with a certain value (not sure why). Once the REL ALT button turns red, it can't be undone except by exiting and reentering DCS. 

2. If I am testing 2 Kiowas in the same mission, jumping from one Kiowa to the other leaves the previous Kiowa bobbing up and down. Not sure if this is app related.

Other than that this release is great!

Edited June 23 by GrEaSeLiTeNiN

[Bailey]

6 hours ago, GrEaSeLiTeNiN said:

1. AI Pilot ON -> OFF -> ON will still cause the Altitude setting in RADALT mode to be denied by Barundas if that requested setting falls below ground level BARO value. (App thinks it is in BARO mode.) Once that happens, it cannot be corrected other than restarting the mission or selecting another Kiowa. When this problem happens, it sometimes turns the REL ALT button red with a certain value (not sure why). Once the REL ALT button turns red, it can't be undone except by exiting and reentering DCS. 

2. If I am testing 2 Kiowas in the same mission, jumping from one Kiowa to the other leaves the previous Kiowa bobbing up and down. Not sure if this is app related.

Other than that this release is great!

 

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!

Edited June 22 by Bailey

[GrEaSeLiTeNiN]

3 hours ago, Bailey said:

Does the middle mouse click override still work?

Middle mouse click to override works with BARO but not with RADALT once the problem (triggered by AI Pilot ON->OFF->ON) occurs.

Other tests:
BARO was set at 300ft. I right left clicked REL ALT of 50ft and helo went up all the way to 2800ft (added 2500ft instead of 50ft) << See video >>
BARO was set at 400ft. I right left clicked REL ALT of 50ft and helo went up all the way to 2900ft (added 2500ft instead of 50ft)
RADALT works fine with REL ALT

Edited June 23 by GrEaSeLiTeNiN

[Bailey]

1 hour ago, GrEaSeLiTeNiN said:

Middle mouse click to override works with BARO but not with RADALT once the problem (triggered by AI Pilot ON->OFF->ON) occurs.

Other tests:
BARO was set at 300ft. I right clicked REL ALT of 50ft and helo went up all the way to 2800ft (added 2500ft instead of 50ft)
BARO was set at 400ft. I right clicked REL ALT of 50ft and helo went up all the way to 2900ft (added 2500ft instead of 50ft)
RADALT works fine with REL ALT

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. 

[GrEaSeLiTeNiN]

1 hour ago, Bailey said:

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. 

1. Sorry in my earlier post on the BARO REL ALT issue, I should have said left-clicked, not right-clicked. Basically to add +50ft rel alt. But it added 2500ft instead.
See <<video>>. (Track replays do not show app button presses.)

2. Added a <<video>> showing that pressing AI pilot OFF-ON causes RADALT to function as BARO meaning:
(a) AI will reject inputs below BARO ground level value (250ft in this test), and middle-mouse click will not override it.
(b) REL ALT issue described above (1) will also start to happen with RADALT. 
(c) This problem could not be undone except by exiting and reflying mission, or choosing another Kiowa.   

[Bailey]

2 hours ago, GrEaSeLiTeNiN said:

1. Sorry in my earlier post on the BARO REL ALT issue, I should have said left-clicked, not right-clicked. Basically to add +50ft rel alt. But it added 2500ft instead.
See <<video>>. (Track replays do not show app button presses.)

2. Added a <<video>> showing that pressing AI pilot OFF-ON causes RADALT to function as BARO meaning:
(a) AI will reject inputs below BARO ground level value (250ft in this test), and middle-mouse click will not override it.
(b) REL ALT issue described above (1) will also start to happen with RADALT. 
(c) This problem could not be undone except by exiting and reflying mission, or choosing another Kiowa.   

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. 

Edited June 23 by Bailey

[GrEaSeLiTeNiN]

5 hours ago, Bailey said:

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. 

 

Unfortunately no, I tried pressing 3x BARO/RADALT and also AI ON/OFF and different combos, including using the DCS AI key binds to my hotas. Just can't seem to get it to reset and behave as it should (RADALT).

Edited June 23 by GrEaSeLiTeNiN

[Andy2828]

This is, like everything you do, outstanding. Ive had no issues using it in VR. Thank you!!

On a different yet similar note, can you make something like this for the cockpit keyboard? Where its at it is very hard to see, especially in VR. Something along the lines of what youve done above would really make things easier. 

[Bailey]

9 hours ago, Andy2828 said:

This is, like everything you do, outstanding. Ive had no issues using it in VR. Thank you!!

On a different yet similar note, can you make something like this for the cockpit keyboard? Where its at it is very hard to see, especially in VR. Something along the lines of what youve done above would really make things easier. 

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! 

Edited June 30 by Bailey

[Bailey]

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.

[Gideon312]

1 hour ago, Bailey said:

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.

Once again, I’m thoroughly impressed by your talent in creating another useful mod for the Kiowa. I’m really looking forward to seeing the final result!

[GrEaSeLiTeNiN]

Suggestion: Logo takes up one half of the empty space and the other half shows what you keyed in (like in a calculator) for visual confirmation. 

[Bailey]

2 hours ago, GrEaSeLiTeNiN said:

Suggestion: Logo takes up one half of the empty space and the other half shows what you keyed in (like in a calculator) for visual confirmation. 

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

[Bailey]

For the brave: https://github.com/asherao/kiowa-mfk-overlay. Let me know how it goes.

For those who like more complete builds and features, please wait till a public release. 

[Bailey]

[jnr4817]

Nice job. Anyway to export this to an Ipad or similar tablet for mounting in sim pit?

[Bailey]

1 hour ago, jnr4817 said:

Nice job. Anyway to export this to an Ipad or similar tablet for mounting in sim pit?

Other than the typical DCS export workarounds and apps, not that I know of.