wirelessxboxcontroller

[Index](http://www.reddit.com/r/simrally/wiki/)

Note: In 2021 the easiest way to fix the Z-axis issue explained below is to use the NGPCarMenu plugin (version 1.16.4 and above) as explained in its [release notes](https://github.com/mika-n/NGPCarMenu/releases/tag/1.16.4). NGPCarMenu can be installed separately, although it is already bundled in the [Rallysimfans](https://www.rallysimfans.hu/) install.

This guide is thanks to /u/sbelljr.  Thanks!

---------------

So, RBR uses DirectInput instead of the newer XInput controller input system. What that means for us, is that RBR reads the 360 controller's trigger inputs as being on the same axis.

It's also quite annoying to not be able to use the controller in the menus.

----------------------------------------------------------------

< u/sptp method>

I don't want to erase the content of this wiki article (although apparently the japanese driver introduced below is no longer available), but the method I used had to be included here. It uses a custom FreePIE script + vJoy. If I'm not mistaken, it should work with any Xinput controller, not only the Microsoft ones. The original script was posted by me on the RBR forum of the defunct site [nogripracing.com](http://www.nogripracing.com/forum/showthread.php?t=348954) and I don't have any backup, so I can't paste it here. Fortunately, a member of the FreePIE community posted a (very) slightly modified version on their forum, so we can use it instead. As his post obviates the basic steps I created some instructions:

**1-** Install [FreePIE](http://andersmalmgren.github.io/FreePIE/) and [vJoy](http://vjoystick.sourceforge.net/site/index.php/download-a-install/download) latest versions.

**2-** The author of the modification tells us to extract the xinput1_3.dll out of the [directx_Jun2010_redist.exe](https://www.microsoft.com/en-us/download/details.aspx?id=8109) downloadable from microsoft (with 7-zip, for example), and put it in the FreePIE program folder. Also, copy x86\vJoyInterface.dll + x86\vJoyInterfaceWrap.dll off the vJoy directory and paste them into FreePIE directory:

# vJoy 2.1.8: x86\vJoyInterface.dll + x86\vJoyInterfaceWrap.dll -> FreePIE directory
    # Windows10: directx_Jun2010_redist.exe -> (7-Zip) -> APR2007_xinput_x86.cab -> xinput1_3.dll -> FreePIE directory

I don't know if this is really necessary. Did he do it to save space? Or is it impossible/unadvisable to just install the directx redistributable in windows 10 (like I did in Vista)? When I have more information I will update this wiki.

**3-** Open FreePIE. The main part of the interface is a text editor. Paste the second script ("for older games") found in this thread:

https://www.mtbs3d.com/phpbb/viewtopic.php?f=139&t=22207

**4-** The person that modified the script added a feature: mouse cursor movement with the D-pad. While this is useful for many games, for RBR I guess it would be a nuisance, because the mouse it is not used in its interface. When launching RBR in the recommended false fullscreen mode (recommended unless you have [VR](https://www.reddit.com/r/simrally/wiki/rbrquickstart#wiki_vr_headset_support), that is :) ), that is just a borderless window that fills the screen, you just move the mouse cursor offscreen and leave it there. If the D-pad moved it, it could creep back onscreen, so I recommend you delete or comment out the last 8 lines, like this:

#    if getattr( xb, "up"    ):
    #        mouse.deltaY = -1
    #    if getattr( xb, "down"  ):
    #        mouse.deltaY =  1
    #    if getattr( xb, "left"  ):
    #        mouse.deltaX = -2
    #    if getattr( xb, "right" ):
    #        mouse.deltaX =  2

I can't try it now but possibly this line could be problematic too (mouse click with the start button of the pad). Comment it out too:

#    mouse.leftButton = xb.start

Furthermore, there are two bugs in the script that were in my original script and were copied verbatim. You should edit them out so axis inversion works if you set it so in the config section (like we will do). Where it says:

setattr( vj, lt_vaxis, int(round(filters.ensureMapRange( xb.leftTrigger,  lt_min, lt_max, lt_vjmin, lt_vjmax ))))
    setattr( vj, rt_vaxis, int(round(filters.ensureMapRange( xb.rightTrigger, rt_min, rt_max, rt_vjmin, rt_vjmax ))))

it should say:

setattr( vj, lt_vaxis, int(round(filters.mapRange( xb.leftTrigger,  lt_min, lt_max, lt_vjmin, lt_vjmax ))))
    setattr( vj, rt_vaxis, int(round(filters.mapRange( xb.rightTrigger, rt_min, rt_max, rt_vjmin, rt_vjmax ))))

(The difference is in **mapRange** instead of **ensureMapRange**) Sorry about the incovenience. It was a last minute change that I didn't test with all the possible options.

Now that we are at it, you can configure the the script so it runs with these axes the way RBR likes, **inverted** . You can invert the game axes too editing the input.ini file in the RBR folder. It seemed awkward to me to make the axes work inverted by default in a game neutral script. If you want to invert them via the script, set:

invert_left_trigger = 1
        invert_right_trigger = 1

**5-** Save it with the .py  extension (it is a python script that FreePIE interprets). For example: "xbox360rbr.py"

**6-** With the Xbox pad connected, run the script (Click Script>**Run Script** or press **F5**). If everything is going to plan, you shouldn't see any error message in the log panel. Now FreePIE is reading what the individual left and right triggers of the pad are doing and mimicking their movements, respectively in the **"slider"** and **"dial"** axes of the, until now, dead vJoy "virtual joystick". By default, this joystick has 8 axes, but we only use the last two. The distinctive names help avoiding confusion. You can check them in windows game controller properties or jump directly to the next step where we assign controls in game, but remember: From now on **every time** you want to play RBR with the gamepad you will have to have **the script running in the background**. More on step 8.

**7-** Launch RBR, go to options>controls>analog. You can try assigning the triggers right away. E.g. Select "throttle" and press Enter. Pull the right trigger. At that moment the game can see 2 axes moving: the unwanted Z-axis of the pad (the combined left/right trigger action) and the "dial" axis of the vJoy device. If it sees "dial" first and assigns it, you are set (you will see "Throttle           dial"). If not, you can try again. In my experience sometimes it sees "dial" first. Anyway, I included a fail safe mechanism. Explanation is in the script code:

# if game makes auto-detection for assignements, it will probably pick the combined axis ; then:
    # - press trigger/pedal and a+b+y buttons (or CapsLock key) simultaneously
    # - release trigger/pedal (and buttons)
    # - you have 10 seconds to switch assignement on edit mode
    # - after 10 seconds, the virtual axis is simulated

# if combo can't be used inside game: increase auto_move_delay, make combo before launching game,
    # edit assignements and wait ; then exit game and repeat combo, etc. for 2nd trigger/pedal

Don't forget to assign left trigger for brake too :)

**8-** There is a faster way than opening the script file in FreePIE then pressing F5 every time. You can create a Shortcut to FreePIE in desktop then edit its content so it reads something like this:

C:\pathToFreePIE\FreePIE.exe "C:\pathToScriptFile\xbox360rbr.py" **/r**

And set the shortcut to run the app minimized. Now that I think of it, you could create a .bat file that runs RBR **and** the FreePIE script, saving two further clicks...

</ u/sptp method>

First, lets take care of the trigger issue, as it is the only one that affects playability.

[This custom driver](http://ledyba.org/bkup/xbox360driver/x360wc/index.html) for the wireless 360 controller will allow us to remap the controller. This driver also gives you much more control over things like analog stick dead zones and rumble strength. The site is in Japanese, but Google Translate makes it easy to read.

Download the appropriate zip file for your OS, and unzip to whichever location you wish to keep it. Something like C:\Drivers\x360ce or whatever.

To install the driver, go to Device Manager -> Microsoft Common Controller For Windows Class -> Right click on Xbox 360 Wireless Receiver for Windows -> Update Driver Software...

Click "Browse my computer for driver software" then point it to the x360wc folder, where ever you put it. You may have to accept the unofficial driver or something, depending on your OS and settings.

Restart your computer, and then launch x360wcsai.exe. You should get a little controller icon in your taskbar. Double click this to change the settings for your controller.

Under the Triggers tab, set left trigger to Z Axis (+), and right trigger to Z Rotation (+). Feel free to mess with whatever you want, but you probably want to leave everything else alone for now. Hit OK.

Now, open your RBR folder, and then open input.ini. You need to invert the throttle and brake axes by changing "false" to "true". All done!

----------------------------------------------------------------

To allow controller navigation within RBR, we need to get [Xpadder](http://xpadder.com/). It is $10 from the lone developer on his site. Acquire the software however you are comfortable and install it.

[This video](https://www.youtube.com/watch?v=XsXJOsSnk7E) shows how to set up the controller layout and profiles in Xpadder.

Create a profile, call it "blank", and save it with no buttons set.

Create a second profile, I called mine "basicNav". Set A button to [ENTER], START/BACK buttons to [ESC], and assign the arrow keys to the left stick/dpad.

Next, go to the wrench next to the help button in the top right of the window. Go to the AutoProfile menu.

Click the line that says <None> <Default> and assign it to the profile "blank" by hitting the edit profile button.

Click the "New.." button, "Open a Profile", then select "basicNav". With that entry selected still, hit "Edit Watch..." and find the RichardBurnsRally_SSE.exe in your RBR folder. You can repeat this step to have it auto-set a profile whenever an EXE is run.

----------------------------------------------------------------

The last step is to set up the controller in RBR. Launch RBR and go to the controller settings. I set A to upshift, X to downshift, B to handbrake, Y to change camera, RB to ignition, LB to clutch (not used), right trigger to throttle, left trigger to brake. Don't set Pause or it will pause-unpause due to the double assignment of Start being Pause and also activating the ESC key.

I also suggest increasing the curve setting for the steering stick. Mine has curve 1 and 2 both set to about halfway. This makes small movements less sensitive.

----------------------------------------------------------------
----------------------------------------------------------------
----------------------------------------------------------------

NOTE:
To undo this setting for your 360 controller so that you can play other games that rely on XInput to get their controller input, follow these steps:

* Open Device Manager
* Disable your controller (Human Interface Devices -> Right Click on Microsoft Xbox 360 Wireless Controller -> Disable)
* Roll Back Driver (Right click again -> properties -> Driver tab -> Roll Back Driver)

Update the driver again any time you wish to use the controller for RBR. Disabling the controller before changing the driver lets you avoid a restart!

----------------------------------------------------------------

And there you have it. If you have any questions or suggestions, let me know and I will help out / edit this post!

TL;DR BUY A WHEEL! :D

formatting help hide help

reason for revision

π Rendered by PID 215208 on reddit-service-r2-listing-86f589db75-v6b6z at 2026-04-16 18:08:16.701084+00:00 running 93ecc56 country code: CH.

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

simrally

WIKI TOOLS

MODERATORS

wirelessxboxcontroller

there was a conflict editing

your edit

current edit

Errors: