known issue Multiplayer datalink share of detected air targets.

[Yaga]

In 2.9.4.53549, the changelog lists this for the F-16C: 

 

• Fixed: Multiplayer datalink share of detected air targets.

 

As far as I can tell, prior to this patch datalink sharing and adding/removing flight members' STNs worked fine in MP. Now it seems to not work at all. Neither preset flights from the ME or flights created in the DED from the cockpit work at all (members don't turn blue or even become PPLI, members don't share targets). 

Could we get some more detail about what changed in this update? Is there a different procedure or intended behavior now? Do we need to update our mission files with something? Or ???

This is only an issue with clients in MP and AI behave fine as group members. 

Any guidance would be appreciated. Maybe I'm doing something wrong. 

Thanks, 

 

[Moonshine]

worked fine for me. make sure you follow the updated startup procedure in regards to Link

[Yaga]

On 4/24/2024 at 3:44 AM, Moonshine said:

worked fine for me. make sure you follow the updated startup procedure in regards to Link

To confirm, you are saying:

In Multiplayer, you are able to enter the STN of another player (not AI) into one of the 7 available Flight Member positions via the DED DLINK page, and this turns that player's donated ppli track into a Blue member of your flight?

I've tried this on several servers since the recent patch that broke it with zero luck. The jet is configured correctly. 

@BIGNEWY  @NineLine 

 

[Hobel]

vor 17 Minuten schrieb Yaga:

To confirm, you are saying:

In Multiplayer, you are able to enter the STN of another player (not AI) into one of the 7 available Flight Member positions via the DED DLINK page, and this turns that player's donated ppli track into a Blue member of your flight?

I've tried this on several servers since the recent patch that broke it with zero luck. The jet is configured correctly. 

@BIGNEWY  @NineLine 

 

Perhaps this also has something to do with it.

but are these “old” airplanes?
does this mean that they were set in the ME before the Datalink update?

does this also happen in new missions where “fresh” airplanes are available?

[Yaga]

24 minutes ago, Hobel said:

Perhaps this also has something to do with it.

but are these “old” airplanes?
does this mean that they were set in the ME before the Datalink update?

does this also happen in new missions where “fresh” airplanes are available?

Blue Flag Modern tried rebuilding some slots with "fresh" airplanes and the issue appears to still persist. But I've been unable to test this independently with a completely new mission, so I'm not ruling this theory out. 

Edit: Unless you are referring to the big L16 update several months ago that introduced STNs and assignable flights to begin with, in which case all tests have been done on servers with fresh airplanes that used to work correctly prior to this recent patch. 

Edited May 2, 2024 by Yaga

[BIGNEWY]

Hi, 

please include a short as possible track replay example. I will ask the team to check. 

thank you 

[Moonshine]

No matter how „fresh“ a slot is, as soon as you overwrite the STN assigned by the ME (by doing it in the jet), your own ship will have an additional green circle behind it

Edited May 2, 2024 by Moonshine

[JarrodR5]

Same seems to happening to me and my friend, the current update did not fixed it. Inputing assigned STN into DED seemingly not working for MP cold start F16. Even follow the new GPS allignment procedure. I would try to add track when me and my friend have time. But that could take a while.

[falconzx]

The workaround is confirm the "own" position in the STN DLNK page. If each team member change it or just confirm the ME position, the team visualization come back to live.

Other strange behaviours are about the GPS time, before using a non GPS sync, so just syncing client clocks TNDL worked fine (i think IRL there should be a NTR to master the time) now you can't see other F16 but you see the F18 members, strange no?

Other messed thing, staying on topic is the sharing on FCR. Before the numbers on top of a shared contact indicated correctly the number of the team member who bugged it. Now it's not anymore consistent.

Best regards

[Yaga]

On 5/4/2024 at 2:31 AM, falconzx said:

The workaround is confirm the "own" position in the STN DLNK page. If each team member change it or just confirm the ME position, the team visualization come back to live.
 

I will certainly try this. Do you know if you only need to confirm your own position in order to see others, or if they also need to confirm their position to be visible? 

 

Edit: I can confirm that this works. You must confirm your own # in order to be visible on net, and others must confirm their own # to be visible to you.

null

 

@BIGNEWY

Edited May 5, 2024 by Yaga

[Sithos]

Am 4.5.2024 um 09:31 schrieb falconzx:

The workaround is confirm the "own" position in the STN DLNK page. If each team member change it or just confirm the ME position, the team visualization come back to live.

Other strange behaviours are about the GPS time, before using a non GPS sync, so just syncing client clocks TNDL worked fine (i think IRL there should be a NTR to master the time) now you can't see other F16 but you see the F18 members, strange no?

Other messed thing, staying on topic is the sharing on FCR. Before the numbers on top of a shared contact indicated correctly the number of the team member who bugged it. Now it's not anymore consistent.

Best regards

I tried so many things but didnt notice that.
Oh man, thank you so much for getting that out !
 

[Lord Vader]

This issue with datalink # assignment is known, hopefully we'll address it soon in a future update. 

Thanks for your patience.

[falconzx]

After a short test, the issue in current patch remains, but now i think it's affecting F-18C also. In the previous patch i could add a F-18 to my team asking him to tell me his STN. Now it doesn't work anymore.
Maybe because the F-18 also have to confirm his "position" in his team. Unfortunately i'm not aware about a way to do it.

[Yaga]

On 7/11/2024 at 5:24 PM, falconzx said:

After a short test, the issue in current patch remains, but now i think it's affecting F-18C also. In the previous patch i could add a F-18 to my team asking him to tell me his STN. Now it doesn't work anymore.
Maybe because the F-18 also have to confirm his "position" in his team. Unfortunately i'm not aware about a way to do it.

Charming. Thanks for the heads up. 

Hopefully they will fix this in the near future. 

@Lord Vader any updates on this? The original issue was not addressed in the last patch. 

Thanks,