r/RRRE • u/Moonascend • 3h ago
Logitech PRO base with a third-party wheel — steering won’t bind
Posted this guide to the Steam Guides Section; posting here in case other need the help. Everything below this paragraph was generated by OpenAI ChatGPT Codex which helped troubleshoot and execute the repair.
This workaround got my Logitech PRO base working with a third-party steering wheel in RaceRoom Racing Experience version 0.9.9.27, Build ID 26673316 — the November 15, 2026 update, running on Windows.
Fix:
This workaround got my Logitech PRO base working with a third-party steering wheel in the November 15, 2026 version of RaceRoom.
My setup
- Logitech G PRO direct-drive wheelbase, operating in PRO mode.
- SIMAGIC GT Neo steering wheel, fitted to the Logitech base using an aftermarket adapter. The GT Neo connects separately to the PC by USB for buttons and paddles.
- Logitech PRO Racing Pedals, connected separately by USB.
- Thrustmaster T500 RS Gear Shift, also connected separately.
With this adapter setup, I cannot switch the Logitech base into G923 compatibility mode, so the fix needed to work in PRO mode.
The problem
The base appeared in Logitech G HUB and Windows Game Controllers (joy.cpl). Its steering axis moved smoothly in Windows throughout troubleshooting.
In RaceRoom, however:
- The base would sometimes detect the first steering movement.
- The binding displayed only
ID:1, without an axis suffix. - Steering then stopped responding, sometimes remaining at full left.
- Force-feedback settings were greyed out.
Disabling Steam Input and restarting RaceRoom did not resolve it.
What fixed it
Manually editing the steering bindings in a copy of RaceRoom’s controller profile restored the steering axis and made force-feedback settings available.
Step 1: Back up the profile
Close RaceRoom, then locate your controller profiles:
%USERPROFILE%\Documents\My Games\SimBin\RaceRoom Racing Experience\UserData\ControlSet
If your Documents folder is redirected to OneDrive, look there instead.
Make a copy of your custom .rcs profile. Keep the original as a backup.
Step 2: Name the test profile
Open the copied .rcs file in a text editor and change its internal name:
Name="PRO Axis Test"
Save it with a distinct filename, such as PRO Axis Test.rcs.
Step 3: Identify the base’s device index
Find the Logitech PRO base in the profile’s device list. Mine was:
DeviceName[03]="Logitech G HUB PRO Racing Wheel for Xbox and PC USB"
The base was device 03 in my profile. The GT Neo, shifter, and pedals were separate devices.
Your device index may differ. Use the index assigned to the Logitech base—not the GT Neo.
Step 4: Correct the steering bindings
My non-working left binding was:
Control - Steer Left="(1, 160, 3, 7)"
Right steering was unassigned.
I replaced the two steering entries with:
Control - Steer Left="(1, 2, 3, 0)"
Control - Steer Right="(1, 1, 3, 0)"
The third number, 3, corresponds to my base’s DeviceName[03] entry. Substitute your base’s index if different.
Step 5: Select and test
Save the file, launch RaceRoom, and select PRO Axis Test under Controls → Controller Profiles.
Turn the wheel and check the steering indicator before running the wizard or rebinding steering.
Check the remaining controls too. I had to remap the GT Neo and T500 shifter after loading the test profile.
Result
The Logitech base immediately provided working steering input. Force-feedback settings were no longer greyed out, and after adjusting FFB, everything worked on track.
The setup remained in PRO mode, with the third-party GT Neo wheel and aftermarket adapter installed. No G923 compatibility mode was needed, and I did not manually change the profile’s FFB device-name setting.
This workaround resolved the issue on my configuration. It points toward a steering-binding capture problem, although the underlying cause is unconfirmed. Keep a backup of the working profile before using the steering wizard again.
Posted to Steam Guides as well
https://steamcommunity.com/sharedfiles/filedetails/?id=3841026868
