Pacedex PT EN ES
Tutorial · compatibility

Pacedex alongside SimHub, MOZA Pit House or another PC

Want Pacedex and SimHub (or MOZA Pit House) reading the same race? You can. Change one port in the other app and flip one switch in Pacedex. Takes 2 minutes. In the screenshots, the yellow outline shows where to click.

Before you start, you need:
  • Pacedex already receiving the game. Not yet? Do your first race first.
  • The other app installed: SimHub, MOZA Pit House, or a telemetry app on another PC.
  • The game sending to port 20777 (the default).
Part 1

Why only one app receives

The game sends telemetry to one port. Only one app at a time can listen on a port.

1

The problem: two apps on the same port

Diagram
F1the game
20777
Pacedex20777
SimHub20777

Windows hands each packet to just one of them. One works, the other sits idle. Sometimes they swap mid-race.

2

The fix: Pacedex receives first and forwards

Diagram
F1the game
20777
Pacedex20777
forwards
SimHub20888

The game stays as it is, sending to 20777. Pacedex listens on 20777 and sends a copy of every packet to the other app, on a port of its own: 20888.

Part 2

Change the port in the other app

The other app moves off 20777 and listens on 20888. We don't have screenshots of these apps: the pictures below are diagrams.

1

In SimHub: set the F1 port to 20888

Open SimHub and go to the F1 game you play (F1 24 or F1 25). In the game settings, find the UDP port. It's 20777 by default. Change it to 20888.

SimHub · F1 game · telemetry
UDP port20888
Diagram, not a screenshot — names vary by SimHub version
⚠️SimHub offers to configure the game for you? Don't let it change the game's port. The game stays on 20777, sending to Pacedex.
2

In MOZA Pit House: same thing, port 20888

In Pit House's telemetry settings for the F1 game, change the port from 20777 to 20888.

MOZA Pit House · F1 · telemetry
Port20888
Diagram, not a screenshot — names vary by Pit House version
3

Turned on UDP Forwarding in the other app before? Turn it off

Before, the other app forwarded to Pacedex. Now it's the other way round. If both forward, packets bounce back and forth.

Part 3

Turn on forwarding in Pacedex

One switch and one number.

1

Click the gear (Settings) → Game connection

The Settings cards with the Game connection card highlighted, receiving on port 20777

The card says receiving · port 20777: Pacedex stays on the game's port. Leave it alone.

2

Find the Forward telemetry to other apps row and flip the switch

The Game connection section with the Forward telemetry to other apps row highlighted, still off
3

Keep the IP 127.0.0.1 and type port 20888

127.0.0.1 means this PC. Click outside the box: it saves by itself.

The Forward telemetry to other apps row switched on, with IP 127.0.0.1 and port 20888
⚠️The number vanished from the box? You typed Pacedex's own port (20777). The packet would loop back to Pacedex, so it clears it. Use 20888.
💡Shortcut: when Pacedex spots SimHub on the same port, the yellow bar No telemetry data arrived on port 20777. shows a Pacedex first: forward to SimHub on port 20888 button. It does step 3 for you. Then just do Part 2.
Part 4

Check it works

Get on track. Both apps should move together.

1

Look at Pacedex: receiving · port 20777

The Game connection card saying receiving on port 20777

The green light stays on. The live dashboard carries on as normal.

2

Open SimHub (or Pit House) and watch the data move

Speed, gear, revs: all moving with the car. Every packet reaches both, instantly.

💡We tested it with a sample race: the app on port 20888 got about 95 packets per second, the same as Pacedex.
Part 5

Another PC on the network

Telemetry app running on another computer? Pacedex sends it there.

1

Find the other PC's IP

On the other PC, open Command Prompt and type ipconfig. Note the IPv4 Address, something like 192.168.0.25.

2

In Pacedex, swap in the other PC's IP and the port its app listens on

Port 20777 is free over there, so it can be that one.

The Forward telemetry to other apps row with another PC's IP 192.168.0.25 and port 20777
⚠️Nothing arrives there? Both PCs must be on the same network. And the firewall on the other PC must let its app receive.

Two apps at once?

The screen has room for one destination. Pacedex accepts up to 5, but the extra ones only via the config file:

  1. Close Pacedex: the PD icon by the clock → Quit.
  2. Open the %APPDATA%\pacedex folder and the overlay_config.json file in Notepad.
  3. Make the forwarding line look like this, one destination per app, and save:
"udp_forward": ["127.0.0.1:20888", "127.0.0.1:20999"],

Open Pacedex again. Careful: touching the boxes on screen afterwards brings it back to a single destination.

Something went wrong?

  • The other app gets nothing: is the port the same in Pacedex and in the other app (20888)? Is the forwarding switch on? Are you on track? The game sends nothing from the menus.
  • Pacedex stopped receiving (yellow bar): the other app is still on 20777 and grabbed the port. Change its port (Part 2) and reopen both.
  • The game's port changed: some app reconfigured the game. In F1: Settings → Telemetry Settings → UDP Port back to 20777.
  • Everything stutters or data repeats: the other app is also forwarding to Pacedex. Turn its UDP Forwarding off. One forward only: Pacedex's.
  • Lag in the other app: Pacedex forwards the instant a packet arrives. On the same PC there's no delay. For another PC, use a cable rather than Wi-Fi.

Still stuck? Post a screenshot on our Discord and we'll help.

TutorialYour first raceFrom download to the engineer on the radio. GuideF1 telemetry setupThe right port, format and rate on PC and console.

Both apps, the same race

Free, on your PC, for F1 24, F1 25 and the 2026 Season Pack.

Free download · Windows →

The full install guide →