Skip to content

Games setup

Jump to bottom
Yannick edited this page Jul 9, 2025 · 44 revisions

Compatibility list

Non exhaustive list of tested games. All fully directinput compatible games should work but some games may use whitelists for specific devices or require config modifications.

Symbol Status
✅ Fully working
(Only ingame setup required at most)
☑️ Fully working with non invasive modifications
or external config changes for correct operation
⚠️ Partially or with issues
(May need third party tools, significant effort or has issues impacting gameplay)
❌ Not working at all or significant problems
(Not officially supported)
📝 Notes available below
Game Status
Assetto corsa ✅
Assetto corsa competizione ✅
Assetto corsa EVO ✅
Automobilista 2 ✅
Forza horizon 4 ☑️ 📝 (See below)
Forza horizon 5 ☑️ 📝 (See below)
Dirt Rally 2.0 ☑️ 📝 (config mod)
Dirt Rally ☑️ 📝 (config mod)
Dirt 4 ☑️ 📝 (config mod)
EA WRC ☑️ 📝 (config mod)
F1 2020 ✅ 📝 (See note)
F1 2022 ✅ 📝 (See note)
rFactor 2 ✅ 📝 (See note)
BeamNG ✅
KartKraft ✅
Project Cars 1 ✅
Project Cars 2 ✅
WRC 8 ✅ 📝
WRC Generations ✅ 📝
Trackmania 2020 ✅
DCS World ✅ (2 axis joystick)
IRacing ✅
Euro Truck Simulator 2 ✅
Raceroom ✅
Live for Speed ✅
Le Mans Ultimate ✅
Wreckfest ✅
Wreckfest 2 ✅
FlatOut 2 ✅
F1 CHALLENGE 99-02 ✅
Trackmania 2020 ✅
Mud Runner ✅
Snow Runner ❌ (Whitelisted vendors)
Moto GP 22 ❌ (xinput only)
Richard Burns Rally ✅
CarX ⚠️ (Bad FFB in general reported)
Sébastien Loeb Rally EVO ❌ ⚠️ (Crashes in control mapper
Maybe fixable or unrelated?)
Dakar Desert Rally ⚠️ (FFBoard works but other devices may interfere)
XPForce (XPlane, MSFS...) ✅

Setup procedures for specific games and recommended settings

All Dirt games

Dirt requires you to add custom devices to the device_defines.xml for example found in the DiRT Rally 2.0\input\devices path or similar.

Add this line to device_defines.xml:

<device id="{FFB01209-0000-0000-0000-504944564944}" name="openffboard" priority="100" type="wheel" official="false" />

You can also add a openffboard.xml to the actionmaps folder:

<?xml version="1.0" encoding="utf-8"?>
<action_map name="openffboard" device_name="openffboard" library="lib_direct_input">
  <axis_defaults>
    <axis name="di_x_axis">
    <action deadzone="0" name="driving.steer.left" />
    <action deadzone="0" name="driving.steer.right" />
    </axis>
  </axis_defaults>
  <group name="driving">
    <group name="steer">
      <action name="left">
       <axis name="di_x_axis" type="lower" />
      </action>
     <action name="right">
      <axis name="di_x_axis" type="upper" />
    </action>
  </group>
 </group>
</action_map>

Recommended settings:

Setting Value
CF Filter 50-80hz
CF Filter q 0.3-0.7
Range 540

EA WRC

Wheel may not be detected or not have any force feedback. In the file steamapps\common\EA SPORTS WRC\WRC\Content\input\Windows\devices\device_defines.xml add this line :

<device id="{FFB01209-0000-0000-0000-504944564944}" name="openffboard" priority="100" type="wheel" official="false" />

Add a new file openffboard.xml in steamapps\common\EA SPORTS WRC\WRC\Content\input\Windows\actionmaps with the following content:

<?xml version="1.0" encoding="utf-8"?>
<action_map name="openffboard" device_name="openffboard" library="lib_direct_input" version="2">
  <axis_map>
    <axis name="di_x_axis" direction_type="left_right" axis_set_name="device"/>
  </axis_map>
  <axis_defaults>
    <axis name="di_x_axis">
      <action deadzone="0" name="driving.steer.left" />
      <action deadzone="0" name="driving.steer.right" />
    </axis>
  </axis_defaults>
  <group name="driving">
    <group name="steer">
      <action name="left">
        <axis name="di_x_axis" type="lower" />
      </action>
      <action name="right">
        <axis name="di_x_axis" type="upper" />
      </action>
    </group>
  </group>
</action_map>

F1 Games

Disable all steering assists.

There will still be a gamepad style visual steering wheel wobble or assist in the simulated wheel for non whitelisted devices. Not confirmed if it impacts the actual input or is only visual.

Recommended settings:

Setting Value
Range 360

rFactor 2

Game appears to use Sine and Damper effects only, no constant force.

Incorrect range or rotation limit

The default for a new steering device is "Rotation limit mode: Device Driver" however RF2 does not support OpenFFB so we must set the rotation limit manually instead.

  1. Set "Rotation limit mode" to "Software"
  2. Set "Max wheel angle mode" to "Custom"
  3. Set "Default max wheel angle" to the range you have set in Open FFBoard Configurator Axis tab
  4. Set "Range set by vehicle" to "On"

Reversed FFB effects

It might be necessary to reverse the FFB forces. This was necessary on Linux when running the game through Proton as well as at least one Windows user. According to this post it may be necessary on windows in some circumstances.

There are two ways to do this:

In game controls menu

Go to Settings -> Calibrate Controls. In the "Force Feedback Settings" section click and hold the "Force feedback strength" down arrow until you reach the negative value of the percentage currently set.

In the game configuration files

In rFactor 2\UserData\player\Controller.JSON

change the following 80% example:

"Steering effects strength":8000,

To:

"Steering effects strength":-8000,

WRC Games

The games use the spring effect for FFB. Confirmed for WRC 8 and WRC Generations. Consider playing around with the spring gain to set how direct and stiff it feels.

More FFB tuning options available in steamapps\common\WRCxxx\Common\Settings\InputFFBSoftwareConfig.cfg

Recommended settings:

Setting Value
Range 540
Spring gain 10 - max

Forza Horizon 5 (or others)

The OpenFFBoard works with Forza in theory but might be more stable with emuwheel.

After FW 1.14.3: Forza motorsport supported and direction does not need to be inverted.

Recommended settings:

Setting Value
CF Filter 60-200hz
CF Filter q 0.3-0.7
Range 540
Spring 2-4
Config file

Adding a file DefaultRawGameControllerMappingProfileOpenFFBoard.xml to the media/inputmappingprofiles.zip might force it to be the primary steering device.

It is not confirmed if this actually helps at all so you may not need that.

<Profiles>
<RawGameControllerInputMappingProfile Version="1" Id="a5dcbf10-6530-11d2-901f-00c04fb951ed" UserFacingName="IDS_DefaultWheelProfile_OpenFFBoard_Name" IsDefaultProfile="1" PrimaryDeviceVidPid="0x1209FFB0" FFBDeviceVidPid="0x1209FFB0" FFBMotorIndex="0">

  <!-- Race -->
  <Context Version="1" Context="INPUTCONTEXT_RACING">
    <Value Version="1" Key="INPUTCMD_GAS" VidPid="0x044fb67f" InputType="Axis" Index="1" InvertAxis="false" InnerDeadzone="0." OuterDeadzone="1.00" />
    <Value Version="1" Key="INPUTCMD_BRAKE" VidPid="0x044fb67f" InputType="Axis" Index="2" InvertAxis="false" InnerDeadzone="0." OuterDeadzone="1.00" />
    <Value Version="1" Key="INPUTCMD_CLUTCH" VidPid="0x044fb67f" InputType="Axis" Index="3" InvertAxis="false" InnerDeadzone="0." OuterDeadzone="1.00" />
    <Value Version="1" Key="INPUTCMD_STEERING" VidPid="0x044fb67f" InputType="Axis" Index="0" InvertAxis="false" DeadzonesAroundCenter="false" InnerDeadzone="0.00" OuterDeadzone="1.00" />  
  </Context> 
  <Context Version="1" Context="INPUTCONTEXT_RACING_UI">
  </Context>

Games working with vjoy emuwheel

Forza

Also confirmed working if you still have other issues is emuwheel.

Emuwheel will merge and hide multiple devices into one virtual one getting around some of the issues forza has with incompatible devices. It will also forward FFB effects to the steering wheel device.

This tool works for games that have steering wheel whitelists blocking unknown devices but supporting vjoy.

In Dakar Desert Rally only 1 vjoy device can be present or it may use the wrong one. Sometimes it works. Sometimes not. For now unsupported.



OpenFFBoard project

Clone this wiki locally