GUYS a great FIX is here found this on steam and it works !!! regards
Deano’s Unofficial 360 pad config for PC
Whilst I’m Lead programmer for Brink, I’m also a disabled gamer and so was very annoyed at myself when the reports came out that the 360 pad wasn’t supported in Brink
However with a little digging I’m glad to say it is working just buried a bit. I apologise for taking a few days to get this information together.
Officially PC Brink using a controller is UNSUPPORTED however I think you should find this works okay for 360 pad users. One important thing to note, is that PC Brink does NOT have aim assistance on mouse or controller. So the extra help you get on consoles using a controller, doesn’t exist here!
However seeing videos of the talents of some disabled gamers, I don’t think that will be a problem
Enable controllers
Controllers are disabled by default, to enable them bring down the command console and type
g_EnablePCControllerInput 1
or add it to your command line when running Brink via
+set g_EnablePCControllerInput 1
If you enabled it in the console, you will likely have to restart Brink before it detects your controllers.
Once enabled you should see in your console.log a report of what controllers Brink has detected (commonly it will be a 360 controller in port 0/1).
A bind config for pads
Once you have enabled controllers you will find that the analog sticks will now control the player same as the mouse does. However no buttons and triggers will work yet. For this we have to run a bind config which maps what button does what.
Create a text file called unsupported360pad.cfg and cut and paste from the code block below into it. This file should be placed in you ‘base’ folder which should be located where your brink.exe is.
Bring down the command console and type (if its in the right place, it will tab complete the full config file name)
exec unsupported360pad.cfg
This will enable a set of binding similar to the default configuration on XBOX 360. It will also leave the mouse and keyboard binding intact, so you can use either M/KB or Controller at any time.
Hopefully the config file makes some sense if you wish to have a different button configuration, however if not if you PM me I’ll try to help move some buttons around, to get us all gaming the way we want
Known Issues
Onscreen key reminders:
The onscreen button reminders will still be for KB/M, so for example it will inform you that keyboard X is for self buffing. This may make it harder to remember which controller button does what I’m afraid but hopefully that won’t be too much of a problem, as there is no solution currently.
unsupported360pad.cfg
Code:
bind “JOY1_1” “_moveup” // A
bind “JOY1_2” “_movedown” // B
bind “JOY1_3” “_consoleContext1” // X
bind “JOY1_4” “_consoleContext2” // Y
bind “JOY1_5” “_sprint” // Left bumper
bind “JOY1_6” “_useGrenade” // Right bumper
bind “JOY1_7” “_selfInteract” // Left stick press
bind “JOY1_8” “_meleeAttack” // Right stick press
bind “JOY1_9” “_limbomenu” “” “default” // Start: Limbo Menu
bind “JOY1_10” “_limbomenushortcut” // Back
bind “JOY1_LEFT_TRIGGER” “_altattack”
bind “JOY1_RIGHT_TRIGGER” “_attack”
bind “JOY1_DPAD_LEFT” “_activateContext1”
bind “JOY1_DPAD_RIGHT” “_activateContext2”
bind “JOY1_DPAD_UP” “_consoleContext3”
bind “JOY1_DPAD_DOWN” “_activateContext3”
bind “JOY1_DPAD_LEFT” “_peekLeft” “JOY1_LEFT_TRIGGER”
bind “JOY1_DPAD_RIGHT” “_peekRight” “JOY1_LEFT_TRIGGER”
bind “JOY1_DPAD_UP” “_peekPopUp” “JOY1_LEFT_TRIGGER”
bind “JOY1_DPAD_DOWN” “_peekHide” “JOY1_LEFT_TRIGGER”
// Menus
bind “JOY1_1” “_menuClick” “” “menu”
bind “JOY1_1” “_menuAccept” “” “menu”
bind “JOY1_2” “_menuCancel” “” “menu”
bind “JOY1_3” “_menuContext” “” “menu”
bind “JOY1_3” “_menuEvent1” “” “menu”
bind “JOY1_4” “_menuEvent2” “” “menu”
bind “JOY1_9” “_menuEvent6” “” “menu”
bind “JOY1_10” “_limbomenushortcut” “” “menu”
bind “JOY1_RIGHT_TRIGGER” “_menuClick” “” “menu”
bind “JOY1_6” “_menuEvent3” “” “menu” // Left bumper
bind “JOY1_5” “_menuEvent4” “” “menu” // Right bumper
bind “JOY1_DPAD_UP” “_menuNavCategoryUp” “” “menu”
bind “JOY1_DPAD_LEFT” “_menuNavBackward” “” “menu”
bind “JOY1_DPAD_DOWN” “_menuNavCategoryDown” “” “menu”
bind “JOY1_DPAD_RIGHT” “_menuNavForward” “” “menu”
// Limbo/Ingame Menus
bind “JOY1_1” “_menuClick” “” “menu_limbo”
bind “JOY1_1” “_menuAccept” “” “menu_limbo”
bind “JOY1_2” “_menuCancel” “” “menu_limbo”
bind “JOY1_3” “_menuContext” “” “menu_limbo”
bind “JOY1_3” “_menuEvent1” “” “menu_limbo”
bind “JOY1_4” “_menuEvent2” “” “menu_limbo”
bind “JOY1_9” “_limboMenu” “” “menu_limbo”//start button
bind “JOY1_10” “_limbomenushortcut” “” “menu_limbo”
bind “JOY1_RIGHT_TRIGGER” “_menuClick” “” “menu_limbo”
bind “JOY1_6” “_menuEvent3” “” “menu_limbo” // Left bumper
bind “JOY1_5” “_menuEvent4” “” “menu_limbo” // Right bumper
bind “JOY1_DPAD_UP” “_menuNavCategoryUp” “” “menu_limbo”
bind “JOY1_DPAD_LEFT” “_menuNavBackward” “” “menu_limbo”
bind “JOY1_DPAD_DOWN” “_menuNavCategoryDown” “” “menu_limbo”
bind “JOY1_DPAD_RIGHT” “_menuNavForward” “” “menu_limbo”
// Bind Menus
bind “JOY1_1” “_menuClick” “” “bindmenu”
bind “JOY1_1” “_menuAccept” “” “bindmenu”
bind “JOY1_2” “_menuCancel” “” “bindmenu”
bind “JOY1_3” “_menuContext” “” “bindmenu”
bind “JOY1_3” “_menuEvent1” “” “bindmenu”
bind “JOY1_4” “_menuEvent2” “” “bindmenu”
bind “JOY1_9” “_limbomenu” “” “bindmenu”
bind “JOY1_10” “_limbomenushortcut” “” “bindmenu”
bind “JOY1_RIGHT_TRIGGER” “_menuClick” “” “bindmenu”
// Radial Menus
bind “JOY1_1” “_menuClick” “” “radialmenu”
bind “JOY1_1” “_menuAccept” “” “radialmenu”
bind “JOY1_2” “_menuCancel” “” “radialmenu”
bind “JOY1_RIGHT_TRIGGER” “_menuClick” “” “radialmenu”
bind “JOY1_2” “_menuContext” “” “radialmenu”
Last edited by DeanoC: Today at 09:36 AM. Reason: typo
