Using a D-Mover H3

Hey everyone so I'm using the H3 D-Mover and have F1 plug in the right folder, but I can't get any Telemetry in the game, the IP is set and I put in a port # in the plug in and in game telemetry, 20777 , does it matter what port number it actually is?

I tried it with DR sim manager as well

Also im getting a lot of this error, Unable to start interface #1, what am I doing wrong why this error keeps popping up and sometimes I have to reset the rig and USB for the PC to clear it, anyone?
This is getting annoying, more than the Joy Im suppose to be having

Hi! I have the exact same motion system and I was struggling with F1 25 too. I finally managed to get SimTools to pick up the telemetry, though I must say it’s not as smooth as Assetto Corsa yet.

I solved it by using SimHub as a bridge to manage the data flow:

1. Since I use a phone as a dashboard, I have SimHub receiving the game data first.
   
   
2. In SimHub, I set up UDP forwarding to port 4123 for SimTools.
   
   
3. I also added another forward to port 20778 for the Moza R9 base (make sure your Moza software is set to listen on that same port).
   

Avoid using the game's native UDP forwarding; it creates terrible latency for the wheel LEDs and the dashboard. By routing everything through SimHub, the lag is completely gone.

If you manage to fine-tune it so the motion feels as good as it does in other sims, please let me know! I’m still working on getting the effects dialed in. In fact, I had to start a thread here to see if anyone else has managed to get F1 25 running properly: https://www.xsimulator.net/communit...telemetry-issues-on-4-actuator-d-mover.19924/

Always double-check the USB port you are using for the D-Mover. It should always be the same physical port; if you switch it, you'll need to update the settings in SimTools because it saves the specific port you initially assigned. Also, avoid using USB hubs or splitters, as they can cause connection issues or data loss.