reported earlier F16 intraflight datalink on persian gulf, not working between 0:00 and 4:00am (multiplayer)

[nighteyes2017]

Yes you read the title right. intraflight datalink in the f16 on the persian gulf is clock time dependant.

The bug is reliably reproducable, and is visible using hotstarts. so no 'you forgot to enter coordinates or mids' or anything like that. 

We didnt test it yet in other theaters, so i dont know if this is a F16,theater,or general bug.

Basically the fault is this:

Persian gulf mission time and F16 ded time are 4 hours apart.

between 0:00 and 04:00 mission time, or between 20:00 and 0:00 F16 ded time, intraflight datalink does not work for server and clients. (AI datalink and intraflight AI remains visible)

When a client connects to the server, at first the server F16 will have datalink on the client joining in because the client is busy spawning in. But after the first datalink update (around 12 secs) the datalink dissappears and stays gone.

The client, on joining, never sees the datalink at all.

So we tested several things:

• Setting mission time at 23:59 (19:59 in ded), and then waiting in pit, the datalink works. Even after the mission passes 0:00 (20:00 in ded). The intraflight datalink stays up.
• Setting mission time one minute later at 0:00 (20:00 in ded), intraflight datalink does not work. as mentioned, on a joining client, the server sees a momentary link, wich dissappears after the first update round.
• Now the other end of the timeslot:
• Setting the mission time at 03:59 (23:59 in ded). The intraflight datalink does not work, BUT, when passing the magic mission time of 04:00 (0:00 in ded), after 12 secs, the datalink suddenly starts working!!.
• Setting the mission time past 04:00 (0:00 in ded), intraflight datalink works just fine from the go.

We didnt have time to test this on other maps 

i have included three mission files with mission time settings 23:59, 00:00 and 3:59. But basically, its just a 2ship F16 mission set on hotstart with both set to client. Nothing else is in the mission file.

What stands out off course, is that the time slot where intraflight datalink is not working is between 0:00 mission time and 0:00 ded time. This may be coincidence, but it is curious.

PG mplay intraflight datalink missiontime 0000.miz PG mplay intraflight datalink missiontime 0359.miz PG mplay intraflight datalink missiontime 2359.miz

[Moonshine]

been reported here since november last year;