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

[Barrios]

It looks and works very well in VR on an MP server, it has no impact on performance.

[Bailey]

3 hours ago, Barrios said:

It looks and works very well in VR on an MP server, it has no impact on performance.

Yahoo! Thanks for letting us know! Enjoy! It was a fun project. Maybe we can see more from devs or modders in this regard for hard to reach panels. 

[Andy2828]

You rock, bro!! Well done!!

 

[Bailey]

4 hours ago, Barrios said:

It looks and works very well in VR on an MP server, it has no impact on performance.

Can I use this screenshot for the first post and github?

[Bailey]

MFK overlay updated. Version 0.2 released!
https://github.com/asherao/kiowa-mfk-overlay/releases

v0.2
- Left click "Kiowa MFK Overlay" sticker to toggle app size
- Right click "Kiowa MFK Overlay" sticker to hide app
- User toggle hotkey will be displayed at the top of the app, even if customized
- Enabled Config Settings via `KiowaMfkOverlayConfig.lua`
  - hideToggleHotkey: edit this to change the toggle hotkey
  - hideOnLaunch: toggle to hide the app on launch of DCS
  - appSize: 0 is full MFK, 1 is only numpad and logo
  - buttonPressTime: time in ms that the buttons are pressed by the program

[GrEaSeLiTeNiN]

On 6/23/2024 at 11:50 AM, 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.   

Hi Bailey, any fix on this? Such a nice app. 

For info, on (2) even if I avoid clicking on the AI Pilot (Off/On/Off) button but use the key bind instead, the same problem happens to the app.  

[Bailey]

41 minutes ago, GrEaSeLiTeNiN said:

Hi Bailey, any fix on this? Such a nice app. 

For info, on (2) even if I avoid clicking on the AI Pilot (Off/On/Off) button but use the key bind instead, the same problem happens to the app.  

I believe that the issue comes from when the AI is turned ON, it defaults and changes to Baro mode. The app did not account for that. So what I have done is that when the AI is toggled, the app selects baro mode and checks for CFIT. Give it a try. Download the MAIN, not the release to test this. Thanks for the video.

Edited July 2, 2024 by Bailey

[Barrios]

hace 8 horas, Bailey dijo:

Can I use this screenshot for the first post and github?

Yes, of course

[jnr4817]

@Bailey anyway we could lock the ai overlay to the bottom or top of the keyboard? 

I’ve never exported anything to an iPad or tablet need to figure this out. What resources are available I can look at?

[GrEaSeLiTeNiN]

9 hours ago, Bailey said:

I believe that the issue comes from when the AI is turned ON, it defaults and changes to Baro mode. The app did not account for that. So what I have done is that when the AI is toggled, the app selects baro mode and checks for CFIT. Give it a try. Download the MAIN, not the release to test this. Thanks for the video.

 

Downloaded the fix. Tested using Syria map -> KIO-WA Test Syria.miz
Unfortunately, the above reported issues (1) and (2) remain, no change. 
Have you tried it?

Edited July 2, 2024 by GrEaSeLiTeNiN

[Bailey]

1 hour ago, GrEaSeLiTeNiN said:

Downloaded the fix. Tested using Syria map -> KIO-WA Test Syria.miz
Unfortunately, the above reported issues (1) and (2) remain, no change. 
Have you tried it?

 

In 1 post, can you explain how to replicate with step by step click/action instructions?

1 hour ago, jnr4817 said:

@Bailey anyway we could lock the ai overlay to the bottom or top of the keyboard? 

I’ve never exported anything to an iPad or tablet need to figure this out. What resources are available I can look at?

Install both overlays. Run DCS. Close DCS. Edit the config of both overlays to have the same hotkey. Start DCS. Put one above the other.

For the export, a google search will yield good results to start.

[GrEaSeLiTeNiN]

7 hours ago, Bailey said:

In 1 post, can you explain how to replicate with step by step click/action instructions?

Actually it is very simple to reproduce. Anytime you click AI Pilot OFF and back ON while in the air, the problem will happen. And it will happen whether you click the green Overlay button or use the key binds. I just discovered that if I want to avoid this problem, I have to land on the ground first before I click AI Pilot OFF or ON. And once this problem occurs, the other problem with REL ALT will also start, where it adds 2500ft instead of 50ft. You can try it with the attached mission file.   KIO-WA Test Syria.miz 

Edited July 3, 2024 by GrEaSeLiTeNiN

[firefox121]

A silly question, is it posible to create at UI or at kiowa controls setup two bindable controls for this overlais, so I can bind Them to a joystick button to enable or disable the viewing.

Don`t know how can it must be done.

 

[Bailey]

1 hour ago, firefox121 said:

A silly question, is it posible to create at UI or at kiowa controls setup two bindable controls for this overlais, so I can bind Them to a joystick button to enable or disable the viewing.

Don`t know how can it must be done.

 

Use a joystick software such as Voice Attack to translate joystick presses to keyboard presses. Make that keyboard press the on/off hotkey for the overlay. 

[firefox121]

hace 19 horas, Bailey dijo:

Use a joystick software such as Voice Attack to translate joystick presses to keyboard presses. Make that keyboard press the on/off hotkey for the overlay. 

I actually use joytokey, but it really will be acool feature to can assign it on the controls setup. Thakns, see some post where people assgin keys on functions, but can't figure it out

Things like this stuff but really don't know how to put this on the UI input control page.

{down = 3022, up = 3022, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Jettison Fuse 2-Pos ARM/DISARM'), category = _('Ins Weapons Status and Control Panel PUI-800')},

or if it is even possible.

Thanks in advance

[Bailey]

5 hours ago, firefox121 said:

I actually use joytokey, but it really will be acool feature to can assign it on the controls setup. Thakns, see some post where people assgin keys on functions, but can't figure it out

Things like this stuff but really don't know how to put this on the UI input control page.

{down = 3022, up = 3022, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Jettison Fuse 2-Pos ARM/DISARM'), category = _('Ins Weapons Status and Control Panel PUI-800')},

or if it is even possible.

Thanks in advance

I also don't know if it is possible. 

[Gideon312]

On 7/3/2024 at 2:01 AM, GrEaSeLiTeNiN said:

Actually it is very simple to reproduce. Anytime you click AI Pilot OFF and back ON while in the air, the problem will happen. And it will happen whether you click the green Overlay button or use the key binds. I just discovered that if I want to avoid this problem, I have to land on the ground first before I click AI Pilot OFF or ON. And once this problem occurs, the other problem with REL ALT will also start, where it adds 2500ft instead of 50ft. You can try it with the attached mission file.   KIO-WA Test Syria.miz 

 

I've been experiencing the same issues as GrEaSeLiTeNiN with the AI pilot.

But to add an extra issue, I've noticed that when I turn the AI pilot OFF and then ON again, and attempt to climb or descend by +/- 50 feet, the aircraft continues to climb or descend beyond the desired altitude. This has been quite frustrating, especially during critical phases of flight, specifically when you want to mask yourself behind a cover.

After some troubleshooting, I found a workaround that seems to mitigate this issue. By cycling the ALT button between BARO and RDR, the AI pilot appears to stabilize and responds correctly to altitude adjustments.

Additionally, for finer control, I would love to have the option to adjust altitude in increments of 10 feet rather than 50 feet. This would greatly enhance precision in (for example) battle positions.

 

Edited July 5, 2024 by Gideon312

[Bailey]

1 hour ago, Gideon312 said:

I've been experiencing the same issues as GrEaSeLiTeNiN with the AI pilot.

But to add an extra issue, I've noticed that when I turn the AI pilot OFF and then ON again, and attempt to climb or descend by +/- 50 feet, the aircraft continues to climb or descend beyond the desired altitude. This has been quite frustrating, especially during critical phases of flight, specifically when you want to mask yourself behind a cover.

After some troubleshooting, I found a workaround that seems to mitigate this issue. By cycling the ALT button between BARO and RDR, the AI pilot appears to stabilize and responds correctly to altitude adjustments.

Additionally, for finer control, I would love to have the option to adjust altitude in increments of 10 feet rather than 50 feet. This would greatly enhance precision in (for example) battle positions.

 

For the first part, can you give me a click by click way to reproduce the issue?

For the second part, thanks for the workaround. 

For the third part, modify the config file to change the altitude step amount. You can get info about other things you can change via the readme: https://github.com/asherao/KIO-WA?tab=readme-ov-file#config

Edited July 5, 2024 by Bailey

[Gideon312]

1 hour ago, Bailey said:

For the first part, can you give me a click by click way to reproduce the issue?

For the second part, thanks for the workaround. 

For the third part, modify the config file to change the altitude step amount. You can get info about other things you can change via the readme: https://github.com/asherao/KIO-WA?tab=readme-ov-file#config

 

. Here is a step-by-step explanation of how to reproduce the problem:

1. **Initial Setup:**
   - Start by entering the cockpit.
   - Allow the AI pilot to take control.

2. **First Hover and RAD Altitude Adjustment:**
   - Let the AI pilot hover the aircraft.
   - Use the RAD altimeter to change the altitude. The AI pilot should respond appropriately and adjust the altitude as instructed.

3. **Manual Control and Battle Position:**
   - Take manual control of the aircraft.
   - Fly to a designated battle position.

4. **Second Hover and RAD Altitude Issue:**
   - Hand over control to the AI pilot again.
   - The AI pilot should enter a hover normally.
   - Attempt to set a specific RAD altitude by scrolling to the desired altitude and left-clicking on it.

**Observed Issue:**
- The AI pilot responds with, “You want me to do what?” and does not adjust to the specific RAD altitude. After engaging the AI pilot for the second (or more) time.
- Additionally (the other mentioned issue), the AI pilot tends to climb higher than the specified +50 feet altitude.

**Reproduction Steps:**
1. AI pilot - hover (2nd time)
2. Scroll to a (RAD) altitude
3. Left-click on the (scrolled) altitude —> “you want me to do what?”

By following these steps, the issue should be reproducible. If anyone has insights or suggestions on how to fix this, your help would be greatly appreciated!

Thanks in advance!

---

I hope this helps in explaining the issue clearly. If you need further assistance, feel free to ask!

 

Thanks for the heads-up on changing values.

Edited July 5, 2024 by Gideon312

[markturner1960]

Great app Bailey, however I have another issue.....I dont use a normal mouse, instead, I use a trackball, so it has no middle mouse button.....this gives me issues with using drift left or drift right as I am unable to stop the drift except by drifting in the opposite direction....so I never become fully stopped.......

Any ideas how to work around this? Thanks! 

[Bailey]

9 hours ago, markturner1960 said:

Great app Bailey, however I have another issue.....I dont use a normal mouse, instead, I use a trackball, so it has no middle mouse button.....this gives me issues with using drift left or drift right as I am unable to stop the drift except by drifting in the opposite direction....so I never become fully stopped.......

Any ideas how to work around this? Thanks! 

Drift is in equal increments. One click left will be canceled by one click right, and so on. You can also toggle the autopilot. 

[Bailey]

12 hours ago, Gideon312 said:

. Here is a step-by-step explanation of how to reproduce the problem:

1. **Initial Setup:**
   - Start by entering the cockpit.
   - Allow the AI pilot to take control.

2. **First Hover and RAD Altitude Adjustment:**
   - Let the AI pilot hover the aircraft.
   - Use the RAD altimeter to change the altitude. The AI pilot should respond appropriately and adjust the altitude as instructed.

3. **Manual Control and Battle Position:**
   - Take manual control of the aircraft.
   - Fly to a designated battle position.

4. **Second Hover and RAD Altitude Issue:**
   - Hand over control to the AI pilot again.
   - The AI pilot should enter a hover normally.
   - Attempt to set a specific RAD altitude by scrolling to the desired altitude and left-clicking on it.

**Observed Issue:**
- The AI pilot responds with, “You want me to do what?” and does not adjust to the specific RAD altitude. After engaging the AI pilot for the second (or more) time.
- Additionally (the other mentioned issue), the AI pilot tends to climb higher than the specified +50 feet altitude.

**Reproduction Steps:**
1. AI pilot - hover (2nd time)
2. Scroll to a (RAD) altitude
3. Left-click on the (scrolled) altitude —> “you want me to do what?”

By following these steps, the issue should be reproducible. If anyone has insights or suggestions on how to fix this, your help would be greatly appreciated!

Thanks in advance!

---

I hope this helps in explaining the issue clearly. If you need further assistance, feel free to ask!

 

Thanks for the heads-up on changing values.

 

Can you test this with what is in the current code in the release branch of the git. With the main branch as it currently is, you would have to toggle Barundus into RadAlt after turning it back on. The default is now baro. The steps you have don't seem to reflect that. 

[Gideon312]

5 hours ago, Bailey said:

Can you test this with what is in the current code in the release branch of the git. With the main branch as it currently is, you would have to toggle Barundus into RadAlt after turning it back on. The default is now baro. The steps you have don't seem to reflect that. 

Double checked if I use the latest build (with fix for DCS defaulting to BARO)

I was pretty sure I toggled it yesterday, did it anyway for this test;

BUT --> started the instant action free flight in the CAU map.

Whenever I LAND and toggle Barandus off and on, the RAD alt which I select works as intended. (and it doesn't matter where I fly to)

BUT

Whenever I fly to a certain point and let Barandus take over in AIR (so not landing), the issue (below) comes up. After this point, it doesn't matter if I land --> toggle Barandus ON / OFF, toggle BARO / RAD ALT.

**Reproduction Steps:**
1. AI pilot take over IN AIR - hover (or fly (it doesn't matter))

2. Cycle BARO -RADALT (at some point even with more than one attempt)
3. Scroll to a (RAD) altitude
4. Left-click on the (scrolled) altitude —> “you want me to do what?”

Edited July 6, 2024 by Gideon312

[GrEaSeLiTeNiN]

1 hour ago, Gideon312 said:

Double checked if I use the latest build (with fix for DCS defaulting to BARO)

I was pretty sure I toggled it yesterday, did it anyway for this test;

BUT --> started the instant action free flight in the CAU map.

Whenever I LAND and toggle Barandus off and on, the RAD alt which I select works as intended. (and it doesn't matter where I fly to)

BUT

Whenever I fly to a certain point and let Barandus take over in AIR (so not landing), the issue (below) comes up. After this point, it doesn't matter if I land --> toggle Barandus ON / OFF, toggle BARO / RAD ALT.

**Reproduction Steps:**
1. AI pilot take over IN AIR - hover (or fly (it doesn't matter))

2. Cycle BARO -RADALT (at some point even with more than one attempt)
3. Scroll to a (RAD) altitude
4. Left-click on the (scrolled) altitude —> “you want me to do what?”

Yep, as I have been saying in my earlier post. Double-click AI Pilot button (or use key binds) when in air and the problem starts -> the RAD thinks it is BARO and you can tell because it won't go below the BARO value for ground level. Select any value higher than BARO ground value (while in RAD) and AI will comply. Once this problem starts, it can't be resolved and it adds another problem which is when I select say REL ALT +50, it adds 2500ft instead of 50ft when in RAD (watch it go up). The only way to avoid this problem from happening in the Overlay is be on the ground whenever you want to turn the AI Pilot ON or OFF.     
 

Edited July 6, 2024 by GrEaSeLiTeNiN

[Bailey]

1 hour ago, Gideon312 said:

Double checked if I use the latest build (with fix for DCS defaulting to BARO)

I was pretty sure I toggled it yesterday, did it anyway for this test;

BUT --> started the instant action free flight in the CAU map.

Whenever I LAND and toggle Barandus off and on, the RAD alt which I select works as intended. (and it doesn't matter where I fly to)

BUT

Whenever I fly to a certain point and let Barandus take over in AIR (so not landing), the issue (below) comes up. After this point, it doesn't matter if I land --> toggle Barandus ON / OFF, toggle BARO / RAD ALT.

**Reproduction Steps:**
1. AI pilot take over IN AIR - hover (or fly (it doesn't matter))

2. Cycle BARO -RADALT (at some point even with more than one attempt)
3. Scroll to a (RAD) altitude
4. Left-click on the (scrolled) altitude —> “you want me to do what?”

 

May I ask a favour and do the reproduction steps with DCS keybinds only? Is the result the same as the app?