DOF Reality H6 SimHub Fix: War Thunder Motion Sim Troubleshooting

Somewhere in Witheren, a man had bolted six stepper motors to a racing seat frame, connected two STM32 microcontrollers to a Gigabyte B650M motherboard, and was now staring at the words "Access to the port COM4 is denied" while his immaculately assembled DOF Reality H6 sat completely, expensively, perfectly still. He had done everything right. The rig looked magnificent. Windows had other ideas.

This is the story of that callout - the diagnosis, the wrong turns, the eventual fix, and the one thing that finally made a 2025 motion platform reliable enough to fly Spitfires in War Thunder without it freezing mid-roll and depositing the pilot face-first into a virtual hillside.

The Problem

The DOF Reality H6 uses two STM32 BLACKPILL F401CC-based controllers, each appearing to Windows as a USB serial device - COM4 and COM5 in this case. The customer's setup was a Ryzen 5 7600 on a Gigabyte B650M Gaming WiFi, running Windows 11 Home. MOZA MRP Rudder Pedals had claimed COM3. On paper, perfectly manageable. In practice, Device Manager was showing USB descriptor request failures, yellow warning triangles on both DOF controllers, and a growing collection of ghost COM port entries - shadow ports from every unplug-and-replug that Windows had thoughtfully preserved forever like little digital fossils.

One controller would work. The other would not - and the broken one switched sides depending on which USB port it was in. That detail matters. It ruled out a faulty controller and pointed squarely at something happening at the software or driver level.

The Investigation

The first hour was spent ruling things out. Faulty USB ports - no, both controllers tested fine on a separate Windows laptop. Faulty cables - possibly, though we would not fully confirm that until a month later. Corrupt drivers - plausible, but the errors persisted on a fresh Windows install. Faulty controller boards - eliminated by the swapping behaviour.

The breakthrough came when we looked at SimHub. The customer was running SimHub to consolidate everything - bass shakers, the wind kit, motion, dashboard displays - all in one platform rather than juggling Sim Racing Studio alongside everything else. Completely reasonable choice. Except SimHub had "Scan all serial ports" enabled in its Arduino settings.

SimHub's Arduino scanner is aggressive. It locks serial ports while it queries them, trying to identify connected Arduino-based devices. The DOF Reality motion plugin - a separately licensed component - was trying to open COM4 and COM5 at the same time. SimHub got there first. Every time. The DOF plugin lost the race and threw the access denied error, which Windows then helpfully escalated into a full USB descriptor failure chain. We called DOF Reality to confirm the diagnosis and their response was unambiguous: SimHub's Arduino scanner must never be allowed to touch the DOF Reality COM ports. Full stop.

What We Tried (And What Did Not Work)

A full Windows wipe and reload was performed. Clean install, nothing carried over. The USB descriptor errors came back immediately on the fresh install - which was actually useful information. It confirmed the problem was not in the Windows installation state or accumulated software cruft. It was something more fundamental.

Both DOF controllers worked perfectly on the technician's laptop. Same cables, same controllers, different result. That is the kind of data point that makes you stop blaming the hardware and start looking very carefully at what is different about the customer's PC. On a fresh Windows 11 install on an AMD Ryzen system with a Gigabyte B650M, the AMD chipset drivers are not installed automatically. Windows installs generic Microsoft USB drivers instead. They work. They just do not work well enough for sustained USB serial communication under load from a motion platform doing real-time telemetry.

The Fix

Four things, in order. Do not skip any of them.

That resolved the COM port access errors and the USB descriptor failures. Both controllers connected cleanly. The rig moved. The customer's Spitfire banked left and the seat obligingly tried to tip him out of his chair. First genuine motion. Satisfying moment.

SimHub vs Sim Racing Studio - The Honest Version

DOF Reality ships its platforms with Sim Racing Studio (SRS). SRS is the officially supported, bundled, tested-by-the-manufacturer software. It works reliably with War Thunder out of the box, the integration is stable, and if something breaks DOF Reality can actually support you. That matters.

SimHub is what the sim racing community has quietly decided is better, and based on the telemetry customisation depth, the peripheral consolidation, and the intensity tuning granularity - they are not wrong. SimHub can run your DOF motion, your bass shakers, your wind kit, your dashboard displays, and your button box all from one application. SRS cannot do that. If you have a multi-peripheral rig and you want everything in one place with per-axis intensity curves you can actually tune, SimHub is the obvious choice.

The trade-off is that SimHub is not officially supported by DOF Reality, requires the separately licensed motion plugin, and - as this entire case study demonstrates - will aggressively fight your motion controllers for serial port access if you let it. You can have SimHub on a DOF Reality rig. You just have to configure it like someone who understands what it is doing, not someone who clicked Next a few times and assumed it would sort itself out.

War Thunder on a Motion Sim - Managing Expectations

War Thunder was not designed with motion simulators in mind. Its telemetry output rate is low enough that on a high-response 6-axis platform, untuned motion feels like the aircraft is being transported across a cobblestone road one jolt at a time. Pitch and roll telemetry is missing entirely for a range of tier 1 and training aircraft - bugs in War Thunder's own telemetry implementation that have not been fixed. Ground vehicles produce no motion data whatsoever. Naval is also silent. You are flying or you are sitting still, and that is the deal.

Within those constraints, it is genuinely achievable. The fix is telemetry intensity tuning in SimHub - reducing the response rate multipliers and adding smoothing to the pitch and roll axes so the platform interpolates between telemetry packets rather than snapping between them. It takes time to tune correctly for each aircraft class. But continuous flight in something like a P-51 or a Zero with a properly dialled H6 underneath you is a different experience to anything a chair can provide. It is worth the effort. Just do not expect it to feel like iRacing out of the box.

The One-Month Follow-Up Fix

A month after the callout, the customer reported occasional USB disconnects under sustained session load. Not frequent. Not catastrophic. Just enough to be annoying. The COM ports would drop, the rig would freeze, and everything would have to be restarted.

The fix was cables. He replaced the stock USB cables that came with the H6 with braided high-quality USB 2.0 cables. The disconnects stopped. That is it. That is the whole fix. Not a driver update, not a BIOS setting, not another round of Device Manager archaeology. Better cables. A twenty-dollar solution to what had started to feel like an existential problem.

If you own a DOF Reality platform and you are chasing USB stability, replace the cables before you do anything else. Before you reinstall Windows. Before you call anyone. Buy decent braided USB 2.0 cables from JB Hi-Fi Helensvale or order a set online, swap them in, and see if the problem evaporates. You will feel mildly cheated by how simple it is. That is normal. Welcome to IT support.

Key Takeaways

The H6 is a serious piece of hardware. It deserves a setup that matches it. If you are running one on the Gold Coast and it is not behaving, the problem is almost certainly solvable - it just requires working through the layers in the right order, not throwing reinstalls at it and hoping something sticks.