correct as is FCR Target Report not working

[Mayo]

Targets send through target report only show on TDS and not on FCR

This report should provide the target library to Apache's in the same IDM network, in order to have aircraft with FCR provide targeting for other aircraft without FCR. All non-FCR equipped aircraft should be able to engage target as if they did a scan them selves and cycle through the targets with next-to-shoot, obviously also with PFZ's active.

In the current state FCR shows 'DL TARGET DATA' but targets from the received library are not shown in the scope.
Reference your own video:

A track file from both Server and clients have been attached.
Screenshots are server side, when the client send his targets.

Setup was 2 computers local with cross-cable, in order to make sure packet loss cannot be the issue.
Same occurred through internet connection though.

 

server-20241103-172524.trk 2sip_apache_testt-20241103-172543.trk

Edited November 3, 2024 by Mayo

[Raptor9]

Only FCR targets generated by the ownship's onboard FCR will be displayed on the FCR page. Any FCR targets received via the datalink will only be displayed on the TSD for orientation and situational awareness.

FCR TGT Reports do indeed overwrite any existing FCR data in the receiving aircraft, but FCR targets received via an FCR TGT Report cannot be used in the same manner as FCR targets generated by the ownship's onboard FCR. FCR targets received through the datalink cannot be directly engaged unless they are received by an RFHO message. This is even specified during the video.

Keep in mind that many of the feature preview videos that Wags releases may include small details that were identified as bugs after the video was produced and were subsequently corrected.

[Mayo]

On 11/3/2024 at 6:03 PM, Raptor9 said:

Only FCR targets generated by the ownship's onboard FCR will be displayed on the FCR page. Any FCR targets received via the datalink will only be displayed on the TSD for orientation and situational awareness.

FCR TGT Reports do indeed overwrite any existing FCR data in the receiving aircraft, but FCR targets received via an FCR TGT Report cannot be used in the same manner as FCR targets generated by the ownship's onboard FCR. FCR targets received through the datalink cannot be directly engaged unless they are received by an RFHO message. This is even specified during the video.

Keep in mind that many of the feature preview videos that Wags releases may include small details that were identified as bugs after the video was produced and were subsequently corrected.

Hadn't had the chance to reply yet.

I stand corrected and above was confirmed by other sources.