Robin_Hood Posted February 18, 2024 Posted February 18, 2024 I would like to submit this simple mission and multiplayer track where the following behavior occurs: Initial conditions: - There is a ME-defined flight of 2 client F/A-18C and an E-2D Hawkeye - Both F/A-18C are defaulted to the same MEMBER Datalink group Behavior: - At mission start, I can initially see the other Hornet as the "B" flight member on the datalink - A few seconds later, he disappears and is replaced with a simple datalink contact from the AWACS, instead of a member or donor or even a party to the Datalink net The track file and the mission file is attached ; if I have missed something, please let me know Note: this is a very simple case that I made after seeing the problem in more complex cases (user-defined groups, custom VCS and TN, etc...) Datalink_multiplayer_test.trk test_DL.miz 2nd French Fighter Squadron
rob10 Posted February 18, 2024 Posted February 18, 2024 Datalink in MP seems to be inconsistently flaky. Haven't found conditions that cause it, but I've see D/L appear and disappear over time.
Spock14 Posted February 19, 2024 Posted February 19, 2024 I think there is a problem, if the Zulu time is on another date than the local time, or changes date during the mission, the Datalink will not work correctly. i only noticed that at Marinas and it seems to be a known problem.
Robin_Hood Posted February 19, 2024 Author Posted February 19, 2024 Interesting, I'll try different times and maps, but I'm pretty sure it worked alright a few weeks ago; now that I think about it, I have changed the mission start time some time ago, maybe it placed it at a different date then. I'll investigate 2nd French Fighter Squadron
Lekaa Posted April 12, 2024 Posted April 12, 2024 (edited) Any work in progress fix on this? Edited April 12, 2024 by Lekaa
Lekaa Posted April 12, 2024 Posted April 12, 2024 On 2/19/2024 at 12:21 PM, Robin_Hood said: Interesting, I'll try different times and maps, but I'm pretty sure it worked alright a few weeks ago; now that I think about it, I have changed the mission start time some time ago, maybe it placed it at a different date then. I'll investigate did you find the culprit for this behaviour?
Recommended Posts