[Bug] Forza Horizon 6 telemetry packets received at full rate, but SimHub dashboards update only every ~10 seconds

[djorourke-lgtm]

Describe the bug

Environment:

• SimHub version: 9.11.13
• Game: Forza Horizon 6, Xbox app / Microsoft Store version
• Windows: Windows 11
• Game package/process:
  Microsoft.ForteBaseGame_3.353.145.0_x64__8wekyb3d8bbwe
  process name: forzahorizon6

Symptoms:

• SimHub detects the game as running.
• Built-in SimHub dashboards do update, but only every several seconds, often around 10 seconds behind.
• This happens on a monitor connected directly to the PC and also when viewing the dashboard from an iPhone, so it does not appear to be dashboard rendering or browser/network display latency.
• The issue occurs on ports 8000 and 29000.
• The issue occurs with Forza Data Out set to both 127.0.0.1 and the PC LAN IP.

Forza settings:

• Data Out: On
• IP Address tested: 127.0.0.1 and 192.168.4.50
• Port tested: 8000 and 29000

Loopback:

• Loopback exemption applied successfully:
  microsoft.fortebasegame_8wekyb3d8bbwe

SimHub UDP binding:
PowerShell confirms SimHub is bound to the test port:

LocalAddress: 0.0.0.0
LocalPort: 29000
ProcessName: SimHubWPF

Raw UDP packet test:
With SimHub closed, a PowerShell UDP listener on port 29000 receives live FH6 packets at roughly 128 to 140 packets/sec while driving. Packets drop to 0 when FH6 quits.

Example output:
17:58:21 packets/sec: 128
17:58:22 packets/sec: 128
17:58:23 packets/sec: 128
...
18:05:47 packets/sec: 131
18:05:48 packets/sec: 133
18:05:49 packets/sec: 93
18:05:50 packets/sec: 0
18:05:51 packets/sec: 0

Expected behavior:
SimHub dashboards should update live at normal telemetry rate.

Actual behavior:
SimHub dashboards only update every several seconds, despite live UDP packets being available at full rate.

Question:
Is FH6 using a packet format that differs from FH5, causing SimHub to detect the game but only partially decode or update telemetry values?

SimHub version

9.11.13

Third-party plugins

• I have disabled all third-party plugins.

Steps to reproduce

1. Install and launch Forza Horizon 6 through the Xbox app / Microsoft Store version.

2. In Forza Horizon 6, enable Data Out.

3. Set Data Out IP Address to 127.0.0.1.

4. Set Data Out IP Port to 29000.

5. In SimHub, configure the Forza Horizon profile to listen on UDP port 29000.

6. Confirm SimHub is bound to the port using PowerShell:

   Get-NetUDPEndpoint | Where-Object {$_.LocalPort -eq 29000} |
   Select LocalAddress,LocalPort,OwningProcess,@{
       Name="ProcessName";
       Expression={(Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue).ProcessName}
   }
   

Result:

LocalAddress: 0.0.0.0
LocalPort: 29000
ProcessName: SimHubWPF
Launch Forza Horizon 6 and enter the driving world.
Open a default built-in SimHub dashboard showing basic telemetry such as speed, RPM, gear, throttle, or brake.
Observe that SimHub detects the game as running, and the dashboard does update, but only every several seconds instead of live.
Repeat the same test using 8000 as the UDP port. The same issue occurs.
Repeat the same test using the PC LAN IP address instead of localhost, for example 192.168.4.50. The same issue occurs.
Close SimHub and test the raw UDP stream directly with PowerShell on port 29000. Forza sends packets continuously at roughly 128 to 140 packets/sec while driving, and packets stop when the game quits.

Expected behavior

SimHub should decode and apply Forza Horizon 6 telemetry live, with dashboards updating smoothly and continuously while the car is being driven.

Since Forza Horizon 6 is sending UDP packets at roughly 128 to 140 packets/sec, basic dashboard values such as speed, RPM, gear, throttle, and brake should update in near real time.

Screenshots

No response

📁 Log files

SimHub.1.txt
SimHub.2.txt
SimHub.3.txt
SimHub.4.txt
SimHub.5.txt
SimHub.7.txt

Additional context

I tested this with all third-party plugins disabled.

This does not appear to be a dashboard display issue. I tested using default built-in SimHub dashboards on a monitor directly connected to the PC, and also by viewing the dashboard wirelessly from an iPhone. Both showed the same delayed update behavior.

This also does not appear to be a basic UDP output issue from the game. With SimHub closed, a PowerShell UDP listener receives live packets from Forza Horizon 6 at approximately 128 to 140 packets/sec while driving. When Forza Horizon 6 quits, packets drop to 0.

Example raw UDP packet test output:

17:58:21 packets/sec: 128
17:58:22 packets/sec: 128
17:58:23 packets/sec: 128
17:58:24 packets/sec: 128
17:58:25 packets/sec: 129
...
18:05:47 packets/sec: 131
18:05:48 packets/sec: 133
18:05:49 packets/sec: 93
18:05:50 packets/sec: 0
18:05:51 packets/sec: 0

Forza Horizon 6 appears to be running under this Xbox app / Microsoft Store package:

Microsoft.ForteBaseGame_3.353.145.0_x64__8wekyb3d8bbwe

The running process name shown in PowerShell is:

forzahorizon6

Loopback exemption was applied successfully:

microsoft.fortebasegame_8wekyb3d8bbwe

The issue occurs with:

127.0.0.1:8000
127.0.0.1:29000
192.168.4.50:29000

SimHub confirms the game is running, but built-in dashboards only update every several seconds. My suspicion is that FH6 telemetry packets are arriving correctly, but SimHub may not be decoding or applying the FH6 packet data correctly.

[xiyivan]

Same issue encountered here. FH6 dashboard only refreshs every few seconds. Detected 100 packets/s in the raw telemetry port, and 200 packets/s in the simhub forward port. The dashboard is running on the same local machine as the game instance. Running a fresh installation of simhub with stock dashboard and no plugins.

[SHWotever]

Hi ! could you check the following advices ? https://github.com/SHWotever/SimHub/wiki/DashStudio-performance Overall forza bveing hand to hand with microsoft they are likely to squeeze any perfroamnce out of game mode and similar priority systems, making simhub left with barely no ressources.

[xiyivan]

Hi, @SHWotever thanks for the information. @djorourke-lgtm I was able to have simhub running normally by forwarding the package to another device in the same network, so I assume it is indeed related to the resource match between simhub and fh6.