How To Fix Connection Issues With Our F1 Telemetry

With the correct IP and UDP port assigned in F1 26, all of your telemetry should feed directly into our platform. However, there can be some instances where this doesn’t happen. This help guide will run through the most common reasons why you could be having connection issues with our F1 telemetry, and solutions to fix them.

Why your telemetry is showing as disconnected

On the telemetry dashboard, and in our F1 overlays, there is a connection indicator. When you are not actively driving in a session, this will show as disconnected. It will only every show as connected while you are actively driving, as this is the only time telemetry packets are being sent from the F1 26 game to our telemetry platform.

This can sometimes lead to it showing as disconnected, even when you are in a game session and all telemetry settings are correct. I would recommend driving a lap to see if the indicator changes to connected and if data is shown after the lap in our telemetry platform.

If you are still seeing the disconnected messaging, continue with the troubleshooting below.

Ensure all in-game telemetry options are correct

The most common reason for telemetry data not being sent from F1 26 to our platform is an incorrect in-game telemetry setting. There are a few key settings that need to be enabled for telemetry to be sent. These include the follow.

• Telemetry: Turned on
• IP address: This should match the IP shown in your telemetry dashboard or overlays dashboard
• UDP Port: This should match the UDP Port shown in your telemetry dashboard or overlays dashboard
• UDP Format: Should be 2025 for F1 25 cars, and 2026 for F1 26 cars
• UDP Send Rate: 60Hz

Conflict with SimHub or other software

One common reason for telemetry not being correctly sent is if you are using SimHub or other software such as racing wheel software, other overlays. These other apps can try to access the same telemetry data from F1 26 that is used for telemetry, and this can sometimes cause a conflict.

Our F1 26 telemetry is designed to be compatible with SimHub and all other apps. But you will need to change the telemetry settings in F1 26 for this to work correctly.

When using SimHub, you should point your in-game telemetry to SimHub rather than to our telemetry directly. Then, in SimHub you can set up port forwarding to allow SimHub to send the telemetry top our platform. This will allow multiple apps to work simultaneously together.

Follow our complete guide for using our F1 telemetry with SimHub here, which includes detailed instructions on how to configure everything.

Firewall blocking telemetry

A less common reason why telemetry is not being recorded correctly can be an overly strict firewall. If when using our F1 telemetry, you get a popup on your PC saying “Allow” via your firewall, ensure you click “Allow”.

Alternatively, you can head into your firewall settings and create an exception for our telemetry. If you are using our overlays app, this can be done from your Firewall and Network Protection settings on your PC. Find our Overlays.exe file. Then ensure it is set to “Allow” on all networks.

VPN blocking telemetry

Another cause could be that you have a VPN enabled. Normally, our telemetry will work even with a VPN, however there are occasions when a VPN can reroute the telemetry to alternate IP addresses. This can cause the telemetry to never arrive at our server, and prevent it from being received. We recommend always disabling your VPN when using our F1 telemetry.

---