SA page vs A/A TCN

[pcoud]

This is kind of a follow up of a message I recently posted in the general forum. I don't think it actually is a bug, but I can't get rid of the problem.

 

I'm running the test mission here attached. One client F18, one awacs and one tanker on the blue side, 3 transports on the red side.

 

Initially the tanker has an A/A TACAN set on channel 1X. I launch the mission  and display the SA page of my Hornet. I can see  the awacs as  a donor, and I can see all bottom parts of the various HAFUs (the tanker and the 3 red planes).

 

 

Now I run the mission but I set the tanker's A/A TACAN to 5X. My SA page looks like this:

 

 

No datalink... I can't see the awacs anymore nor any of the bottom parts of the HAFU symbols.

 

This is 100% reproduceable on my setup, BUT I recently played a MP mission with friends, there was a tanker with its A/A TCN set to 5Y and I was  the only one not getting the SA page... 

 

If it may help, I am also attaching a log of my test missioin run with a 5X A/A TACAN, resulting in the loss of the datalink.

 

 

Test SA page.miz dcs.log

[Tholozor]

As Harker mentioned here, it's correct as is. Set your A/A TACAN to a channel between 37-63, or 100-126 and it shouldn't interfere.

 

 

Edited December 31, 2020 by Tholozor

[Joni]

8 hours ago, Tholozor said:

As Harker mentioned here, it's correct as is. Set your A/A TACAN to a channel between 37-63, or 100-126 and it shouldn't interfere.

37X

 

 

 

What? If that would be true then setting it to 1x like he said it was set would have made it unable to work but it worked. 

 

The simulation of the MIDS terminal antennas is not working at the moment.

 

 

[Tholozor]

It's correct as is in the sense that you shouldn't use those channels for A/A TACAN, regardless of the fact that the A/A TACAN works in that frequency range and interferes with the datalink.

Edited December 31, 2020 by Tholozor

[Joni]

3 minutes ago, Tholozor said:

It's correct as is in the sense that you shouldn't use those channels for A/A TACAN, regardless of the fact that the A/A TACAN works in that frequency range and interferes with the datalink.

 

 

No, it isn't correct. See my response.

 

OP is reporting that 1X works fine and that 5X doens't. According to Natops, Wags, and public documents, 1X and 5X are in the same range that should be avoided.

 

So no, it isn't correct.

[Tholozor]

What's I'm saying is that he shouldn't use those channels (1X or 5X) for A/A TACAN, period (I am agreeing with you). Regardless of the MIDS terminal inconsistencies.

Edited December 31, 2020 by Tholozor

[pcoud]

Thanks for your replies @Tholozor and @Joni

I understand what you're saying @Tholozor: being in the recommended range guarantees it'll work, being outside it may or may not work. And by the way, I did some quick tests with 38X and it worked so far, always.

 

I remain quite puzzled though:

 

1) I'm part of 12 people squadron,  our missions always have a tanker set on A/A 5Y, and we never ever had an issue with that

2) I played with them two days ago, I was the only one having the problem

3) I remain very surprised, statistically speaking, that among the hundreds or more people designing missions with the hornet and that, we can assume, did not know about these recommended ranges, the issue was not raised several dozen of times

 

So apparently I'm the only one, and since very recently... Makes me believe something went wrong with MY config (I tried repairs to no avail)...

[Tholozor]

There's reported issues of TACAN having issues in multiplayer on AI units, mainly regarding when the TACAN command is activated. Generally it affects clients that join a mission after the command is performed (usually at mission start). Some mission designers work around it by making the unit activate its TACAN on a repeating timer so it's always turning it back on if a player's client thinks it's off. The problem on the whole is fairly inconsistent.

Edited December 31, 2020 by Tholozor

[pcoud]

Fair enough, thx