Tom Clancy's Rainbow Six: Vegas

Tom Clancy's Rainbow Six: Vegas

28 ratings
Getting an Xbox360 controller to work with Rainbow Six: Vegas
By markzwaan
This guide will help you to get your (wireless) Xbox360 controller working with Rainbow Six: Vegas.
   
Award
Favorite
Favorited
Unfavorite
Introduction
The game ran just fine but didn't recognize my wireless Microsoft Xbox360 controller. I couldn't find a solution in the Steam forums but after a short Google search I found a working solution in the Ubisoft forums. The solution isn't mine but I can confirm that it works like a charm!
Changing the config file
Each game controller or game pad produced has its own "product ID" or 'PID'
The problem is that the controller game is looking for has the wrong PID.

You need to go into the config file and change it.
This may seem daunting, but it is really very easy.

Open the folder into which Steam has installed the game and go to the folder called "Kellergame", then open the "Config" folder and finally the "PC" folder. There is also a file called PCKellerJoysticks in the Config folder but changing that won't help!!

Open the file "PCKellerJoysticks" (u can just double click on it and it will open in notepad as a text file)

The top few lines will read:
[Joystick0]
ProductName=XBox Controller HID Minidriver, XID
VendorID=***some number (a)**
ProductID=***some number (b)**
Joy1=XboxTypeS_A
Joy2=XboxTypeS_B
Joy3=XboxTypeS_X
Joy4=XboxTypeS_Y

you have to change (a) to 1118.

Now, you need to find out what your Product ID is. Before that though, two very likely IDs are :673, and 1817, so try each of those first.
(to check them, change the number, save the file, and then run the game and try to turn on the "use 360 controller" option in the game.)
Finding your controller PID
If neither of those work, you will have to find out what your PID is manually.

Go to Device manager and under "Human Interface Devices" there will be your game controller. (if they also appear under "universal serial bus controllers")

right click on your controller and chose "properties"
In the window that appears select the details tab. Go to tje drop-down menu and choose "Hardware Ids"

In the "values" box you will see something that looks like this:

HID\VID_045E&PID_0719&IG_00
HID_DEVICE_SYSTEM_GAME
HID_DEVICE_UP:0001_U:0005
HID_DEVICE

Those are the ID's of your controller.
(Do not worry if your values are slightly different.)

What we will focus on is the first line at the top (HID\VID_045E&PID_0719&IG_00)

Let me translate: Human Interface Device (HID)\Vendor ID(VID) 045E (the number 1118 in hexadecimal) & Product ID (PID)**YOUR PRODUCT ID** and then the rest doesn't matter.

What you are looking for is the PID. (mine is 0719)

BUT WAIT!
That number is in hexadeximal digits. Google "hexadecimal converter" or something along the line of that, and convert what your PID is into deciaml digits.

TA DA!
You now have your product ID so that you can go into the PCKellerJoysticks file and change (b) to your PID
Config file
Although the controller will now work with the game, the controls might be screwy, so you need to add this line in : "UseXInput=true"

Mine now looks like this:

[Joystick0]
ProductName=XBox Controller HID Minidriver, XID
VendorID=1118
ProductID=1817
UseXInput=true
Joy1=XboxTypeS_A
Joy2=XboxTypeS_B
Joy3=XboxTypeS_X
Joy4=XboxTypeS_Y
Joy5=XboxTypeS_RightShoulder
Joy6=XboxTypeS_LeftShoulder
Joy7=XboxTypeS_LeftThumbstick
Joy8=XboxTypeS_RightThumbstick
Joy9=XboxTypeS_Start
Joy10=XboxTypeS_Back
Joy11=
Joy12=
Joy13=
Joy14=
Joy15=
Joy16=
Axis_X=XboxTypeS_LeftX
Axis_Y=XboxTypeS_LeftY
Axis_Z=XboxTypeS_RightX
Axis_Rotation_X=
Axis_Rotation_Y=
Axis_Rotation_Z=XboxTypeS_RightY
Slider_0=XboxTypeS_RightTrigger
Slider_1=XboxTypeS_LeftTrigger
DPadUp=XboxTypeS_DPad_Up
DPadDown=XboxTypeS_DPad_Down
DPadLeft=XboxTypeS_DPad_Left
DPadRight=XboxTypeS_DPad_Right
Acknowledgements
I didn't come up with this solution myself, but found it on the Ubisoft forums (of Rainbow Six: Vegas 2) so this fix should work for that game as well.
Thanks to jg_guy and sprinkill1980 (who pointed out that you have to go to the PC subfolder) .
15 Comments
D_Block35 1 Sep, 2024 @ 11:17am 
Has Anyone tried this with a PS4 controller?
ThreeSon 1 Sep, 2023 @ 12:46am 
Does anyone know how to get this working if we are using Steam Input? There doesn't seem to be a way to get the hardware and product IDs.
~~Dead4Life~~ 5 May, 2023 @ 9:06am 
I plug and play and works.
El Rojo Grande 29 Mar, 2023 @ 6:32pm 
Thanks for posting the fix. Same configuration works for both my Bluetooth converted Stadia and Xbox 360 controllers. :steamthumbsup:
zappinnati 11 Mar, 2023 @ 10:39pm 
Great guide! I'm using Windows 11 and the file KellerJoysticks.ini did not exist in the folder "C:\Program Files (x86)\Steam\steamapps\common\Rainbow Six Vegas\KellerGame\Config\PC". I copied the file from the Config folder to the PC folder and used the following (for a wireless Xbox Series X controller).

[Joystick0]
ProductName=XBox Controller HID Minidriver, XID
VendorID=1118
ProductID=2835
UseXInput=true
WongJP 3 Jul, 2021 @ 9:09pm 
Xbox One Wireless Controller (Bluetooth):
I have this model and was able to get it working by applying the above steps with this info:

ProductName=XINPUT compatible HID device
VendorID=1118
ProductID=736
UseXInput=true

ALSO / THIS MIGHT HELP TOO:
Inputting these didn't make it fully work, however - I'd fire up the game and the control sticks weren't working, LT was acting as the confirm (A) button etc.

The fix for that?
1. In your Library, right click on Rainbow Six Vegas to access "Properties..."
2. Select "Controller" (General, Updates, Local Files, Language, -> Controller)
3. From the dropdown, select "Disable Steam Input"

Game worked like a dream after that (all controls were perfectly binded from the get-go)
SILEN1172236 9 Jul, 2020 @ 12:15am 
soy tu fan jajaja muchas gracias
markzwaan  [author] 17 Sep, 2019 @ 4:12am 
@ijonesflow: Glad to hear that it's working for you, enjoy the game!
ijonesflow 16 Sep, 2019 @ 10:16pm 
man thanks so much!!!
mehmetalper360 27 Nov, 2018 @ 12:46pm 
I tried everything you said.. but unfortunately it s not working on windows 10 x64... feel so sad..