fixed Datalink error after update 19-12-2023

[Floyd1212]

On 7/22/2024 at 5:11 PM, Raptor9 said:

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.

Can we find out of these fixes should already be in the game at this point?  Or maybe a list of the known issues that remain with DL in multi-player and multi-crew situations?

We are still getting instances of DL not working after setting it up on the pad and testing before lifting off.  Still getting double transmits.  And still getting NACK messages when the message has in fact been received.

I can spend some time organizing a multi-player DL bug report again, but I don't want to waste my time if these are still known issues and being worked on.

[Raptor9]

52 minutes ago, Floyd1212 said:

Can we find out of these fixes should already be in the game at this point?

The issues originally identified in this thread were included in the patch notes several updates prior. This thread is marked as "fixed" for this reason.

52 minutes ago, Floyd1212 said:

Or maybe a list of the known issues that remain with DL in multi-player and multi-crew situations?

We have no pending issues regarding datalink issues in multiplayer in general, meaning that if one player sends messages to another player, we have not reproduced any issues. There is always the possibility of high server loads causing data loss or de-sync; or missions that include custom scripts that may be causing issues.

As for datalink issues with multi-crew, there are some reports that have already been reported that can be seen in AH-64D bugs section.

52 minutes ago, Floyd1212 said:

We are still getting instances of DL not working after setting it up on the pad and testing before lifting off.  Still getting double transmits.  And still getting NACK messages when the message has in fact been received.

When configured properly in multiplayer sessions that do not include custom scripts or mods, we have not experienced any issues in testing aside from a few reports regarding specifically multi-crew de-sync.

If you receive a datalink message across an FM radio while both FM radios are tuned to the same frequency and both FM radios are set up to receive datalink traffic, the avionics will treat this as receiving two messages. If you disable datalink on one FM radio or tune the FM radios to different frequencies, this will not occur. Having said that, there is an internal report to address the FM radios being able to tune frequencies in 5 kHz (.005 MHz) increments. In reality, the FM radios can only be tuned in 25 KHz (.025 MHz) increments; so if the radio frequencies are close enough, the messages are bleeding through even though the frequencies are technically slightly different. If the frequencies on each FM radio are separated by 25 kHz, receiving two identical datalink messages from a single transmission will not occur.

As for the NAK, we have not been able to replicate any issues with this either. However, it is worth noting that if any of the intended message recipients have their AUTO ACK on the MODEM page disabled, or any of the intended message recipients otherwise do not receive the message, a NAK notification will still occur. This will often occur if a message is transmitted to multiple recipients at low altitude. The more recipients you are trying to send a message to, the more chances it may not reach someone. Further, as a reminder, TEAM messages go out to all TEAM members in a network, so it is important to understand to whom a message is being sent on a given network, and who is selected as a TEAM or a PRI member.

As the originally reported issues in this thread have been resolved, I am closing this thread. If anyone finds additional issues, as usual please start a new thread with a track file to avoid turning these bug report threads into perpetual "catch all" threads that will become confusing to track and understand.

Edited November 4, 2024 by Raptor9
Edited for typo