fixed Datalink not working with cold start ?

[Zarma]

Hi

I noticed that I have trouble to communicate via datalink with my wingmen. I triple checked the configuration in the ME and in the pit, it's not working as long as I used a cold start ship.

Using the linked mission, I tried the following (all in MP not in SP) :

- 2 hot start player ship : OK

- 2 cold start player ship : not working

- 1 cold start and 1 hot start player ship : not working

- hot start with AI wingman : OK

- cold start with AI wingman : OK ??

Can't figure out if I am doing something wrong or if there is a bug with the cold start ships.

 

 

 

testDL.miz

Edited June 10, 2024 by Zarma

[Floyd1212]

You've got 8 aircraft in that mission with IDs 1-8.  But some of them have Preset 1 setup with 4 members, and some with only 2 members.

For example, these two aircraft have 4 members defined.

But these two aircraft are 7 & 8, and they only have each other defined.

You would need to go into the COM page and add the missing members manually if you want to communicate with them as part of your team.

[Zarma]

Yeah both double client are linked in the same DL and checked in the cockpit. 
 

the 4 to the south are one lead client with one AI wingmen each (hot and cold)

[markturner1960]

My buddy Gideon and I had teh same problem this morning...cold start aircraft would not see each other on datalink, despite checking and re setting all settings....( we are pretty familiar with the set up and operation of the datalink) Same mission, checked and spawned into a hot start pair and datalink was working fine.....

So this may be some kind of bug? 

[Floyd1212]

We were flying last night with 4 Apaches, all cold start, and weren't having issues with DL.  This is with a single aircraft per "group" in the ME, and adding members manually with a C/S and ID at startup. @markturner1960 Was your mission setup with two-ship flights like the OP has setup?

 

[Zarma]

My main mission has 2 and 4 ships groups with the same issue. And on rotorhead server, setting up manually, had same issue. 

[GCRev]

Seeing similar in MP. Sometimes it seems to work, sometimes it only works in one direction, sometimes not at all. Hopefully this track file provides ED with some more info!

[Zarma]

17 hours ago, Floyd1212 said:

We were flying last night with 4 Apaches, all cold start, and weren't having issues with DL.  This is with a single aircraft per "group" in the ME, and adding members manually with a C/S and ID at startup. @markturner1960 Was your mission setup with two-ship flights like the OP has setup?

 

Not sure but I guess that on Rotorhead server they are all single ship and was hardly working.

[Gideon312]

22 hours ago, markturner1960 said:

My buddy Gideon and I had teh same problem this morning...cold start aircraft would not see each other on datalink, despite checking and re setting all settings....( we are pretty familiar with the set up and operation of the datalink) Same mission, checked and spawned into a hot start pair and datalink was working fine.....

So this may be some kind of bug? 

Here is a screenshot of the troubling cold start AH-64's @Floyd1212:

 

 

Edited June 11, 2024 by Gideon312

[Floyd1212]

It very well could be an issue with cold starts in a multi-ship group.  I always setup my missions with single units for clients, and we haven't seen issues of DL flat-out not working at all since the last patch.

[LorenLuke]

I know I've had issue trying to get it to work, with cold-start aircraft, across a shared mission-editor setup AND manual set-up for presets, across UHF, VHF, and FM1/2 radios from no more than 30 feet away. Something's off, for sure.

[papaz]

Our group is having datalink issues too, since last patch (2.9.5.55918). From some testing, it seems that using the primary freq as Preset, DL works, while the other radios are unable to xmit. edit: this is with AI only, we're yet to confirm it in multiplayer.

AH-64D_datalink_UHF.trk

edit: Multiplayer test result:
Nothing works out of the box, when spawning into a cold heli. The radio panel lies to you, even though it says you're on PRE1 L1 PRE3 L3 PRE4 L4 etc, the link is inop on all of them.
To get the link to operate, you need to select another preset on your chosen radio. Alternatively, switch away-switch back to it.
For example: FM1 from PRE3, switch to any other PRE, alternatively switch and then select PRE3 again from the list.
This workaround can be used until it gets fixed.

Edited June 19, 2024 by papaz

[derfritz]

Our group just did the same test, we had three apaches that were setting up the datalink completely from scratch (set ownship ids, set profiles, set net with wingmen, set freqs, set SC, IDM select) and it did not work at cold start. With a hot start, and the same procedure it did work. So yeah something weird is going on.

Edit: After more testing, we got it working on cold start as well, even without selecting a different preset and switching back. The only different factor in multiple tests were that it was not working when both helicopters were multicrew, and it was working fine when both were only single pilot. Can anybody confirm that?

Edited July 1, 2024 by derfritz

[zenatsu]

19 hours ago, derfritz said:

The only different factor in multiple tests were that it was not working when both helicopters were multicrew, and it was working fine when both were only single pilot. Can anybody confirm that?

I can confirm that even not in multicrew, the DL will still not work from a cold start. I have held multiple lessons with people (we each have our own apache) and it consistently has not worked to try and practically demo the DL.

That said, over time, at some point, the data link will just "Turn on" and suddenly work. I do not know how as its different every time I teach someone. One time it kicked on after someone switched to the UHF and configured it. One time it kicked on after someone equipped an FCR. It's very inconsistent and Im eager to see if there is a consistent workaround.

[derfritz]

Did some more multicrew testing.
If the CPG sets up the Datalink following the complete procedure (set ownship ids, set profiles, set net with wingmen, set freqs, set SC, IDM select), everything syncs to the Pilot fine except: CALLSIGN and ORIG ID. They will stay on default.
If the Pilot sets up the Datalink following the complete procedure, everything inputs well.
So if the CPG does the datalink setup, double check the values afterwards. Especially make sure Callsign and ORIG ID are correct. On top of that we will make it a habit to hit the swap key on the EUFD a couple times.
I'll report back if we find anything else, but this specifically seems to be a pretty obvious desync issue.

Edited July 2, 2024 by derfritz

[Gideon312]

I’ve tried several suggestion made here, but no joy. Still doesn’t work, what a pity.

Edited July 7, 2024 by Gideon312

[Zarma]

Did someone test after latest patch ?

[papaz]

The bug is still present after patch. From our testing it's even worse than before, VHF DL wasn't working, despite doing the frequency change -> preset trick.
Had to use FM1 DL.

[Guest]

Hi all, 

Sorry a bit off topic,  but has anyone had Kiowa's showing up on the TSD of their Apache?  Sometimes the icons move with their changes in position,  other times they stay fixed, even if the Kiowa is long gone. 

Cheers

'52

[Raptor9]

As a follow-up to this thread, I wanted to update you all that we were finally able to identify and reliably reproduce a few issues with the datalink, and these have been fixed internally. We appreciate your patience and hopefully these fixes can be sent to the public builds as soon as possible.

[evo16g]

@Raptor9 Is there an anticipated timeline on the release of those updates? When the datalink works, man, it's great!

 

[Raptor9]

8 hours ago, evo16g said:

@Raptor9 Is there an anticipated timeline on the release of those updates? When the datalink works, man, it's great!

This was already included in the update released on August 9. The thread is tagged as "fixed" as well.

If you have encountered a new bug with regard to datalink, please submit a new bug report with a short track demonstrating the problem.