Comrade Doge

Hello, try starting theway again and opening/closing the crosshair. It should reset itself. Hello, TheWay can save the waypoints to a file, as well as being transferred in the jet. Simply click the download icon in the bottom left corner to save the waypoints in a json format. It should work if you hold ctrl, then hold shift, and then the next key. If it doesn't, PM me and we'll take a closer look

The correlation is real between the FCR and the Link, and when both of those see the same target, the position atribute is taken from the FCR (since it's more accurate) but the Link 16 fills up the rest of the information, such as identification. In any case, new threads could be made on this issue, and I and others will happily help with further clarification

The identification requirements/ROE tree are a different subject than the basic track correlation that should occur here. Since there was no additional identification performed by the FCR (no NCTR scan was performed), there is no reason that an existing Hostile track would become Suspect, or mipple back and forth between the two. If however, the NCTR would have indicated a different print other than hostile specific ones, indeed that would be the case. But as we know that is not what's happening here, a simple sweep of the radar over a target immediately changes the ROE of Hostile tracks to Suspect, which makes no sense whatsoever. The expected behavior would be, upon painting a hostile track with the radar, that it would correlate into a hostile track as well, and only if there exists other evidence that the same track might not be hostile (such as NCTR), then we can talk about how to display other indications.

Yes, ED believes it is correct as is and not a bug. Me and some other folks are very open to discussing the issue with publicly available information with ED, if they decide to revisit the issue. For instance, even from the official manual, the FCR has no authority to change ROE, but when seeing a datalink target with the FCR, the ROE changes from hostile to suspect still. A pretty obvious contradiction even at first glance.

It is established by available documents that the red to yellow track correlation behavior is incorrect. Now we are waiting for ED to acknowledge this, one day, hopefully...

@Willie NelsonSince I see you are using TheWay mod, make sure to update it to the latest version found here. The older versions had a habit of causing crashes when exiting the game.

Hello everyone, the issue was found, it was due to a problem in the mod TheWay, which I have created. This has now been fixed in the most recent version found here. There will not be any crashes when exiting the game anymore. My apologies for the confusion.

Hello everyone, the issue was found, it was due to a problem in the mod TheWay, which I have created. This has now been fixed in the most recent version found here. There will not be any crashes when exiting the game anymore. My apologies for the confusion.

Hello everyone, please check the newest release with the following bugfixes: Fixed crash on exiting DCS Fixed not being able to select waypoints on water using keybinds 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 modified files. Then, run the new installer. No need to modify the Export.lua file. Download link here: https://github.com/aronCiucu/DCSTheWay/releases/tag/v2.4.2

You may revisit the classification tree as well, but that's not what this topic is about

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