Transfer steerpoints from the F10 map into the aircraft - DCS: The Way

[MadKreator]

11 hours ago, jonsky7 said:

Done!

https://github.com/jonsky752/DCSTheWay/releases/tag/v2.5.6
 

Changed from 2 options:

1. Add to Flightplan
2. Make a New Flightplan

to 4 options:

1. Add to Flightplan
2. Make a New Flightplan
3. Add to Alternate Flightplan
4. Make a New Alternate Flightplan

Cheers
Jon

Oh awesome! You are the man. Thank you so much, as always!

[jonsky7]

ED have made some changes to the clickable data file for the Chinook, mainly all of the button codes for the CDU's have changed.

Update can be found:

https://github.com/jonsky752/DCSTheWay/releases/tag/v2.5.7

[MadKreator]

2 hours ago, jonsky7 said:

ED have made some changes to the clickable data file for the Chinook, mainly all of the button codes for the CDU's have changed.

Update can be found:

https://github.com/jonsky752/DCSTheWay/releases/tag/v2.5.7

I spent a good couple hours this morning reworking the helios interface for every button on both CDU’s and re-working the exports for the chinook rwr and adding one for the f-5 remaster. For just fixing the 3 cdu buttons that needed fixed, I feel like they didn’t NEED to remap the entirety of the CDU(s)

[Gil80]

how do you bring up the interface? and how do you hide when you're done with waypoints?

[Habu_69]

theWay 2.5.7: After saving my navigation waypoints I have a keybind to transfer those WP to the Hornet. With 2.5.7, however, I must now break VR and alt-tab to The Way so I can answer the "Input PP YES NO" question prior to commanding the transfer. Does a more convenient procedure exist?? A YES/NO keybind would be a big help.

I have watched the YouTube vid on how to use the new Hornet weapon coordinate input procedure, but the vid has no verbal instructions and I am a little confused. AFAIK one must

1. Transfer the mission navigation waypoints to the jet.
2. Clear those WP from theWay window.
3. Save (or retrieve from a file) the desired weapon coordinates as a new set of WP in theWay.
4. Navigate the MFD to the Weapon/MSN/PP# page.
5. Initiate coordinate transfer.
6. Answer INPUT PP question YES. 

Is this the proper/best procedure?

Edited December 20, 2024 by Habu_69

[jonsky7]

5 hours ago, Gil80 said:

how do you bring up the interface? and how do you hide when you're done with waypoints?

Not sure what you mean, are you using VR?
I run the app, TheWay app window opens. If I click on the Green + button, I get a crosshair appears in the middle of my screen, hit the save button to create a waypoint based on the crosshair.
If you run VR, I think you can minimize the app and use the keybinds to save and then transfer waypoints. I don't really use VR so I'm not 100% sure on how it works.

 

 

2 hours ago, Habu_69 said:

theWay 2.5.7: After saving my navigation waypoints I have a keybind to transfer those WP to the Hornet. With 2.5.7, however, I must now break VR and alt-tab to The Way so I can answer the "Input PP YES NO" question prior to commanding the transfer. Is their a more convenient procedure to do this?? A YES/NO keybind would be a big help.

I have watched the YouTube vid on how to use the new Hornet weapon coordinate input procedure, but the vid has no verbal instructions and I am a little confused. AFAIK one must

1. Transfer the mission navigation waypoints to the jet.
2. Clear those WP from theWay window.
3. Save (or retrieve from a file) the desired weapon coordinates as a new set of WP in theWay.
4. Navigate the MFD to the Weapon/MSN/PP# page.
5. Initiate coordinate transfer.
6. Answer INPUT PP question YES. 

Is this the proper/best procedure?

Hmm yeah, sorry, this hadn't crossed my mind as I don't use VR. I will have a look to see if I can implement keybinds for the options, but it may be beyond what I'm capable of.
So far I've managed to create the extra options needed in the list of keybinds, and selected binds seem to save, but I'm stumbling on getting the option to select when the keys are pressed, this may take a while.

As for the procedure, at the moment that seems to be the only way to do it. Or transfer the same points twice, once into nav points, and a second time into the weapons. 
Do you think a "both" option would be beneficial? So TheWay transfers the same points into the Jet and Weapons on the click of the transfer button. That I may be able to do. It would however just transfer the points twice.

I won't be able to look at it until after the holidays I'm afraid.

Edited December 20, 2024 by jonsky7

[Habu_69]

2 hours ago, jonsky7 said:

Or transfer the same points twice, once into nav points, and a second time into the weapons. 
Do you think a "both" option would be beneficial? So TheWay transfers the same points into the Jet and Weapons on the click of the transfer button.

I guess a BOTH option would be beneficial, but how does the jet know which WP are for nav and which for Weps? The keybinds are higher priority IMO, if at all possible. Appreciate your efforts. Merry Christmas.

[Gil80]

16 hours ago, jonsky7 said:

Not sure what you mean, are you using VR?
I run the app, TheWay app window opens. If I click on the Green + button, I get a crosshair appears in the middle of my screen, hit the save button to create a waypoint based on the crosshair.
If you run VR, I think you can minimize the app and use the keybinds to save and then transfer waypoints. I don't really use VR so I'm not 100% sure on how it works.

 

 

Hmm yeah, sorry, this hadn't crossed my mind as I don't use VR. I will have a look to see if I can implement keybinds for the options, but it may be beyond what I'm capable of.
So far I've managed to create the extra options needed in the list of keybinds, and selected binds seem to save, but I'm stumbling on getting the option to select when the keys are pressed, this may take a while.

As for the procedure, at the moment that seems to be the only way to do it. Or transfer the same points twice, once into nav points, and a second time into the weapons. 
Do you think a "both" option would be beneficial? So TheWay transfers the same points into the Jet and Weapons on the click of the transfer button. That I may be able to do. It would however just transfer the points twice.

I won't be able to look at it until after the holidays I'm afraid.

Yes, I use VR.

Have you seen how scratchpad works? Clicking ctrl+<profanity>+x brings up the UI in VR to eneter coordinates.

I was hoping this would behave the same.

[jonsky7]

15 hours ago, Habu_69 said:

I guess a BOTH option would be beneficial, but how does the jet know which WP are for nav and which for Weps? The keybinds are higher priority IMO, if at all possible. Appreciate your efforts. Merry Christmas.

It wouldn't really, just if you want to enter the same waypoints as both nav points and weapon points i could probably get it to do both on one transfer.

What I'm usually doing is programming the weapons to drop on multiple targets in the same area, then I delete all but one of the points and enter that as nav/steerpoint to get me close enough for release.

If you're planning at route through a valley or something, and then having completely different weapon points, then I think that will always require two transfers.

You can always use the now built in route planner for your steerpoints, and just use theway for you weapon points.

Merry Christmas to you.

 

2 hours ago, Gil80 said:

Yes, I use VR.

Have you seen how scratchpad works? Clicking ctrl+<profanity>+x brings up the UI in VR to eneter coordinates.

I was hoping this would behave the same.

I'm not the original author of this program, and I have very limited coding knowledge. I just found other people had made some modifications that I found useful. I used the supplied source code to build a version with all those modifications built into it and just thought I'd share it.

Most of it is far beyond my coding abilities if I'm honest.

[Habu_69]

3 hours ago, jonsky7 said:

What I'm usually doing is programming the weapons to drop on multiple targets in the same area, then I delete all but one of the points and enter that as nav/steerpoint to get me close enough for release.

My use case is flying the Hornet in VR on public multi-player servers where ground target locations are only generally known and the player has no opportunity to use the ME route planning feature. Route and target planning are done on the F10 map in the game. I have therefore reverted to version 2.4.2, which suits my needs.

[1BRAVO9]

 

First of all, I would like to thank the developer of this app/mod or whatever you want to call.

This thing rocks!! I have been using it for a year or so and I love it, it even works with the F-15E.

Recently I go to the F10 map and plot my waypoint using the green dot, but after I return to the cockpit the green dot remains on the screen and will not disappear until the end of that match.

Is anyone else having this issue?

Second, any possibility of it working for the F-15C? I'm sure this has been asked and answered but I missed, sorry if so.:)

 

 

[jonsky7]

9 hours ago, 1BRAVO9 said:

 

First of all, I would like to thank the developer of this app/mod or whatever you want to call.

This thing rocks!! I have been using it for a year or so and I love it, it even works with the F-15E.

Recently I go to the F10 map and plot my waypoint using the green dot, but after I return to the cockpit the green dot remains on the screen and will not disappear until the end of that match.

Is anyone else having this issue?

Second, any possibility of it working for the F-15C? I'm sure this has been asked and answered but I missed, sorry if so.:)

 

 

To make the cursor dot dissappear  press the "add waypoints" button again after you are done adding waypoints. Just for clarification, that's the circle button with a + in it, it changes to an X.

It's not possible to make it work with the F15C, IIRC there's no way to manually enter waypoints into it. The new-ish built in route planning tool may be of use to you for that, but that only works before you spawn.

[1BRAVO9]

15 minutes ago, jonsky7 said:

To make the cursor dot dissappear  press the "add waypoints" button again after you are done adding waypoints. Just for clarification, that's the circle button with a + in it, it changes to an X.

It's not possible to make it work with the F15C, IIRC there's no way to manually enter waypoints into it. The new-ish built in route planning tool may be of use to you for that, but that only works before you spawn.

That did it, thanks!!

This is an awesome app.

[Eggcake]

Maybe I'm acting a bit stupid, but I installed it and it seems to work, but when I select "Transfer to DCS", it seems to not enter the coordinates correctly. I am currently flying the F16. It does not enter anything in "Lat" but I think tries to enter everything in "Lng".

I'm sure I missed something but currently can't figure out what.

[jonsky7]

1 hour ago, Eggcake said:

Maybe I'm acting a bit stupid, but I installed it and it seems to work, but when I select "Transfer to DCS", it seems to not enter the coordinates correctly. I am currently flying the F16. It does not enter anything in "Lat" but I think tries to enter everything in "Lng".

I'm sure I missed something but currently can't figure out what.

Which version have you downloaded?

[Eggcake]

1 hour ago, jonsky7 said:

Which version have you downloaded?

Ah, I see - I downloaded 2.50 from the first page but I see you have your own GitHub page. Will try the latest one from yours!

 

Tried the newest version, and still have the issue. I made a short video.

Edited January 15 by Eggcake

[jonsky7]

4 hours ago, Eggcake said:

Ah, I see - I downloaded 2.50 from the first page but I see you have your own GitHub page. Will try the latest one from yours!

 

Tried the newest version, and still have the issue. I made a short video.

I've just tested it on mine, seems to be working ok

The button entry speed seems very fast on your video, this can be an issue if you are running very high framerates.

If you click on the settings cog in TheWay window and scroll down you will see a 
Button Press Delay, try setting this to maximum (100ms) and see if it works then.

If that does the trick, you can always try lower delays until the issue arises again, then just increase the delay a bit again.

Or

Try limiting the frame rate (FPS) 

Edited January 16 by jonsky7

[Eggcake]

17 hours ago, jonsky7 said:

I've just tested it on mine, seems to be working ok

The button entry speed seems very fast on your video, this can be an issue if you are running very high framerates.

If you click on the settings cog in TheWay window and scroll down you will see a 
Button Press Delay, try setting this to maximum (100ms) and see if it works then.

If that does the trick, you can always try lower delays until the issue arises again, then just increase the delay a bit again.

Or

Try limiting the frame rate (FPS) 

Thank you for looking into it.

 

I increased it to 100ms and limited FPS to 30 but it still seems to be the same.

 

Edited January 16 by Eggcake

[jonsky7]

4 hours ago, Eggcake said:

Thank you for looking into it.

 

I increased it to 100ms and limited FPS to 30 but it still seems to be the same.

 

It looks like you are on a multiplayer sever so I'm assuming you are on the latest version of DCS?

I ask because there was a change to the F16 steerpoint entry. TheWay just follows a set routine for getting the waypoints into the jet, and it looks like the routine for yours is different to mine. Your DED cursor is not moving over to the MAN/AUTO select position.

Before the change it was dobber down once to go from the steerpoint number select, down to North coordinate entry.

After the change, dobber down once goes from steerpoint number select, to man/auto select, then dobber down again for North coordinate entry.

in pics 
On Sterrpoint number select

Dobber down once


Dobber down again

 

You can manually try to do the inputs in the same order as "TheWay" by:

1. Data Control Switch Left (Dobber RTN), this makes sure we are at the default screen showing comms freq, current steerpoint, and the time. 
2. UFC button 4/STPT, Steerpoint screen select
3. Data Entry Display Increment button (left of dobber up/down buttons - press up), increments to next steerpoint.
4. Dobber down - DED cursor moves to man/auto select
5. Dobber down - DED cursor moves to North coordinate select
6. Verify on North Coordinate selection.

Edited January 16 by jonsky7

[Eggcake]

Should be the latest version, yes: 2.9.11.4686 - I also did a full repair of everything.

Interesting, Dobber down does not move to man/auto for me. That explains it of course why it does not work, but why is it different for you (or me)?!

[VampireNZ]

11 hours ago, Eggcake said:

Should be the latest version, yes: 2.9.11.4686 - I also did a full repair of everything.

Interesting, Dobber down does not move to man/auto for me. That explains it of course why it does not work, but why is it different for you (or me)?!

Which # steerpoint are you trying to enter it as? I had the same problem as I was trying to add it as a SP in the 20's...can only add in number range 1-20. Steerpoint sequencing can only be changed in the SP range of 1-20. so it won't cycle over to MAN/AUTO for any other SP #. See the latest manual Pg 201 para 6.

It's not that the program specifically needs MAN/AUTO....but by being in a higher SP # it skips over an extra SEQ dobber as it can't get there so skips the first set of N co-ords instead.

 

I am actually having a problem with the keybind I use to Save a SP is registering multiple times so saving 2-4 of them. Tried increasing the Delay, even in the Config.json but no luck so far.

Awesome little program thou, exactly what I have been looking for!

Edited January 19 by VampireNZ

[Eggcake]

8 hours ago, VampireNZ said:

Which # steerpoint are you trying to enter it as? I had the same problem as I was trying to add it as a SP in the 20's...can only add in number range 1-20. Steerpoint sequencing can only be changed in the SP range of 1-20. so it won't cycle over to MAN/AUTO for any other SP #. See the latest manual Pg 201 para 6.

It's not that the program specifically needs MAN/AUTO....but by being in a higher SP # it skips over an extra SEQ dobber as it can't get there so skips the first set of N co-ords instead.

 

I am actually having a problem with the keybind I use to Save a SP is registering multiple times so saving 2-4 of them. Tried increasing the Delay, even in the Config.json but no luck so far.

Awesome little program thou, exactly what I have been looking for!

Thank you! That's it. Indeed, I used quite high SP# to enter my manual steerpoints.

 

Thanks all for the support. So it will work for SP 1-20, but not for anything above.

[VampireNZ]

2 hours ago, Eggcake said:

Thank you! That's it. Indeed, I used quite high SP# to enter my manual steerpoints.

 

Thanks all for the support. So it will work for SP 1-20, but not for anything above.

You're  welcome 

I am not a programming guru, but I imagine a simple fix would be to remove one of the initial automatic SEQ inputs if the SP # is above 20 - not sure if there is a way to incorporate that.

[jonsky7]

20 hours ago, Eggcake said:

Thank you! That's it. Indeed, I used quite high SP# to enter my manual steerpoints.

 

Thanks all for the support. So it will work for SP 1-20, but not for anything above.

 

17 hours ago, VampireNZ said:

You're  welcome 

I am not a programming guru, but I imagine a simple fix would be to remove one of the initial automatic SEQ inputs if the SP # is above 20 - not sure if there is a way to incorporate that.

 

So I was pondering on what the best solution for this was for a while, a special version that removed a dobber down action, an option select screen (VR people don't like those) etc.

When I was testing though, it's not ALL the Steerpoints 21 and above, somewhere in the 100's range, it goes back to being able to auto-sequence again(bug?) 

Then it occurred to me that if we simply dobber up from the Steerpoint number select instead of down, we can miss out the auto/man selection altogether.
Takes a fraction of second longer to enter 1 waypoint, shouldn't be any different at all for 2 or more because we had to go back to the start anyway.

So I present my version 2.5.8, which should do the waypoint entry regardless of the Steerpoint numbers used.
https://github.com/jonsky752/DCSTheWay/releases/tag/2.5.8 

No other changes from 2.5.7

Edited January 20 by jonsky7

[VampireNZ]

26 minutes ago, jonsky7 said:

 

 

So I was pondering on what the best solution for this was for a while, a special version that removed a dobber down action, an option select screen (VR people don't like those) etc.

When I was testing though, it's not ALL the Steerpoints 21 and above, somewhere in the 100's range, it goes back to being able to auto-sequence again(bug?) 

Then it occurred to me that if we simply dobber up from the Steerpoint number select instead of down, we can miss out the auto/man selection altogether.
Takes a fraction of second longer to enter 1 waypoint, shouldn't be any different at all for 2 or more because we had to go back to the start anyway.

So I present my version 2.5.8
https://github.com/jonsky752/DCSTheWay/releases/tag/2.5.8 

No other changes from 2.5.7

WOW, great job!