🛈 Announcement
Greetings! The For Honor forums are now archived and accessible in read-only mode, please go to the new platform to discuss the game
  1. #11
    Hi CritBull, the guide is located in the file legacygamepads.ini in folder where you have For Honor installed. For example C:\Games\ForHonorBETA\legacygamepads.ini.

    It is just a text file so you can open it in your notepad, long text file. For example, if you will look to the end of the file, there is something like:
    [02E0045E-0000-0000-0000-504944564944]
    PROFILE=XBOX BLUETOOTH
    ...the first row in [ ] brackets is UID of your controller. In the file you can find how to achieve UID of your gamepad. Search for (CTRL+F) "The Device UID section"
    the second row stands for name of profile.

    If you will look a little bit up of theese last text lines in the file, you will see something like this:
    [XBOX BLUETOOTH]
    BTN_A=DI_BTN_1
    BTN_B=DI_BTN_2
    BTN_BACK=DI_BTN_7
    BTN_LBUMP=DI_BTN_5
    BTN_LSTICK=DI_BTN_9
    BTN_LTRIGGER=DI_AXIS_TZ,POSITIVE
    BTN_RBUMP=DI_BTN_6
    BTN_RSTICK=DI_BTN_10
    BTN_RTRIGGER=DI_AXIS_RZ,POSITIVE
    BTN_START=DI_BTN_8
    BTN_X=DI_BTN_3
    BTN_Y=DI_BTN_4
    DEVTYPE=XBOX360GAMEPAD
    DPAD_DOWN=DI_POV_0_DOWN
    DPAD_LEFT=DI_POV_0_LEFT
    DPAD_RIGHT=DI_POV_0_RIGHT
    DPAD_UP=DI_POV_0_UP
    NAMEPATTERN=
    THUMB_LX=DI_AXIS_TX
    THUMB_LY=DI_AXIS_TY
    THUMB_RX=DI_AXIS_RX
    THUMB_RY=DI_AXIS_RY
    ...as you may see, in [ ] brackets there is exactly the name of the "PROFILE=XBOX BLUETOOTH" and below this are some mapping lines what will happen if you press something. There is also an information how to know what the controller buttons names are (again through dxdiag), you may read about it at the end of "The mapping section" section. Also, you have stated actions what game knows in this section. So you will know, that if for example a game knows command "button_x" providing guard block for example and a button on the controller will return you "button_365" then you will just connect theese two things together via button_x=button_365 (names of theese are just example).

    Everything is in the file, just notice that every line of text beginning on "#" is a comment - will not be evaluated by the game.

    Before you do anything, backup your original file because if you will miss something, it may cause errors.

    Anyway, since it is guided in their official file, if you do everything propperly like it is described, I believe it can help you without any errors (because they know how their game take inputs so their guide would be excellent). Just for all cases - backup your original legacygamepads.ini if any error will occur. Then you may also (before restoring the original file) search for possible mistakes in spelling for example.

    Wish you best luck & hope it helps you with the controller! I have to say that I was not able to test this, because 1) I found the file when I was searching for keyboard mapping config (unsuccesfully ) and I found it when I had no time to test it in game because of closed beta ended soon, and 2) I have just an ordinary xbox controller so it was mapped automatically and since this file is named "legacy gamepads" I think I would not be able to override my compatible gamepad settings with this. But I may try once open beta will come. I also want to try it with TrackIR if it will do something and also for example on a wheel or joystick or HOTAS Hope I will have enough time to do that. May be funny
    Share this post

  2. #12
    Originally Posted by emoKittenCZ Go to original post
    Hi CritBull, the guide is located in the file legacygamepads.ini in folder where you have For Honor installed. For example C:\Games\ForHonorBETA\legacygamepads.ini.

    It is just a text file so you can open it in your notepad, long text file. For example, if you will look to the end of the file, there is something like:
    [02E0045E-0000-0000-0000-504944564944]
    PROFILE=XBOX BLUETOOTH
    ...the first row in [ ] brackets is UID of your controller. In the file you can find how to achieve UID of your gamepad. Search for (CTRL+F) "The Device UID section"
    the second row stands for name of profile.

    If you will look a little bit up of theese last text lines in the file, you will see something like this:
    [XBOX BLUETOOTH]
    BTN_A=DI_BTN_1
    BTN_B=DI_BTN_2
    BTN_BACK=DI_BTN_7
    BTN_LBUMP=DI_BTN_5
    BTN_LSTICK=DI_BTN_9
    BTN_LTRIGGER=DI_AXIS_TZ,POSITIVE
    BTN_RBUMP=DI_BTN_6
    BTN_RSTICK=DI_BTN_10
    BTN_RTRIGGER=DI_AXIS_RZ,POSITIVE
    BTN_START=DI_BTN_8
    BTN_X=DI_BTN_3
    BTN_Y=DI_BTN_4
    DEVTYPE=XBOX360GAMEPAD
    DPAD_DOWN=DI_POV_0_DOWN
    DPAD_LEFT=DI_POV_0_LEFT
    DPAD_RIGHT=DI_POV_0_RIGHT
    DPAD_UP=DI_POV_0_UP
    NAMEPATTERN=
    THUMB_LX=DI_AXIS_TX
    THUMB_LY=DI_AXIS_TY
    THUMB_RX=DI_AXIS_RX
    THUMB_RY=DI_AXIS_RY
    ...as you may see, in [ ] brackets there is exactly the name of the "PROFILE=XBOX BLUETOOTH" and below this are some mapping lines what will happen if you press something. There is also an information how to know what the controller buttons names are (again through dxdiag), you may read about it at the end of "The mapping section" section. Also, you have stated actions what game knows in this section. So you will know, that if for example a game knows command "button_x" providing guard block for example and a button on the controller will return you "button_365" then you will just connect theese two things together via button_x=button_365 (names of theese are just example).

    Everything is in the file, just notice that every line of text beginning on "#" is a comment - will not be evaluated by the game.

    Before you do anything, backup your original file because if you will miss something, it may cause errors.

    Anyway, since it is guided in their official file, if you do everything propperly like it is described, I believe it can help you without any errors (because they know how their game take inputs so their guide would be excellent). Just for all cases - backup your original legacygamepads.ini if any error will occur. Then you may also (before restoring the original file) search for possible mistakes in spelling for example.

    Wish you best luck & hope it helps you with the controller! I have to say that I was not able to test this, because 1) I found the file when I was searching for keyboard mapping config (unsuccesfully ) and I found it when I had no time to test it in game because of closed beta ended soon, and 2) I have just an ordinary xbox controller so it was mapped automatically and since this file is named "legacy gamepads" I think I would not be able to override my compatible gamepad settings with this. But I may try once open beta will come. I also want to try it with TrackIR if it will do something and also for example on a wheel or joystick or HOTAS Hope I will have enough time to do that. May be funny
    WOW thats awsome Kitten! I may have a little play around with it in the Open Beta thanks for all the explanation too will be very helpful for a noob like me
    Share this post

  3. #13
    You are welcome man. Hope it will help you.

    Just notice the "# If you need to add or modify a legacy controller, please add it to your legacygamepads_user.ini file which is located in "Documents\My Games\For Honor"." sentence in beginning of the guide and you should be OK.

    It is coming soon so you may prepare your file even now via your controller device settings for the correct mapping. In those drivers if you press some button on your controller, its number will shine. For example if you press the bottom one button (out of those 4) and if for example number two will shine, then just make connection BTN_A=DI_BTN_2 etc. If you will need to invert an axis, just make a connection like THUMB_RY=DI_AXIS_TZ,INVERT (note the INVERT). Their guide is pretty excellent there and I believe you will pass it if you will play with that a bit With some patience, maybe you would be able to map even your joystick or a wheel to that...lets try it in the open beta? Actually if they really support up to 4 D-pads, I may try it even with my X-55 with guard on some of those hats the camera control would suck but hey...its for fun, isnt it?

    Also I finally found the key bindings config. I am happy that the config is prepared for primary and secondary keys so I believe it will be in the game also, maybe in this open beta already, but I am also sad that I doubt there will be an option to have three or four keys bound to a single action according to the way they use for binding. Anyway I may try -.-
    This is where the other games like Call of Duty and Counter Strike shines. Meanwhile in CoD you have in your config for example:
    bind MOUSE1 +attack
    bind C +attack
    bind M +attack
    bind MWHEELUP +attack
    ...and so on...
    then the game would just gen an input key pressed and do the action listed...that mean, no matter if you would press left mouse button, C key, M key or scroll mouse wheel up, you will just shoot. No matter how much keys you have listed to a single action, each of it will do that. Here it is kind of different approach...
    Gameplay.GuardBreak=E
    Gameplay.GuardBreak.Secondary=
    ...I am worried that there is no .Tertiary, .Quarternary etc. at least the .Secondary may help a lot... But I would like to see more something like "bind E Gameplay.GuardBreak" for an infinite options
    Share this post

  4. #14
    Jan_GG's Avatar Junior Member
    Join Date
    Dec 2015
    Posts
    26
    emoKittenCZ, do you by any chance know if the legacygamepads.ini method allows binding the central silver 'Guide' button on an XBox controller (I believe it's internally referred as button 13)?

    Guess I'll find out myself in 2 days, but that's one of the things I'm trying to figure out.
    Share this post

  5. #15
    Originally Posted by emoKittenCZ Go to original post
    You are welcome man. Hope it will help you.

    Just notice the "# If you need to add or modify a legacy controller, please add it to your legacygamepads_user.ini file which is located in "Documents\My Games\For Honor"." sentence in beginning of the guide and you should be OK.

    It is coming soon so you may prepare your file even now via your controller device settings for the correct mapping. In those drivers if you press some button on your controller, its number will shine. For example if you press the bottom one button (out of those 4) and if for example number two will shine, then just make connection BTN_A=DI_BTN_2 etc. If you will need to invert an axis, just make a connection like THUMB_RY=DI_AXIS_TZ,INVERT (note the INVERT). Their guide is pretty excellent there and I believe you will pass it if you will play with that a bit With some patience, maybe you would be able to map even your joystick or a wheel to that...lets try it in the open beta? Actually if they really support up to 4 D-pads, I may try it even with my X-55 with guard on some of those hats the camera control would suck but hey...its for fun, isnt it?

    Also I finally found the key bindings config. I am happy that the config is prepared for primary and secondary keys so I believe it will be in the game also, maybe in this open beta already, but I am also sad that I doubt there will be an option to have three or four keys bound to a single action according to the way they use for binding. Anyway I may try -.-
    This is where the other games like Call of Duty and Counter Strike shines. Meanwhile in CoD you have in your config for example:
    bind MOUSE1 +attack
    bind C +attack
    bind M +attack
    bind MWHEELUP +attack
    ...and so on...
    then the game would just gen an input key pressed and do the action listed...that mean, no matter if you would press left mouse button, C key, M key or scroll mouse wheel up, you will just shoot. No matter how much keys you have listed to a single action, each of it will do that. Here it is kind of different approach...
    Gameplay.GuardBreak=E
    Gameplay.GuardBreak.Secondary=
    ...I am worried that there is no .Tertiary, .Quarternary etc. at least the .Secondary may help a lot... But I would like to see more something like "bind E Gameplay.GuardBreak" for an infinite options
    Kitten... Great this is all very useful! Maybe between you and Jan we can work out how effective this is? Just want to thank you again soo much! Please report back and let us know how you did with all your testing. If we can help out at all let us know. As for me to be honest I am a big noob at this stuff but learning alot just by talking to you guys.
    Share this post

  6. #16
    Originally Posted by Jan_GG Go to original post
    emoKittenCZ, do you by any chance know if the legacygamepads.ini method allows binding the central silver 'Guide' button on an XBox controller (I believe it's internally referred as button 13)?

    Guess I'll find out myself in 2 days, but that's one of the things I'm trying to figure out.
    Hello Jan, I am worried I will not have positive answer for you.

    I have only Xbox 360 controller, not Xbox One. In my settings I have 10 buttons (A, B, X, Y, RB, LB, back, start, LS and RS). The middle X button is then not mappable (if thats the correct word). I have read that new standards for Xbox One and PS4 does not use this logo/central button as a normal button either, so I am worried that this will not be a 13th button.

    Anyway, you may try to connect your controller, go to your devices & printers, go to your controller settings and try to push it, if any of buttons will flash. If so, then I believe you can bind this button to something like for example BTN_LBUMP=DI_BTN_13. Anyway, even if it will not flash, then you may try to bind any DI_BTN_13 up to DI_BTN_20 if it will work. To be honest, if the button will not flash in your device settings, I am worried it will not work.

    Even if it would work, I am worried, that you cannot have one action bound on a single controller button, so you would just remap the action. But if it is ok, then why dont try it Good luck.

    Also I think that remaping (as a lot of ppl just said, that it is not comfortable to have guard break on X button) BTN_X=DI_BTN_5 (or whatever your LB is) and vice versa BTN_LBUMP=DI_BTN_3 (or whatever your guard break button is) can solve a problem. I played only for a while with my controller, so I dont remember what is mapped to left bump button so dont hate me if there were something important bound to left bump button before

    Since my controller is xbox 360 it is naturally compatible with the game. Anyway I may try if some remapping will work like to have guard break on LB. I will try to edit it in legacygamepads_user.ini in documents/my games/for honor folder and see if it will actually override the legacygamepads.ini file, as my controller is profiled there:
    [02A1045E-0000-0000-0000-504944564944]
    PROFILE=XBOX 360 COMPATIBLE
    And if it will not work, I may try to edit it in legacygamepads.ini file, but note their warning of possible patch can reset the file changes. Then I may also try erasing it from legacigamepads and copying it only to legacygamepads_user. But I hope and believe that devs thought about it and legacygamepads_user would override the original legacygamepads, because if it would not, then it is pointless to edit legacygamepads_user and you may need to make the changes again and again after some patches updating the legacygamepads file.

    Originally Posted by CritBull Go to original post
    Kitten... Great this is all very useful! Maybe between you and Jan we can work out how effective this is? Just want to thank you again soo much! Please report back and let us know how you did with all your testing. If we can help out at all let us know. As for me to be honest I am a big noob at this stuff but learning alot just by talking to you guys.
    You are welcome I am glad to try to help even if we need to try that after they run open beta live Hope it will work and you will be able to play with your controller. I am more of a keyboard + mouse oriented but I am not a "racist" on controllers just because I am not skilled enough using it especially for the camera I hate using the stick to rotate my view

    I will let you know about my tests (if I will have time to test it), but I am not sure if we will be able to use this thread as I heard, they will possibli wipe the Closed Beta forum and now this cathegory is already hidden from the main for honor forum menu.

    I am looking forward to see your possible success with your controller, please let me know, thank you
    Share this post

  7. #17
    Jan_GG's Avatar Junior Member
    Join Date
    Dec 2015
    Posts
    26
    This thread is in an old subforum but whatever.

    The quick update is that I can't do anything with the X360 controller. No method allows any rebinding, seems like it's somehow hard-coded in the game. The legacygamepad.ini works only for controllers normally not supported by FH, Xinput is ignored and things like Joy2Key make the game see 2 inputs (rebinded and default) at the same time.

    Talk about frustration.
    Share this post

  8. #18

    I can confirm that.

    Sadly even if you erase X360 from the file, it has still those default settings. That is really great fail.
    I tried to controll FH on my Thrustmaster wheel and X55 HOTAS and everything was OK but the X360 controller...ahm really disappointed. This is kind of elementary school coding from a 4 years old girl, not AAA coding.

    Still hope there will be binding settings for controllers in the game especially default controllers. And still hope for being able to use more than two keys bound to a single action.
    Share this post

  9. #19
    Jan_GG's Avatar Junior Member
    Join Date
    Dec 2015
    Posts
    26
    Hallelujah, Deus Vult, To Valhalla and Konichiwa!

    I have found out a way to configure a X360 controller. The problem was it uses Xinput by default and legacygamepads.ini is used for Directinput controllers. So I had to disable Xinput. I did it by putting /noxinput in Game launch arguments (Uplay->Games->For Honor->Properties->Game Launch Arguments).

    Excuse me while I go wreck some noobs with my superior LB-Guard Break technique.
    Share this post

  10. #20
    Good job and good luck with your guard breaking man

    Well...if you want to play with controller, how much research is need to be done to be able to get something what is just a basic option in other games... :/ If you want to change XInput, EAC will not allow you to do so, If you want to bind it like any other DI device (because it simply is just another DI device) then XInput looks like to override that settings..

    Really, if it will not be part of the live game, someone in dev team pretty failed his job.
    Share this post