Comrade Doge

There is no logic really, the system is not complete, hopefully it will be solved. This is the issue, we are not talking about IFF here, there is no issue about the ROE System (changing classification), the issue is with track correlation (filling the hollow Link16 symbols). It is possible to have a correlated Hostile track without NCTR print, because that track has already been established as Hostile (ROE has already been applied by whomever has donated that symbol over Link 16), now all that's left is to do correlation when FCR sees it (fill up the symbol). I will gladly provide more details in DMs if desired.

The key here is that there are 2 different topics, one is the track correlation (what this topic is about), and the other is ROE Tree. ED thinks we are talking about ROE Tree, but in reality the problem is with the correlation only (which is irrespective of the 2 factor argument). Maybe one day this will be revisited.

Yes this is in the plans for the Apache, the more I fly it the sooner I'm gonna make it Make sure you are not actually creating a mark point, that would be represented as a cross on the HSD. Generally if you don't choose too higher STPT numbers you won't run into the mark point data bank

Hello, could you DM me a video of the issue? Thanks Hello, if you are not using VR you could try the alternate crosshair option in the settings, until I figure out a fix

Yes I am aware, unfortunately these days I have been busy with things, i will take a look at it. I wouldn't be too worried since it only happens when you try to close the game anyways, but thanks for the heads up

Hi, please DM me, maybe it's an installation issue

Hello, please DM me your dcs.log and we'll continue there

in my opinion this is wrong, since you can have a hostile track without 2 factor being needed from your ownship. Real manuals even offer an example of this. You only need 2 factor if you want to change ROE to hostile, from other classifications. But not the opposite, when it's already Hostile on the HSD. Waiting for ED to acknowledge this issue

Hello, for the F16 you can manually increment to a steer point of yoir choice and then hit transfer, and it will enter the new steerpoints after the one you had selected.

Hello, the export.lua seems correct, make sure you also have the folder TheWay (which has the lua files) inside the Scrips folder, next to the Export.lua

Glad you solved it!

Weird, I haven't seen this before, if you can DM me your dcs log, Export.lua file and the contents of the Scripts folder, maybe there's a missing link there. No. It only enters it into the PVI-800

Hi, I don't really understand what you mean by "repeat", could you detail the issue? Or maybe attach a video of it and DM me your dcs.log and the Scripts folder.

Hello, turns out I made a small mistake in the code and some keybinds weren't working, please update to the newest version found here which fixes the issues. To update to this version, just run the new installer.

Check the GitHub readme https://github.com/aronCiucu/DCSTheWay#how-to-install

Hello all, new update for the program, this time to add features for VR users in particular. Warning: If you are updating from an older version, remove all traces of TheWay, including TheWay.lua file and the Export.lua line, and then follow the new install instructions in the README This release adds heavily demanded features to aid VR players, such as: New crosshair system that will show in VR as well (no need for other mods to achieve this functionality,like Scratchpad) The new crosshair also works well with multiple monitor setups Added ability to customize keybinds to perform different actions (such as toggling crosshair, saving points etc). Open the settings to assign them. Ability to input a waypoint file without DCS open Added C130 Hercules support thanks to @Summit60 . Make sure to install the Patch for the C130, linked here. You can find the release link here. Make sure you follow the new install instructions! The old Lua files you may have installed will not work anymore! Hello, I'd suggest trying out the newest version, remove all traces of TheWay including the lua files and follow the new install instructions

Best to wait for the next version which will always display on the DCS monitor

Hello, try the following: start the mission again and do not change any steer points in the module by yourself, let TheWay to everything from the beginning. If that doesn't work, go into the program settings and increase the button delay, and see how it fares. If it still doesn't work, PM me a video of the issue. I have tested the F16 numerous times myself and it should work just fine.

I have plans for the future to improve the VR behavior, and not require additional mods You can PM me and I can help you find the issue

I recently got VR as well, I will try to come up with a solution if possible. For now, planning with the goggles off or use the keybinds

Hello everyone, here is a new update, bringing new features and bugfixes: Added a settings page where you can change various options Option to select crosshair color Option to disable program being always on top Added ability to make button inputs slower, in case waypoints are not entered correctly Fixed issue with Ka-50 Ability to select waypoints in spectator mode Download here Make sure to also update your TheWay.lua file with the new one! I'd also like to thank everyone for reaching over 20K downloads of the program!

Hello, I'm glad you enjoy it. As for the Eagle features, I for one am not too familiar with all the routing options, perhaps if one of our contributors who's more knowledgeable will find time for this. Unlikely, as the JF already had these features implemented natively It is already supported in the latest version

I see, I will try to make it so that the crosshair will show on the monitor that contains the DCS instance.

Hello, which display is set as primary inside windows? The crosshair should be shown on that one

Hello, must have missed it, interesting request. If I find the time necessary, I must find a proper UI implementation that won't clutter the interface. In the meantime, you can try saving the points to files, for the target and nav options, then import each of them when needed.