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

[jonsky7]

4 hours ago, Comrade Doge said:

Hello, indeed I got some reports for it not working anymore, I will work on a fix as soon as I can

@Comrade Doge

This should fix the Harrier, done a bit of testing, seems to work.

I've just commented out some of the ODU Option 2 presses

AV8BNA.java

[Comrade Doge]

5 hours ago, jonsky7 said:

@Comrade Doge

This should fix the Harrier, done a bit of testing, seems to work.

I've just commented out some of the ODU Option 2 presses

AV8BNA.java 11.01 kB · 3 downloads

Hello, good work there! I will test it as soon as I can as well. I see some other changes as well, like the NAV master mode input being removed. Is that not required anymore?

[jonsky7]

8 hours ago, Comrade Doge said:

Hello, good work there! I will test it as soon as I can as well. I see some other changes as well, like the NAV master mode input being removed. Is that not required anymore?

No, Master mode does not have to be set to NAV mode for waypoint entry to work .

[Comrade Doge]

Hello all, I finally got to publishing the hotfix version, download it from here: https://github.com/aronCiucu/DCSTheWay/releases/tag/v1.4.1

[tech_op2000]

awesome, thanks

 

[Floydii]

@Comrade Doge

This is a great app, extremely helpful.

 

I note the earlier requests to get this working for FC3 modules, to which you correctly responded that waypoints can only be changed  in the mission editor but not in-mission.
However, I had a thought about making a "Poor Man's GPS" that allows FC3 aircraft to navigate based on points entered into your app. Sort of like the NS430, but without the fiddly knobs and obtuse interface. It would stay open during play and look much like the current TheWay interface window.

The concept is that your app would have a sub page that is basically a nav page based on the waypoints entered by the user. They could select one of the previously entered nav points as their destination and it would provide basic info such as:
 

• Current heading
• Heading to currently selected point
• A 'heading tape' made of characters* that emulates the one that we usually see at the top of the HUD.
• Distance to selected point
• Time to currently selected point in HH:MM:SS to current point
• Time of arrival at current point in HH:MM:SS
• Own aircraft bearing and range from bullseye (to allow players to provide bullseye calls).
• Own aircraft location in at least DD.MM.SS

 

* This heading tape would use text characters to give steering directions to the player:

• Currently heading directly to selected point: < - - - - 0 - - - - >
• Selected point is  slightly left of current heading: < - - 0 - | - - - - >
• Selected point is more than 25 degrees Right of current heading:  < - - - - | - - - - 0

The possibility exists to expand the functionality to include course between two points, use of different units, accounting for wind and automatic waypoint switching, but for the time being I would see this being used to get FC3 players accurately onto a steerpoint and allow them to use bullseye with other players. 

What this is dependent on is your App's current ability to capture steerpoints along with the ability to get the player's own location and speed over ground. I'm unsure of the specific projection DCS uses (to account for the curve of the earth) but once that is known its some maths to produce the navigation information.

What do you think? could it fit in your app?

[Comrade Doge]

6 hours ago, Floydii said:

@Comrade Doge

This is a great app, extremely helpful.

 

I note the earlier requests to get this working for FC3 modules, to which you correctly responded that waypoints can only be changed  in the mission editor but not in-mission.
However, I had a thought about making a "Poor Man's GPS" that allows FC3 aircraft to navigate based on points entered into your app. Sort of like the NS430, but without the fiddly knobs and obtuse interface. It would stay open during play and look much like the current TheWay interface window.

The concept is that your app would have a sub page that is basically a nav page based on the waypoints entered by the user. They could select one of the previously entered nav points as their destination and it would provide basic info such as:
 

• Current heading
• Heading to currently selected point
• A 'heading tape' made of characters* that emulates the one that we usually see at the top of the HUD.
• Distance to selected point
• Time to currently selected point in HH:MM:SS to current point
• Time of arrival at current point in HH:MM:SS
• Own aircraft bearing and range from bullseye (to allow players to provide bullseye calls).
• Own aircraft location in at least DD.MM.SS

 

* This heading tape would use text characters to give steering directions to the player:

• Currently heading directly to selected point: < - - - - 0 - - - - >
• Selected point is  slightly left of current heading: < - - 0 - | - - - - >
• Selected point is more than 25 degrees Right of current heading:  < - - - - | - - - - 0

The possibility exists to expand the functionality to include course between two points, use of different units, accounting for wind and automatic waypoint switching, but for the time being I would see this being used to get FC3 players accurately onto a steerpoint and allow them to use bullseye with other players. 

What this is dependent on is your App's current ability to capture steerpoints along with the ability to get the player's own location and speed over ground. I'm unsure of the specific projection DCS uses (to account for the curve of the earth) but once that is known its some maths to produce the navigation information.

What do you think? could it fit in your app?

Hello, that is a splendid suggestion, and would definitely make the life easier for FC3 pilots. It would require quite the bit of work to implement, and I'm not sure my expertise is sufficient to materialize it... I will remember the request however, not sure if it would come to fruition though... Cheers!

Edited January 12, 2022 by Comrade Doge

[C3PO]

Hello - has elevation data been implemented now? Many thanks for such a wonderful tool!

[Comrade Doge]

6 minutes ago, C3PO said:

Hello - has elevation data been implemented now? Many thanks for such a wonderful tool!

Hello, yes it has! Check out the latest release.

[C3PO]

Hi - has anyone tried this in VR ... don't see why it shouldn't work ... 

[okopanja]

3 hours ago, Comrade Doge said:

Hello, yes it has! Check out the latest release.

Can we have the ability to setup the default elevation increment, used to calculate the desired altitude, with ability to override this in table per waypoint, together with 3rd column displaying resulting altitude?

Is ABRIS entry feasible?

It looks like it would be dependent on scale of the map as well as repeat rate of knobs... This later I am not sure if it is constant on all devices...

Also Load/Save would be cool.

Edited January 21, 2022 by okopanja

[Comrade Doge]

5 minutes ago, okopanja said:

Can we have the ability to setup the default elevation increment, used to calculate the desired altitude, with ability to override this in table per waypoint, together with 3rd column displaying resulting altitude?

Is ABRIS entry feasible?

It looks like it would be dependent on scale of the map as well as repeat rate of knobs...

Also Load/Save would be cool.

 

These are all great features to implement, and people have indeed  requested them a great deal. However  at the moment it appears that my free time to develop them has become scarce (exams, study, things of that nature)... hopefully the situation will improve and I might find more occasions to work on those features in the future...

Edited January 21, 2022 by Comrade Doge

[okopanja]

Just now, Comrade Doge said:

These are all great features to implement, and people have indeed  requested them a great deal. However  at the moment it appears that my free time to develop them has become scarce... hopefully the situation will improve and I might find more occasions to work on those features in the future...

I might be able to directly contribute if my time allows. I looked at your code already.

- Load/Save is what I would call essential.

- Table + altitude modifications as highly recommended.

- ABRIS is nice to have. 

IDEA: in case of Ka-50 PVI can be fed step by step (for more than 6 waypoints).

Do you have any API reference on devices and commands?

[Comrade Doge]

4 minutes ago, okopanja said:

I might be able to directly contribute if my time allows. I looked at your code already.

- Load/Save is what I would call essential.

- Table + altitude modifications as highly recommended.

- ABRIS is nice to have. 

IDEA: in case of Ka-50 PVI can be fed step by step (for more than 6 waypoints).

Do you have any API reference on devices and commands?

I used the DCS-BIOS repo as a reference for all the device and command codes corresponding to all the switches. About the UI, I recently  posted a demo about how the new interface would look like, and that I would like to rebuild it someday in another language...

[okopanja]

6 minutes ago, Comrade Doge said:

I used the DCS-BIOS repo as a reference for all the device and command codes corresponding to all the switches. About the UI, I recently  posted a demo about how the new interface would look like, and that I would like to rebuild it someday in another language...

Will it be Electron based?

[Comrade Doge]

Just now, okopanja said:

Will it be Electron based?

That would be the plan indeed. I am looking at Electron + Vue.js for a rebuild, will be quite the task but when I find the free time I will look forward to finalizing it (I still need to learn some extra JS knowledge to make it work). I enjoy working on it when I can, and the project has taught me a good number of things so far.

[okopanja]

47 minutes ago, Comrade Doge said:

That would be the plan indeed. I am looking at Electron + Vue.js for a rebuild, will be quite the task but when I find the free time I will look forward to finalizing it (I still need to learn some extra JS knowledge to make it work). I enjoy working on it when I can, and the project has taught me a good number of things so far.

In that case it makes no sense for me to make further changes on existing code base...

[C3PO]

Sadly doesn’t work at all in VR … could anyone help implement?

[beewip]

Need help guys, I can not make it works, it's not detect my DCS.

I copy the theway.lua file inside the scripts folder on save games and add the line on export.lua like installation said but not its not connection between them.

What I am doing wrong?

 

 

[jonsky7]

32 minutes ago, beewip said:

Need help guys, I can not make it works, it's not detect my DCS.

I copy the theway.lua file inside the scripts folder on save games and add the line on export.lua like installation said but not its not connection between them.

What I am doing wrong?

 

Can you attach or copy the code from your exports.lua file?
I put TheWay as the first line in my export.lua file, as something seemed to be blocking it at one point (maybe the SRS line) , so my export.lua looks like this now

 

-- The Way
local TheWayLfs=require('lfs'); dofile(TheWayLfs.writedir()..'Scripts/TheWay.lua')

-- load the DCS ExportScript for DAC and Ikarus
dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]])

--DCS Bios
dofile(lfs.writedir()..[[Scripts\DCS-BIOS\BIOS.lua]])

--SRS
pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil);

Something else to try is to start DCS first, then start TheWay once DCS is up and running.

I find having a folder open when starting DCS makes it easier to ALT-TAB out of DCS, then I use Win+D to get to my desktop to enable me to start TheWay.

Edited January 25, 2022 by jonsky7

[beewip]

Ok I will make the change and put it first

 

 

 

[beewip]

mmm no change

 

[beewip]

Got this on the dcs log

[beewip]

mmm but if u check tacview got the same slash \Scritps/Tacview... I thinks its correct but l'll try to change it, let me see

[jonsky7]

2 minutes ago, beewip said:

mmm but if u check tacview got the same slash \Scritps/Tacview... I thinks its correct but l'll try to change it, let me see

You must have seen that post before I deleted it, I noticed tacview was the same, and indeed mine is the same way