> For the complete documentation index, see [llms.txt](https://raia-software-inc.gitbook.io/tacview/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://raia-software-inc.gitbook.io/tacview/features/tacview-advanced/real-time-telemetry.md).

# Real-Time Telemetry

When using DCS World, X-Plane, Microsoft Flight Simulator, Falcon BMS, or the public protocol, you can connect Tacview to your simulator in real-time. Here are instructions for each simulator.

### With DCS World, X-Plane, or Microsoft Flight Simulator

#### On the Same Computer

* Start flying in your favorite flight simulator
* Open Tacview
* Go to `Recording -> Real-Time Telemetry`, enter `localhost` as your address, and `Connect`.

![Real-Time Telemetry - Same Computer](https://681332907-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ9tiJ3xbT7zyJ4FlZiMM%2Fuploads%2Fgit-blob-230bdd093b51e20c59c1cb0f727864726dc15f79%2Frtt-same-computer.png?alt=media)

* You should start seeing your flight in Tacview immediately

#### On Two Different Local Computers

* Ensure the port 42674 (or your chosen port) is open on your firewall
* Start flying in your favorite simulator on Computer # 1.
* Make sure you know the Local IP Address of this computer – open a command prompt and type `ipconfig` to find it.

![Real-Time Telemetry - ipconfig](https://681332907-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ9tiJ3xbT7zyJ4FlZiMM%2Fuploads%2Fgit-blob-fcdfbf8152fd25583ff62862b6de9a0f53dba153%2Frtt-ipconfig.png?alt=media)

* Open Tacview on computer #2
* Go to `Recording -> Real-Time Telemetry`, enter the Local IP Address of computer #1 and click Connect.

![Real-Time Telemetry - Different Computer Same Network](https://681332907-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ9tiJ3xbT7zyJ4FlZiMM%2Fuploads%2Fgit-blob-bb51e1309c44cecfa755a989b3b360d4df4b12e9%2Frtt-different-computer-same-network.png?alt=media)

#### On Two Computers on Different Networks

* Make sure the port 42674 (or your chosen port) is properly redirected on the router of the computer which is hosting the flight session.
* The host must advise the client of the host's public IP address (the host can find his public IP address on Google or other sites such as <https://icanhazip.com/>) and Tacview Host Telemetry Password if applicable. Leave password field blank if no password is desired.

![Real-Time Telemetry - What is my IP](https://681332907-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ9tiJ3xbT7zyJ4FlZiMM%2Fuploads%2Fgit-blob-70bc3cf7b3dd99443a4e23424929b12e02fc29bc%2Frtt-what-is-my-ip.png?alt=media)

* The host starts flying in their favourite simulator
* The client opens Tacview and goes to `Recording -> Real-Time Telemetry`, enters the Public IP Address of the host, along with port and password as applicable, and clicks `Connect`.

![Real-Time Telemetry - Different Networks](https://681332907-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ9tiJ3xbT7zyJ4FlZiMM%2Fuploads%2Fgit-blob-a3cce5fe4f5c0db7d55275537828eacacf173b50%2Frtt-different-computer-different-network.png?alt=media)

### Real-Time Telemetry with Falcon BMS

For Real-Time Telemetry with Falcon BMS, see the [Falcon BMS User Guide](https://github.com/RaiaSoftwareInc/tacview.documentation/blob/main/falcon-bms.md)

### Real-Time Telemetry via the Public Protocol

With Tacview Advanced and above, you can stream telemetry data in real-time using the public protocol described in this [documentation](/tacview/technical-documentation/real-time-telemetry-public-protocol.md).

The password must be a crc64 of the UTF-16 text password (not UTF-8).

The crc64 is well documented on the internet, but here is some [c++ source code](https://ln5.sync.com/dl/8f8cd8f70/th8uqueu-6prad3iz-astnm6xb-jpuby4n2) to calculate it.

For example, for the password `L"test"` the corresponding crc64 will be `0x38e095a027baf2bc`

Please note that when Tacview tries to connect to real time telemetry, it uses the official 64-bit CRC hash first for the password. If this fails, it retries with a 32-bit CRC hash. This is because DCS2ACMI is still using 32-bit CRC hash, and Tacview must compensate for that. Anyone writing their own exporter must use 64-bit CRC hash.