Comrade Doge

Hi, for VR have you tried using the DCS 2D mirror to select the points on the map? This way you will also see the interface on the desktop alongside it

Hello, in the Export.lua file, try moving the line you added at the bottom of the file, after all the others. If this still doesn't work, PM me on the forums with your dcs.log

Hi, i will investigate on why some keys don't register, in the meantime for VR you can try going to the desktop view and using the DCS mirror that shows in 2D, and use TheWay interface from there like you would normally do.

Hello everyone, thanks to our GitHub contributors the OH-58 Kiowa is now supported! Check out the newest version here Important! To update to this version from an older one, replace your existing TheWay folder found in Saved Games/DCS/Scripts with the new one, overriding any existing files. Then, run the new installer. No need to modify the Export.lua file. To install from scratch, follow the installation instructions here

Hi, makre sure your route is being shown on the TSD from the SHOW menu. The OH Kiowa update is almost ready to be released

Very well written, here's to hope ED actually reads this with an open-minded attitude and takes these notes seriously.

Indeed weirdly enough the previous implementation was more realistic in regard of datalink correlation. But that's what we have at the moment, I just filter out Link 16 from the FCR by the means of IFF Outboard. This gets rid of the unrealistic implementation from the FCR.

F-16 GPS guided bombs are not so accurate at the moment, their accuracy can definitely deviate more than 10 meters, even with a perfect waypoint. If you want to test the accuracy of the waypoints, load one up on a known landmark, then point the TGP at it, it should be right on the spot. Also about the Kiowa, it's definitely planned for a release in the future

The fact that RWS SAM (a radar mode which only tracks the target every 1.5 seconds) has smoother tracking that STT (which tracks the target continously).

From what I know it's not possible to start at other numbers than from the beginning, not as target points. The F-15E code was written by other contributors so I'm not sure when it will change to accommodate that...

DM me your dcs.log

Yes the current DCS implementation is wrong. There are references that point to that, and despite ED telling us it's correct-as-is, there is no evidence we know of that backs up their claim, so it's probably bad manual interpretation. The primary issue lays in thinking that in order to fill up a symbol, the radar needs to do identification of some sort (NCTR), which is wrong. Filling up symbols (correlation) has nothing to do with identification, it just happens when the FCR sees the same target as the Link 16 net, at the same position in the sky. Thus, it turns a hollow symbol into a filled up one, retaining the original "color" of the symbol. This would be the correct behavior. No NCTR/IFF is required. It's as simple as radar sees target -> fills up the hollow symbol (whichever color it may be). Currently in DCS, for some unknown reason, this correlation also changes the color/identity, and it requires NCTR to change the color back to the original Link 16 one. Which does not make sense, as correlation/filling does not depend on NCTR as previously established. I think they've made this confusion by mixing up correlation (filling existing symbols) and identification (change symbol color by means of NCTR), 2 different concepts in the F-16, and slapped them together to result this mix. It's a slim chance it's gonna be fixed if you ask me, we've had this report ad-nauseaum without any progress. I just turn off Link 16 in the FCR by IFF Outboard, and only use the HSD to see Link 16.

No this is not right. Red filled triangle will show when there is a red hollow triangle on the network, and your radar sees that same target. No IFF / NCTR needed. Filled symbols simply mean your ownship radar sees the contact.

That contact should clearly correlate to show a green circle, as Link 16 declares it as such on the net, and ownship NCTR didn't provide a disagreement. It'll correlate right away to a friendly. Same logic should apply for Hostiles.

What do you mean by "Looking at the desktop?", all the application code is open source, and many others have contributed to it, if it would be a "nefarious app" it would have been pretty obvious. Also I've never heard of it being reported by Windows Defender ever, for all these years it's been distributed. But if so, other mods have also been flagged as such throughout history, and Windows Defender likes embellishing them with scary titles (perhaps to convince you to only use their Microsoft Store products).