{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
10/24/2017 6:07:12 PM
13
Key Bindings
Trying to get my keys bound over to the numpad side (lefty here!) like I had them set during the beta, but it's not letting me do it now? Has that been removed? or still glitchy because it's day1?
-
This didn't work for me during the beta and after trying to restore defaults, somehow managed to assign multiple actions to the same key, at which point I just gave up. As it was a "Known Issue" I assumed this would get fixed in a Day 1 patch but somehow its actually worse at launch and I'm playing the game with a controller. I don't really understand how something so basic that works in every other title I have on PC does not work for a Triple A title. I hear the workarounds with various key-mapping software etc. but this is crazy when it should just work. Bungie please fix so I can play the game using my preferred control method.
-
It's absurd that we can't bind numpad keys in the game when this worked in beta. How the hell do you manage to break something as basic as keybinding... Been playing FPS games since they were invented, I'm not about to install a third party application just to use the part of the keyboard most left handed players use.
-
5 RepliesHeres how you work the numpad. Open Windows start menu and search for RUN. When RUN is up, type %appdata%. Find Appdata\Roaming\Bungie\DestinyPC\prefs\. In there you will see "cvars.xml". Open it with notepad. Find the keybindings section. It will look like "<cvar name="jump" value="unused!unused" />" Replace the first unused with keypad #. It will looks like this. <cvar name="jump" value="keypad 0!unused" />. Save it and run the game. Happy killing guys.
-
7 RepliesDownload AutoHotKey open-source scripting app at: https://autohotkey.com/ Once installed, right click on open desktop background, create script, and name it what you will keeping the .ahk extension. Edit the file by right-click>edit context. Bungie literally handed us the list of "approved" keys via their default key-mapping, so you can literally go 1:1 here and assign the key they want you to use as the output for the key you have gotten used to using in your X-years+ of gaming. If you make mistakes in the script and put the wrong Destiny2 default key as output to your chosen numpad key, the easiest fix is just to use the in-game remap function with whatever it spits out on keypress. This will work unless you put in another reserved/forbidden key, then you'll have to correct in your original *.ahk file, recompile, etc. I'm providing my script and control scheme if you are averse to typing and willing to use what I had via a quick remap session in game as described above for oopsies: #NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases. SendMode Input ; Recommended for new scripts due to its superior speed and reliability. SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory. Numpad8::w Numpad4::a Numpad6::d Numpad2::s Numpad0::space ;jump NumpadEnter::r ;reload Numpad5::g ;highlight player NumpadDot::z ;hold to crouch Numpad7::f ;super Numpad9::v ;class ability Numpad1::x ;air move Numpad3::Tab ;deploy ghost Right::RShift ;arrow block by thumb Up::1 ;kinetic default Down::2 ;energy default Left::3 ;power default ;Numpad/,*,-,+ All get recognized in game without issue so no need to script them here
-
Wouldn't recommend key binds, you'll probably get banned.
-
2 RepliesEdited by RedPhoenix HD: 10/24/2017 6:40:16 PMhttps://www.bungie.net/en/Forum/Post/236455208/0/0 Numpad binding will not work and was an issue even in Beta. They may not be planning to implement it.
-
Key mapping does not recognize Enter key (normal or numpad).
-
Same :( had to change to an awkward IJKL setup, but I'd really prefer to use the numpad and arrow keys like normal. Please fix ;-;
-
1 ReplyI am also having the same problem. I use a multi-button mouse and have many keys on the side of it that use the number pad, and I cannot bind them to anything, and I especially want to use one of them as my aim button.
-
FIXED: Used AutoHotKey with the following schema: Numpad8::w Numpad4::a Numpad6::d Numpad2::s Numpad0::space NumpadEnter::r Make sure to compile your script to generate an *.exe, fire it off before opening Destiny2, and if there are any conflicts with what you remapped in AHK, just use whatever AHK kicks out as a remap in-game through the provided Bungie shite interface. I got strange behavior from the keys using Bunny's cvar edit method.
-
1 ReplyEdited by iuki: 10/24/2017 7:39:56 PMSo in the beta I was able to use arrow keys and bind things to the num pad; it worked great. Now in launch arrow keys = numpad. Thus I cant use numpad for weapon and ability swaps + use arrow keys for movement since they are the same binds now. End result is I can't play the game like this, I have been using arrow keys to move in shooters/mmos for over 30 years so I can't use WASD! It's completely unplayable. Please put it back to what it was in beta so I can play again, thanks.
-
4 RepliesSame. This game is unplayable for me if this dsnt get fixed :/
-
Sharpkeys saved the Day..... And therefor i payed 50 Bugs...
