cannot reproduce F16 Datalink Broken

[Lord Vader]

Thank you for the feedback and suggestion @itn.

Honestly, aside this very particular instance about the platform maintainer that I clarified, we've explained earlier when the new GPS INS logics for the F-16 were presented about faction limitation and GPS availability.

 

[Nedum]

7 minutes ago, Lord Vader said:

Thank you for the feedback and suggestion @itn.

Honestly, aside this very particular instance about the platform maintainer that I clarified, we've explained earlier when the new GPS INS logics for the F-16 were presented about faction limitation and GPS availability.

 

Please, can you direct me to the exact posting who describe who we have to set up all the stuff (USA flight must be enabled for the blue side to get GPS data, etc.).

The posting, you'd linked, is not explaining what was talked about in this thread.

I am still looking for it, and I am unable to find it.

We have so many of these threads because of the missing documentation, in which we should have all the necessary things described.

Pointing to Threads, full of things, not going into the necessary details, isn't the thing we needed, but all we have. That's not good. That's producing frustration.

How long do we have to wait for a Handbook, with all the necessary stuff, so we can >>start << to test the F16 module and if all systems are working like they should?

And NO, the linked threads, postings, documents, whatever you show are not good enough to use all the >>current<< F16 systems like we have to. It's more like a "Where is Waldo?" thing, but the opposite of fun.

[Lord Vader]

I'm sorry you feel that way, @Nedum.
The "threads full of things" is what we can do while this very complex system is being improved on a daily basis. We believe the users prefer we share the information as regularly as possible and that's why we have the Mini-Updates as well as the famous Matt Wagner's videos.
I am not sure a "handbook" could be further designed for this specific item, but I'll pass on the suggestion.
Our DCS: F-16C manual will certainly be updated in the future, but I'm not sure that's what you're referring to. In any case, we cannot commit right now to a manual if production is still ongoing. Please remember that all this takes time to produce accurately, demanding research for an as accurate as possible simulation we're improving constantly. 

[itn]

My comment about documenting the GPS gotchas was mostly meant in general, not only F-16 and not only for the dozen of us who actually closely follow the Viper Mini-updates. I like the mini-updates and for those that follow them, they’re the best way to stay current with the changes. Thank you for those.

However, if I remember correctly (checked before I sent my previous message), the GPS cut-off date and coalition degradation is mentioned nowhere in the DCS User Manual. Text on Unrestricted SATNAV says what it does, but does not detail what are the restrictions that gets unrestricted. 

What I had in mind in my comment is the budding mission maker, not knowing all the ”just need to know” gotchas and not following e. g. Viper mini-updates. The one we found in this thread is just the newest gotcha found out more or less accidentally.

Also I’ll mention that apparently Russia has some GPS keys to share even if blue does not. If you have blue without USA versus Russia and others on red, blue Vipers get no GPS as we established, but red Vipers get the degraded red GPS. Even if the key/coalition/faction simulation might make some sense overall, you’ll quickly find yourself in weird technicalities that make no sense even if the mission scenario might be believable. 

Just my two cents. 

[Hyperlynx]

It's still busted.

Usually cycling the time on and off on the TIME page fixes it, but I've just restarted a mission and the second time out I got no datalink no matter what. (In addition, when I entered in target coordinates the sensors pointed off into the sky instead. It was fine the first attempt, but after restarting the mission it was not.)

This is incredibly frustrating!

[BIGNEWY]

please include a track replay example

thank you 

[YoYo]

I will only add that if for some reason we set the mission before the date 28/3/1994 the GPS signal won't work, so DL probably won't work properly either. It's worth checking too.

[Hyperlynx]

Just had it happen again, on an exercise with some 12 odd other aircraft. I was supposed to link up with a flight of three hornets and do OCA, and had to try to go by bullseye calls alone (very difficult, I did not manage very well, admittedly had a great time trying).

Of course, like a doofus, I forgot to save a track file. I'll do my best to remember, next time it happens.

[Hyperlynx]

Wait! I *do* have a track file, because apparently multiplayer always gets saved to track file!

It's 171MB, so I can't attach it. I've uploaded it here: https://drive.proton.me/urls/C98RTVGRD0#q9yGm4Y0P3Yz

Apparently the other Viper's datalink worked fine, it was just me.

Edited January 23 by Hyperlynx

[speed-of-heat]

I'm still having it happen in campaign missions, essentially no data link

[Nuggetz]

To add my support to the suggestion that the Data Link and radar are broken. It does not happen on every engagement but it does happen all too frequently. Not only is there missing target tracks and there are examples of misdirection ie target is indicated at my 2 o’clock but the target attacks from the 10 o’clock. Two days ago while fighting PvP, DL indicated my opponent was at the 3 o’clock but the RWR was screaming he was on my six. Clearly something has changed and is not right. ED I implore you to believe we are not making this up or incompetent operators of the F16.