resolved DCS F-16C Data Link Not Working When Cold Start...

[wptmd7675]

when i start Hot start, Data link is Good Working..

But if i start cold start, Data link Not Working..

Like below picture, i did Start Procedure Precisly !! (MIDS on, INS NORM -> NAV, IFF Master NORM)

 

In my HSD Page, Bandit & Friendly Unit Now Shown

 

Is there any Problem ?! 

 

 

 

 

Edited March 1, 2021 by wptmd7675

[BIGNEWY]

Hi

 

welcome to the forum, 

 

Please include a short track replay showing the problem. 

 

you can save a track replay when you exit the mission 

 

thanks

[wptmd7675]

here ! Thanks for your Supprot.

Due to file size, upload by google drive !

link here

 

my mission : https://drive.google.com/file/d/1S44HlMjoPSQ0x2WRH9F4hQ3MOASFw-59/view?usp=sharing

replay : https://drive.google.com/file/d/1_V04auVQk1RNw49YZSsPCaTjKv04vSSd/view?usp=sharing

[XCNuse]

worked no problem for me; you had nothing to look at though, unsure why you didn't see AWACS, but tossed in some SAMs and Mig29s and they showed up right as I went into NAV.

 

Only thing I see different is my FCR is on; which in theory shouldn't matter.

 

Side note, you had -AWACS enabling twice on the AWACS.

That also may be why; it may have been turning itself off?

When you put down an aircraft set as a type, be it CAP, CAS, AWACS, Refuel; you don't need to put in that task again; it's already preprogrammed in.

 

Edited March 1, 2021 by XCNuse

[wptmd7675]

Thanks for your reply.

first of all, my FCR was 'ON' too, (Just make sure, I tried one more time. but problem not solved..)

and as your commention, i edited Units Task of my mission, But Data Link still not Working.. !  

[XCNuse]

In theory the only thing you should be getting at all is the AWACS anyways; as there's nothing else off your nose that you have in the mission to see.

 

Also worth noting at times you can lose datalink tracking information depending on line of sight.

[Dragon1-1]

Are you airborne? Weigh on wheels turns off FCR and possibly a few other systems, in other not to fry the ground crew. Datalink might be turning off, too.

[XCNuse]

3 hours ago, Dragon1-1 said:

Are you airborne? Weigh on wheels turns off FCR and possibly a few other systems, in other not to fry the ground crew. Datalink might be turning off, too.

at least in OP's picture, FCR was actually off-off, not in standby off. He has MIDS on, so they SHOULD be getting DL info, but again; there's nothing off the nose in the mission except the AWACS itself, which SHOULD show up, and did for me.

 

Side note OP, the far right top and bottom switches around avionics power don't need to be flipped up (I think it's DL and MAP).

 

Datalink is over the MIDS.

 

Either way, you should get datalink with the FCR off completely, so it's weird to see not even the AWACS visible.

 

OP out of curiosity, did you do a standard align or a fast align?

Reminder if you to a standard INS align, you MUST select the location and elevation on the INS page on the DED and accept their location with the enter button on the UFC.

With a stored heading alignment you don't select and confirm the location.

 

Other than the FCR thing (at work so I can't test), the only thing I can think is the INS was borked in some fashion by doing one of those things incorrectly.

 

Generally speaking; there's no need to use the standard align... really ever in DCS. Even if you move, it seems that stored heading will update. That said, the only reason again you should be resetting INS is if you lose all power and deadstick a landing and repair or something similar.

 

But again; with nothing actually off the nose of the aircraft in the mission... the only thing that we'd be seeing is the AWACS anyway; until you take off at least.

Edited March 1, 2021 by XCNuse

[XCNuse]

Just tried it again.

 

I realize what you did wrong OP; you indeed did a standard INS alignment and did not confirm the LAT/LONG/ALT in the DED.

 

And I know this because I was able to just do it, and at 240 I see bulls and the AWACS.

The fact your screenshot does not show bulls, means your INS is wrong.

 

If INS is wrong, your datalink information will not display correctly.

 

And I know you did it as a standard align, because of the time and accuracy numbers on the top of the DED.

[Taz1004]

XCNuse is correct.  You can also do STOR HDG INS Alignment.

Edited March 2, 2021 by Taz1004

[Machalot]

9 hours ago, XCNuse said:

Even if you move, it seems that stored heading will update.

Slightly off topic but I just saw another thread complaining the STD HDG align always reverts to the original spawn point rather than storing the state at shutdown.  Are you seeing different behavior?

[wptmd7675]

Thanks For all Reply !!

Problem Solved. I Tried 'STOR HDG INS Alignment' and Data Link Works Perfect !!

But If i tried 'NORM INS Alignment', it still Not Work.. (When i tried 'NORM INS Alignment', Waited for Counting '6' = 'RDY' Sign Flashing)

Edited March 2, 2021 by wptmd7675

[SpaceMonkey037]

18 minutes ago, wptmd7675 said:

Thanks For all Reply !!

Problem Solved. I Tried 'STOR HDG INS Alignment' and Data Link Works Perfect !!

But If i tried 'NORM INS Alignment', it still Not Work.. (When i tried 'NORM INS Alignment', Waited for Counting '6' = 'RDY' Sign Flashing)

 

You're most likely aligning your INS incorretly. I will not explain how to correctly align your INS in this post, but make sure to re-enter the aircrafts coordinates after starting the alignment.

[XCNuse]

8 hours ago, Machalot said:

Slightly off topic but I just saw another thread complaining the STD HDG align always reverts to the original spawn point rather than storing the state at shutdown.  Are you seeing different behavior?

Unless that has changed; it's been a hot minute since I've had to actually reset my alignment (aka, several months at this point).

It seemed to always work though; and by work I mean... that's totally not realistic, but INS aligned and DL came back correctly it seemed.

I would hope they've fixed it by now at least, as that's definitely incorrect behavior!

 

 

@ OP again, if you do a NORM align you MUST CONFIRM the LAT, LON, and Elevation early during the INS alignment procedure, they're put in for you automatically, but you still have to confirm them by clicking enter on the UFC.

[SpaceMonkey037]

5 hours ago, XCNuse said:

Unless that has changed; it's been a hot minute since I've had to actually reset my alignment (aka, several months at this point).

It seemed to always work though; and by work I mean... that's totally not realistic, but INS aligned and DL came back correctly it seemed.

I would hope they've fixed it by now at least, as that's definitely incorrect behavior!

 

 

@ OP again, if you do a NORM align you MUST CONFIRM the LAT, LON, and Elevation early during the INS alignment procedure, they're put in for you automatically, but you still have to confirm them by clicking enter on the UFC.

Like I said, I am very sure that he has incorrectly aligned his INS. The problem isn't with the datalink, it's with how the INS system is far from correct. As long as you do a semi-correct alignment you will have no issue with datalink.

[XCNuse]

oh no for sure; not disagreeing.

At that point OP could just do an in-flight alignment as well to resolve but still not a great solution.

 

That all said; I doubt we'll ever see a more accurate INS system in the Viper anytime soon / ever.

[Machalot]

16 minutes ago, SpaceMonkey037 said:

Like I said, I am very sure that he has incorrectly aligned his INS. The problem isn't with the datalink, it's with how the INS system is far from correct. As long as you do a semi-correct alignment you will have no issue with datalink.

How would you even get an alignment with -289 ft altitude as shown in the picture? 

Edited March 2, 2021 by Machalot

[ice41]

2 hours ago, Machalot said:

How would you even get an alignment with -289 ft altitude as shown in the picture? 

 

 

the current F16 INS in DCS will start alignment with SALT set to the barometric altimeter value, and SALT can be changed by the barometric pressure knob on the altimeter during alignment.

 

I noticed that when an alignment completes and the knob is turned from ALIGN to NAV, the SALT will magically be synced to the actual altitude reported in the external view info bar regardless of the value used for alignment.

 

The odd SALT value in the screenshot is most likely an effect of the inproper alignment procedure.

 

wptmd7675 I took a look at your original trackfile. I did not see you confirming the LAT LNG and SALT values during the NORM alignment.

You must use dobber up/down and ENTR to confirm each value at the beginning of a NORM alignment.

see 2:15 in the norm align tutorial by Wags. Though unless you are doing a new alignment after shutdown, there's really no reason to use ALIGN NORM and should just go with the ALIGN STOR HDG

 

Edited March 2, 2021 by ice41

[VampireNZ]

Yes there seems to be some misinformation going around that I have seen in other threads that you don't need to 'ENTER' your lat/long and alt during normal alignment.

 

As stated above - yes you do. No need to change any of the digits if they match your location as per the F10 map - but you still need to dobber down to each field and hit 'ENTER'.

[Florence201]

On 3/2/2021 at 3:41 PM, VampireNZ said:

Yes there seems to be some misinformation going around that I have seen in other threads that you don't need to 'ENTER' your lat/long and alt during normal alignment.

 

As stated above - yes you do. No need to change any of the digits if they match your location as per the F10 map - but you still need to dobber down to each field and hit 'ENTER'.

 

This is the correct procedure, but you MUST wait for ALIGN to flash in the HUD rather than the RDY in the INS page. This seems to be an ongoing misunderstanding with respect to Viper INS alignment. In both STORED or NORM, wait for flashing ALIGN in the HUD and you will be fine.

[VampireNZ]

4 hours ago, Florence201 said:

 

This is the correct procedure, but you MUST wait for ALIGN to flash in the HUD rather than the RDY in the INS page. This seems to be an ongoing misunderstanding with respect to Viper INS alignment. In both STORED or NORM, wait for flashing ALIGN in the HUD and you will be fine.

 

Yep rgr that - personally once I have accepted the INS position I dobber left away from INS page and continue with after-start setup. When ALIGN flashes in HUD I shift to NAV - easy.