![]() |
|
#6
|
|||
|
|||
|
from the DeviceLink.txt file im your IL2 root folder
The DeviceLink interface is meant to provide the third-party software with the current condition of the player's aircraft as well as allow an unified method of connecting alternative operating controls. DeviceLink utilizes the UDP protocol to transfer the data. In this network, IL2 plays a part of the server. The external application sends a query packet, in reply, IL2 sends back one (or several) packets containing the query result. Proposing using the protocol within a single computer, ar a local network, no data encoding is used and data integrity CRC-checks are not taken. Packets do contain only symbolic information, the allowed range is (0x21-0x7e)..... How this is used varies and requires some sort of program to collect/send the data. There is also a restriction on some of the 'instrument' type output readings in online play. What can it be used for? displaying gauge outputs on a second screen driving 'physical' gauges in a simpit charting flight parammeters (to prove fm right/wrong) allowing 'unconvential' control devices (such as midi keyboards) is a brief/ non exhaustive list |
| Thread Tools | |
| Display Modes | |
|
|