![]() "n" is also the equivalent of "y" on your game pad for switching different activatable things and some menus stuff. Also right next to it is the "n"-key which causes dual wield(not sure if "q" is used in any way, now that I think of it). I bound "Interact" to the "b"-key because it doesn't interfere with the AutoHotkey-script and because I can reach it while having my fingers on WASD. ![]() I suggest going with the Default AHK, it takes a little getting used to but is generally quite nice. Read the whole damn thing, it's really informative, though a bit badly typeset maybe. Long story short I suggest looking at this: This is of course old news but I fixed my problem with vanilla DS2 so long ago that I forgot and Scholar of the First Sin reset all your settings including a crucial step in getting the Script to work.(meaning setting all your mouse settings in the DS2 ingame config to "nothing") I've checked with some people and throughly tested everything from refresh-rates, advanced tv settings/enhancement interferance to electric frequencies, resolutions, rendering and software. However the devs were kind enough to provide keyboard keys for the attack animations, which can be mapped to the mouse via AutoHotkey. As of right now, a majority of the Dark Souls II community are having some serious input lag with their M1 and M2 buttons even with their scrollers and the raw mouse input working flawlessly. ![]() The game waits for a double click input and only if there is none will it after a given time react to the single click which results in noticeable lag of course. The problem has got to do with the incredibly insane programming of the DS2 mouse controls. I'm sorry I fixed the problem some time ago, I will update my main post but also write here, so:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |