Comrade Doge
-
Posts
350 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Comrade Doge
-
-
48 minutes ago, slowmover said:
Hello mates. I have installed the v.2.5.0 i have mapped the buttons. In 2d it works great the problem is at VR. I can not see the green dot , so i do not know which point on map i aim to transfer and also the Key bindings does not work.
Also as you see here, i opened dcs entered on apache and the application does not connect to DCS
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
-
3 hours ago, Sprool said:
New version with Kiowa support (big thanks!) works fine oon flat screen, but I cannot get it working in VR (Quest 2 headset). I tried the deault key bindings (ctrl+shift+s, ect.) and also tried changing settings to map my own keybinds but it will not pick up, store or transfer any thing. Its like my key presses are being ignored (in VR as well as flat screen). Did I miss a step?
Is <numpad Enter> a reserved keypress? I guess I may have had ctrl+shift+s apready mapped to something different, if I change it to ctrl+shift+w then it works, I just wanted to avoid having to do ctrl+shift+anything in vr as I cannot see the keys.
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 existingTheWayfolder found inSaved Games/DCS/Scriptswith the new one, overriding any existing files. Then, run the new installer. No need to modify theExport.luafile.To install from scratch, follow the installation instructions here
-
1
-
1
-
-
28 minutes ago, subseauk said:
Hi, I have installed "The Way" as directed and made a waypoint list, then imported into DCS AH64 all without issue. I then watched the data being input into the AH64 keyboard but nothing shows on the MFD map? I cannot see what the issue is, do you have any suggestions? I would also like to use this for the new OH Kiowa but it say it won't work, any thoughts? Thanks
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
-
2
-
-
Very well written, here's to hope ED actually reads this with an open-minded attitude and takes these notes seriously.
-
5
-
1
-
-
14 hours ago, Trojan said:
I remember at one point this functionality was at least closer to what @Comrade Doge is describing within DCS but has since changed. Even chucks guide details it as such in the datalink section of the guide. Have not read into the manuals myself recently, but I can say that It doesn’t make sense that the FCR would be this difficult to use due to a software/symbology issue when IRL it is a matter of life and death and could presumably be fairly easily changed / updated.
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.
-
2
-
-
1 hour ago, firehorse said:
Not Accurate new version.
For some reason accuracy is way off even when zooming in to select target.
I reinstalled the older version of the way to test and it too now is not accurate. (it used to be dead on)
For some reason the gbu38's hit 10m away from the targets, always.
INS done, NAV selected in F16.
Have tried reinstallation for both the way versions and tried various zoom to target selects but still crappy accuracy.
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
-
16 hours ago, NineLine said:
What are you basing this is wrong on if I may ask as the team will indeed ask me.
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).
-
11 hours ago, Str][ker said:
Hi! I managed to get it working. I had some odd issue which impacted SRS as well. I did a full slow repair and that seemed to resolve the issue. I then reinstalled The Way and all works. Thank you for offering to help!
While I have your attention, is there a way to modify the waypoints being used in the strike eagle? It defaults to 1A (or 1B) but there's no way to tell it to start at something like 50 and to set waypoints as a target (i.e. 50. or 1.) Just curious if this was possible and i'm missing something.
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...
-
3 hours ago, Str][ker said:
Wanted to try this again. Installed the latest. Followed the instructions but I am getting the no connection to DCS error..
Export.lua is good. TheWay folder is in Scripts. Any suggestions for troubleshooting?
DM me your dcs.log
-
3 hours ago, Nedum said:
So, the current behavior in DCS is wrong?
I have by 100 % to bug and NCTR a target before it's turning fully red. Even if I turn my radar off, all tracks are fulfilled. Maybe this could be the current radar bug, but I don't know.
When my radar sees the hollow triangle, it turns to a full yellow square, and only if I NTCR the bugged contact, the yellow square turns to a fulfilled red triangle.
All !!not!! friendly contacts turn instantly into a yellow fulfilled square, as soon my radar see them. Only "friendly" contacts turn into white fulfilled squares from time to time, like RyanR shows.
But all that makes in no way any sense. How can my radar without any NTCR or IFF decide what kind of object the contact is? How do I get all the different colors, if there is no way the radar can say it's a Hostile, Unknown, or Suspect Target? And again, In what situation should I see the hollowed out squares (white and yellow)?
I never saw hollow squares with the datalink connected. No matter the radar is on or off.
The current way in what situation the contacts became a special symbolic, makes in no way any sense to me.
Without the Datalink I can see much more details for my tracks.
I can see if a target is a tracked target, a system target or a bugged target. With datalink on, I can't see this anymore, and that is total BS in my eyes.
How can I see what targets are system or bugged targets? All the good things I get without datalink are gone, but why? And why is the NTCR or IFF not necessary anymore?
Is there a manual that explains my questions? The current F16 manual doesn't do it.
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.
-
4
-
2
-
-
12 hours ago, Nedum said:
Maybe I understand something wrong (and that often
).
If the contact is a friendly in the same datalink network, or the information comes from an AWACS, the contact should be shown as a green circle, as long as I didn't track the contact (s.d.).
Is the following right?
All filled symbols are only shown, if I track the same target and the following happens:
Red filled triangle: I did an IFF scan (TMS long left), and the scan shows an enemy, and another datalink bro has the same result.
White filled square: I track the target, my IFF check shows inv, and the same happens for another datalink sender.
Yellow filled square: The result of my scan of the tracked target and the one of the datalink sender is different.
Green filled circle (dot): My result of the same track and the result from datalink sender show it's a friendly.
What I want to know. In which situations should I see hollowed out yellow squares? What must happen to see this symbolic?
As I understand, the difference during an active datalink is, I am not tracking the tracks. I only get the information from the datalink senders.
If this is right, why I always see filled out yellow or white squares as long I am a member of a datalink, even I have locked nothing?
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.
-
2
-
-
11 hours ago, 71st_Mastiff said:
incorrect installation, looks like you placed the whole .exe program into your script folder, doesnt working like that.
delete the files you placed in there and run the program from the desktop.
there also seems to be a nefarious issue with this app, its looking at my desktop all the time?
uninstalled; I'm guessing widows defender was right...
it identified it as ransom ware.
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).
-
1
-
-
On 3/25/2024 at 8:37 PM, minimi66 said:
Hey guys,
Just installed today and all working ok other than the little green crosshair dot won't go away even after closing The Way app?
Its still perched smack dab in the middle of my DCS screen? Using the Toggle Crosshair hotkey (CTL-ALT-X) i set up does nothing either?
Any ideas?
Thanks.
Hello, try starting theway again and opening/closing the crosshair. It should reset itself.
On 3/27/2024 at 7:12 PM, PeeJott17 said:@Comrade DogeThis is one piece of very cool software. Thanks a lot. Makes waypoint-editing sooo much more fun
(and a lot less painful). I was wondering how you transfer the waypoints into the planes systems. I'm one of the Devs from VSN and your App would come in very handy for our F-4B/C and upcoming standalone Mods for multiplayer use. Right now, we are reading the waypoints from the mission itself. Is there a possibility to read the waypoints from TheWay somehow? It transfer the waypoints somewhere and I guess they do not get set in the mission 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.
1 hour ago, Cobb said:How do we set up the CTRL + SHIFT + (key)? I can get the CTRL or SHIFT to show in the Keybindings setup, but not both.
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
-
40 minutes ago, skywalker22 said:
I would like to know just one thing, is there or is there not a real correlation between datalink contact and FCR contact, regarding its location (X,Y,Z) so FCR know exactly about which contact is getting the info from Datalink? If not, then ED is right, if yes, then I don't see any reason why FCR would create its only picture of contacts and therefore firing solutions (appropriate color desigantion of System and Bugged targets).
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
-
3
-
-
On 3/25/2024 at 1:09 PM, WHOGX5 said:
This is not entirely correct, but rather a slight misunderstanding of the manuals.
What happens in real life is that when a pilot hops his aircraft he will load different identification requirements from his DTC which specifies what makes a track be classified as friendly or hostile using his onboard sensors. One important thing to note, is that the F-16CM-50 is unable to correlate IFF information to tracks, so any IFF response requirements in the identification requirements will only be taken from interrogations performed by other aircraft on the same target, transmitted via LINK 16. So a hostile ID requirement could be that the target has to be of type MIG-29 and have a negative Mode 4 IFF response. Then you can determine the aircraft type with NCTR using your own radar, and if some other aircraft on your LINK 16 network has interrogated that same target, correlated it to the track, and sent that Mode 4 response back onto the network, then that target will show up as hostile on your FCR.
Now, if there is a disagreement between a track identity on the LINK 16 network and the identity which has been determined for that same correlated track by your own aircraft, then the track will mipple (flash) between the two different identities to show the pilot that there is an ambiguity there. Since ID requirements aren't necessarily the same on the LINK 16 network and in your own aircraft, you can have all kinds of ID disagreements even with the exact same information about the track in question.
Also, what the manual means when it says that the FCR has no authority to change ROE, they literally mean that what is displayed on your FCR doesn't in any way override the rules-of-engagement which have been set by the commanders and generals leading the war. Just because something has been ID'd as hostile in your aircraft, does not mean that it actually is hostile or that you're cleared to fire at it. In the same way, just because something shows up as an unknown, does not mean it's not hostile or that you're not allowed to fire at it. You can have a situation where you have identified the aircraft type via NCTR, you have performed an Mode 4 interrogation which came back negative but isn't correlated to the track so it still shows as unknown, yet you have still fulfilled theatre ROE requirements and are allowed to fire at the target.
So yeah, the main issue in the DCS F-16C regarding this specific aspect of the symbology is that correlated tracks don't mipple back and forth between the different track identities if there is a disagreement in identity between your own onboard sensors and what is supplied via LINK 16.
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.
-
3
-
-
5 hours ago, Willie Nelson said:
Perhaps incorrect but not a bug….is that what you’re trying to say?
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.
-
4
-
-
2 hours ago, Opesher said:
Hello. To put it into two cents and make response useful to other people who may read this, I will get into some context.
With F-16C's radar you have four types of contact symbols:
- Search Target: FCR has detected a contact, but the contact has not been up for long enough for radar to build a track on it. It's reprecented by a small rectangle with a line indicating aspect (hot/cold).
- Track Target: After some time, if the contact has not disappeared, FCR has resolved contact well enough to generate track data. It's reprecented by a solid square with more details available. Radar does it automatically.
- System Target: Pilot-designated (TMS Up above contact) track targets. It's reprecented by a hollow square.
Keep in mind that TMS Right transforms all availabe track targets, but not search targets. This is one of issues you were having with it in original post.
- Bugged Target: Basically soft target track of a system target, it allows for weapons employment with FCR tracking data. Indicated by a solid box with a circle. Be aware - when you have a bugged target, you may no longer promote track targets to system targets, and first have to remove it (TMS Aft).
As for "not functioning at all" and "cannot see which targets are buggable or not" is not true a bit in my case.
I see a lot of people having troubles with understanding difference between your own onboard tracks and datalink tracks (not to blame), and that's probably the issue you and the person above are having.
To not play the "guessing game", there is a datalink data filter for your FCR, and the current setting is displayed above OSB15. You can either cycle through the options with IFF IN or disable all datalink tracks with IFF OUT.
- ALL: Show all datalink tracks.
- FTR+: Filter out all surveliance datalink tracks.
- TGTS: Filter out all surveliance and PPLI (donor) tracks.
- NONE: Filter out all datalink tracks.
That's a good practice to keep general situational awareness with FCR set to ALL and HSD, but switch filter to FTR+/NONE prior to engagement to actually know what your radar actually sees. It will be still corelated on HSD display, so just crosscheck it.
Let's have an example:
1. AWACS detects a contact.
2. Determines either this contact is hostile, ambiguous or friendly.
3. Sends the data over datalink.
4. You receive that data (in this example, a hostile aircraft, indicated by a hollow red triangle on fcr and hsd pages).
When you point your radar in the direction of the target, the red triangle changes to a yellow box, and that's where many people start having problems:
-- Yellow: Means target is ambiguous. Although surveliance/donors have declared the contact hostile (red), it's still unknown (white) to your own FCR.
-- Box: Indicates track data received from a datalink source. It's not your FCR track data! Even if it's corelated, it may still be a search target. This only means that whatever radar return you had at that position has been corelated to datalink track data.In this scenario, unless you apply a filter, you can't know the status of the contact - search target or track target.
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...
-
3
-
-
@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.
-
3
-
-
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
-
1
-
2
-
26 minutes ago, BIGNEWY said:
We understand the issue, for now it is working as intended. In the future we may revisit the target classification tree.
thank you
You may revisit the classification tree as well, but that's not what this topic is about
-
3
-
Transfer steerpoints from the F10 map into the aircraft - DCS: The Way
in DCS Modding
Posted
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