DOF H3 Motion Platform and Sim Racing Studio setup for FSX Steam Edition

FSX-SE / SRS / SimConnect check

Hi seaportrait,

Good news first: that SimConnect output tells us FSX-SE’s SimConnect server is actually starting, so I would not begin by blaming the DOF H3 itself. Since the platform works in your other sims, this looks more like an FSX-SE/SRS connection/config issue.

The important bit is this:

SimConnect version 10.0.61259.0
Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=34455

That port is FSX’s SimConnect server endpoint. It is not the same thing as a normal “game UDP telemetry output” port. FSX does not simply broadcast motion telemetry over UDP by itself. SRS needs to connect to FSX through SimConnect, or through whatever FSX-specific module/plugin SRS expects.

So I would not assume that setting SRS to listen on:

Port: 34455

is correct just because that port appears in the SimConnect log.

What I would try first

1. Start FSX-SE first

   Load into an aircraft, sitting on the runway or ramp, with the sim fully loaded. Do not leave it at the menu screen.

2. Then start SRS

   If FSX-SE is being run as Administrator, run SRS as Administrator too. Better still, for testing, run neither as Administrator unless you specifically need to.

3. Do not use the SimConnect port as a UDP listening port unless SRS specifically tells you to

   The SRS “Game UDP Listening Port” is most likely for titles that output UDP telemetry. FSX-SE normally needs SimConnect access, not a UDP listener pointed at FSX’s SimConnect port.

4. Temporarily remove custom SimConnect network config

   If you have created or edited a SimConnect.xml while troubleshooting, back it up and test without it.

   Check both possible FSX-SE config locations, depending on how your system was installed:

   %APPDATA%\Microsoft\FSX\SimConnect.xml

   and/or

   %APPDATA%\Microsoft\FSX-SE\SimConnect.xml

   Do not delete it permanently. Just rename it for a test, for example:

   SimConnect.xml.bak

   For a local PC setup, FSX and SRS should normally be able to talk locally without you forcing an IPv4 port.

5. Check whether SRS is seeing FSX at all

   Once FSX-SE is loaded into a flight, look in SRS and see whether it reports FSX/FSX-SE as connected, detected, running, or similar. If it stays disconnected, the issue is before the motion profile even gets involved.

6. Make sure FSX is not paused or in slew

   Some motion/telemetry tools will appear “dead” if the sim is paused, in slew, in a menu, or not yet fully in the flight.

A useful test

Your SimConnect log should show some additional client activity when SRS attempts to connect. If the log only shows the server starting and nothing else after SRS is opened, SRS is probably not connecting to FSX SimConnect at all.

In that case, the problem is likely one of these:

• SRS is not using the FSX/FSX-SE SimConnect method.
• SRS is pointed at a UDP telemetry mode instead of an FSX mode.
• The needed FSX SimConnect client/runtime for SRS is missing or not being loaded.
• FSX-SE and SRS are running at different privilege levels.
• A custom SimConnect.xml/SimConnect.cfg is sending SRS the wrong way.

My hunch

Based on what you posted, I would first stop trying to match SRS to port 34455. That number is coming from FSX’s SimConnect server setup, but SRS should not normally be “listening” on that port as if FSX were sending UDP telemetry to it.

I would reset the FSX-SE SimConnect side to local/default behavior, then make sure SRS is using its FSX/SimConnect connection method rather than a generic UDP game input.

A few things that would help narrow it down

• Which version of SRS are you running?
• Does SRS show FSX-SE as detected/connected, or does it stay disconnected?
• Are FSX-SE and SRS both on the same PC?
• Did you manually create or edit a SimConnect.xml or SimConnect.cfg for FSX-SE?
• When you start SRS after FSX is loaded into a flight, does the SimConnect log add any new lines?

If you can paste the SimConnect log after starting FSX-SE, loading into an aircraft, and then opening SRS, that should tell us whether SRS is even knocking on the SimConnect door.