need more information Datalink not being correct in mission editor and in-game

[=GR= Cypher]

During editing and testing a mission I created 4 groups of F-16s with 4 elements each. All datalinks, STN, Voice Callsigns, transmit power and flight details inserted in the editor but in-game nothing is the same.

Example: Enfield 4 ship flight with STN from 00011 to 00014, Voice callsign EN11-14, transmit power high and for EN11 to be Flight Lead, during the mission is shown as EN12, STN 00011, OWN#2 which should be #1 as it's flight lead, transmit power MED and FL NO (Flight Lead).

This also happens with the other elements in exactly the same way. The only option to have it in a correct way is to be manually inserted in-flight.

[Lord Vader]

Hi @=GR= Cypher

Since you didn't supply the Miz or Track file, I created my own simple mission following your steps.

Aside from the fact that the Transmit Power is indeed ignored if set to High (may need a revisit), I couldn't reproduce the ownship number and flight lead status. 

[Moonshine]

Im seeing the same as Cypher whenever i create a static template off of a flight, then load an empty map, add the static template and somehow the STNs for #3 and #4 are swapped constantly. Only manual input in the jet „fixes“ it. I made a post about it a while back.

in the meantime i changed PC, completely reinstalled DCS from scratch and it still happens.

Edited February 15, 2024 by Moonshine

[=GR= Cypher]

@Lord Vader the trk file showing the issue.

 

Thank you for your time!

datalink F16.trk

[Lord Vader]

Hi again @=GR= Cypher

I checked your track and indeed I can observe the #2 issue. However, this track is a bit tricky to use, since it contains several scrips, including Mist and CTLD. Some of these scripts have been reported to have issues with our datalink logic. I am not sure their creators solved these issues or not, maybe it's related.

The point of this is that I tried to replicate the issue in my own simple mission, no scripts, and couldn't see a problem with the IDs and allocation. Of course, I won't suggest you edit your mission to remove the scripts, but it does seem like they could be the cause here. 

[=GR= Cypher]

Checked it again. Seems that it works fine even with the scripts. 

 

Please disregard the above post.

 

Thank you for your time!