AAR Replay Issue

[Tetra]

Saving and replaying a track file of an AAR session will not show any radio comms performed or trigger the tanker to drop the boom. 

• Branch: Open Beta
• Build: 2.9.2:49940
• Mission: Aerial Refueling F16 Instant Action - Caucasus
• Jet: F16
• Issue:
  • Contacted tanker (using Voice Attack + Vaicom Pro), Opened fuel door, set HUD to show data and ICP to bingo page. Approach tanker, contact tanker, ready pre-contact, perform full refuel, no disconnects.
  • Disconnect on transfer complete and fly off.
  • Save the replay, load the replay, however no radio contact with the tanker is shown, not approaching to refuel, or ready-pre contact, therefore in the replay the tanker boom never drops to refuel. All the replay shows is me flying along behind the tanker with no boom connected to the jet and no fuel being transfered.

AAR_F16_Replay_Bug.trk

Edited January 28, 2024 by Tetra

[draconus]

Use build-in comms and check again.

[MAXsenna]

Saving and replaying a track file of an AAR session will not show any radio comms performed or trigger the tanker to drop the boom. 

• Branch: Open Beta
• Build: 2.9.2:49940
• Mission: Aerial Refueling F16 Instant Action - Caucasus
• Jet: F16
• Issue:
  • Contacted tanker (using Voice Attack + Vaicom Pro), Opened fuel door, set HUD to show data and ICP to bingo page. Approach tanker, contact tanker, ready pre-contact, perform full refuel, no disconnects.
  • Disconnect on transfer complete and fly off.
  • Save the replay, load the replay, however no radio contact with the tanker is shown, not approaching to refuel, or ready-pre contact, therefore in the replay the tanker boom never drops to refuel. All the replay shows is me flying along behind the tanker with no boom connected to the jet and no fuel being transfered.

AAR_F16_Replay_Bug.trk

VAICOM, DCS-BIOS etc. won't write information in the track files. It's not a bug, but hopefully ED will make it compatible in the future.

Sent from my SM-A536B using Tapatalk

[Tetra]

Gotcha, thanks both of you, good to know it's just a result of Viacom. Appreciate the input. 

[Nealius]

If you want to get around this bug for filming/screenshots, etc. use the "options" command and "take #" to manually make a selection through VAICOM. Those will be written to the track file.