Jump to content

Shark Planner: waypoint entry into Ka-50 ABRIS and PVI-800 from F10

okopanja

By okopanja
in DCS Modding

 Share

Recommended Posts

  • 2 months later...
okopanja

okopanja

Posted
  • Author
Posted (edited)

v1.6.0

Improvements in Waypoint list and Crosshair information + important bug fixes.

What's Changed

  • Features
    • [Crosshair] display of coordinates and altitudes by @okopanja in #120
    • [Crosshair] display of object model by @okopanja in #131
    • [Waypoint list] Allow altitude change by @okopanja in #121
    • [Waypoint list] Reordering of waypoints/fixpoints/targetpoints (Drag&Drop) by @okopanja in #124
    • [Internal] Implement internal camera interface by @okopanja in #119
  • Bugfixes
    • [Hotkeys] Fixed issue with hotkeys by @okopanja in #114
    • [JF-17] Fixed clearing of waypoints by @okopanja in #129
    • [JF-17] Prevent selection of non existing waypoint in JF-17 by @okopanja in #123
    • [Internal] Remove inspect utility from camera.lua by @okopanja in #127

Full Changelog: v1.5.2...v1.6.0

 

image.png


Edited by okopanja
  • Like 3
  • Thanks 1
Link to comment
Share on other sites
  • 1 month later...
okopanja

okopanja

Posted
  • Author
Posted
On 4/20/2024 at 11:20 PM, Tank33 said:

Would you be able to implement this for UH-60L?

I would need to take a look. I installed the mode once for the co-op mission and got surprised at the level of details of the mod. If the mod implemented the key entry it should be fairly easy.

A developer can even do this for arbitrary module on his/her own:

https://github.com/okopanja/SharkPlanner/tree/main/Development

2 hours ago, Xtorris said:

This is amazing! Thank you!

Is there any way to have Shark Planner name the waypoints, which are entered into the ABRIS?

I would state that by far ABRIS is the weirdest input device in whole DCS. It can have very complex states especially when it comes to the selected items inside menu (it sadly remembers the positions of them, so each time I use them I need to return them to original state for subsequent use).

Waypoints are auto-numbered. In PVI-800 they are designated with numbers and there can be up to 6 of them, hence I limited the entry of max 6 of them. Since they are auto-numbered there is not much point into designating them as text. Each waypoint can be also edited with planned speed, altitude and wind information.

However it is is possible to enter the annotation "objects" and they can be named in ABRIS. Here I face the problem that the entry is done via dials which are finicky, and already now this is not 100% reliable due to:

- non-deterministic time needed for UI to update

- inability to always determine if there is already an object surface covered with designation ABRIS cursor.

- inability to query the exact state of the UI of ABRIS device (more or less it's a blind entry, although I did hard effort to utilize what little information it provides)

Also I would need to fix the following issue first: https://github.com/okopanja/SharkPlanner/issues/108

Even then I can not promis anything and at best the feature may get added as Experimental (non-active by default) since ti can affect the stability of entry.

Link to comment
Share on other sites
Xtorris

Xtorris

Posted
Posted
4 hours ago, okopanja said:

I would state that by far ABRIS is the weirdest input device in whole DCS.

Don't sweat it then, man. Your mod cuts down on a huge majority of the ABRIS input, as it is, and me assigning names to the ABRIS waypoints give me something to do while the PVI-800 aligns.

Link to comment
Share on other sites
  • 4 weeks later...
okopanja

okopanja

Posted
  • Author
Posted (edited)
On 4/20/2024 at 11:20 PM, Tank33 said:

Would you be able to implement this for UH-60L?

I was working on UH-60L entry support. However, I encountered a something that confuses me.

On page 60 and 61 they state that the waypoint can be cycled with INC/DEC or entered numerically in WPT DIST/BRG TIME display.

However, I found out that in WP/TGT page, while still not in keyboard entry mode I can enter the numerically 2 digits, which changes the upper underlined digit group.

INC/DEC changes the lower one.

Do you know what is the first digit group used for?

image.png


Edited by okopanja
Link to comment
Share on other sites
Tank33

Tank33

Posted
Posted (edited)

I believe the first line is showing the waypoint number that is currently chosen for navigation.

When you are adding a new waypoint, you just have to change the waypoint number on the 2nd line and enter coordinates on the WP/TGT page.

Some missions might have pre-assigned waypoints already on the 60L system and might be better to choose a starting number something like 50+

The easiest sequence would be:

1. Select WP/TGT page

2. Enter desired waypoint number to add by pressing the numer on the keypad. like 5 and 1 for 51 (this will change the waypoint number on the first line)

3. Press KYBD then press CLR to match the waypoint number on the 2nd line to the one you entered previously

4. Enter coordinates

 

 


Edited by Tank33
Link to comment
Share on other sites
okopanja

okopanja

Posted
  • Author
Posted (edited)
On 5/17/2024 at 1:36 PM, Tank33 said:

I believe the first line is showing the waypoint number that is currently chosen for navigation.

When you are adding a new waypoint, you just have to change the waypoint number on the 2nd line and enter coordinates on the WP/TGT page.

Some missions might have pre-assigned waypoints already on the 60L system and might be better to choose a starting number something like 50+

The easiest sequence would be:

1. Select WP/TGT page

2. Enter desired waypoint number to add by pressing the numer on the keypad. like 5 and 1 for 51 (this will change the waypoint number on the first line)

3. Press KYBD then press CLR to match the waypoint number on the 2nd line to the one you entered previously

4. Enter coordinates

 

 

 

First of all I have a working implementation but I am not 100% happy with it: at the moment it utilizes the INC/DEC button to position entry from #1 (after entry it cycles back).  If the user cycles himself this will not work properly anymore.

BTW: at the moment I did not have the need for textual descriptions (might be nice and useful in Ka-50, but it may reduce reliability of entry). At the moment I will not implement this since it would require changing the UI and make the waypoint list wider. I will check if it is feasible to get nearest populated place for automatic entry instead.

I think there are exactly 100 flight plans (0 comes from mission editor) each with up to 70 points, point 0 is starting position and at the moment I do not touch this one. I am not sure but I think that first line might be a flight plan.

I will try to experiment today again and based on your feedback check if I can deterministically perform entry even if users plays with waypoint numbers.

I might have more time over next 2 weeks, but will not bring hotas/headtracker with me.

 

 

 


Edited by okopanja
corrected assumption
Link to comment
Share on other sites
okopanja

okopanja

Posted
  • Author
Posted (edited)

v1.6.1

Important bugfix + first non official module

What's Changed

Full Changelog: v1.6.0...v1.6.1

@Tank33Please review the documentation (I did add nearest place for waypoint!), I am not an expert user of Black Hawk. But it appears that HSI bearing wheel is the only way to change the heading.


Edited by okopanja
  • Like 1
Link to comment
Share on other sites
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...