Datalink Command

[Snakeice]

Hello everyone, I wanted to ask you for some clarification on the functions of the Datalink. yes to chuck's guide and the manual, they talk about existence of the DLWPT. do these waypoints enter in the Mission Editor as the various IP, FP, ST? Second question: in the cap, there are WILCO, POINT, CANCO, ENGAGE. according to the manual, they should be functional. beyond the technical purpose of the button, which in addition to being well explained in the manual are self-explanatory, what is the purpose in DCS.

Thank you

 

Snakeice

[QuiGon]

3 hours ago, Snakeice said:

Second question: in the cap, there are WILCO, POINT, CANCO, ENGAGE. according to the manual, they should be functional. beyond the technical purpose of the button, which in addition to being well explained in the manual are self-explanatory, what is the purpose in DCS.

 

None

[Snakeice]

so why heatblur say: 

 

Quote

The DATA LINK category contains message button functionality for RIO data link responses to data link controller commands. The WILCO (will comply), CANTCO (can not comply) tells the controller if own aircraft can or can not comply to a command. POINT enables the RIO to mark a hooked track sent to the controller for special attention. ENGAGE likewise indicates own intention to engage a hooked track.

The NAV GRID button enables the NAV GRID functionality on the TID, see Navigation Command and Control Grid (NAV GRID)

The TID AVIA button enables the AVIA display on the TID. Not yet implemented.

The F/F NAV UPDATE allows for Link-4C fighter to fighter navigational updates. See the navigation chapter.

Remaining buttons are non-functional.

should't they say also WILCo, CANTCO.. aren't functional and not only remaining buttons? @IronMike

 

Snakeice

[The_Tau]

Shouldn't they work like in Fighter-2-Fighter datalink?

[QuiGon]

2 hours ago, The_Tau said:

Shouldn't they work like in Fighter-2-Fighter datalink?

 

I don't think so. AFAIK this is only for ship and Hawkeye datalink.