arrow keys not working on latest release
kax888 opened this issue · 9 comments
on default configs, Arrows does not work with at least Hollow Knight, haven't tried other games.
i rebound my in game directions to WASD and then put SOCD on WASD and it worked, binding in game to arrows and selecting Arrows does not work.
I downloaded the previous version, and Arrows work as intended on that version.
I personally dont care that i have to use a slightly older version, but figured you would probably like to know that's a problem with the latest build.
Hey thanks for letting me know! I'll be able to check it in a week or so
I I'm finally back home and checked arrows on latest release. At least in Hollow Knight they work for me. Could you please provide more info about your setup? Show generated config when selecting arrows. The config is called socd_v008.conf for the current version
i'm not the person who opened this initially but i've been having the exact same issue. my config when selecting arrows is:
25
27
26
28
45
0
i'm also using a razer keyboard with razer synapse 3 as drivers if that matters.
I had another similar report on discord, and the person has windows 11. Do any of you who has arrows not working try it on use it on win11 by any chance? And another, maybe silly question - do you have a desktop with a separate keyboard or laptop? If laptop - what model?
Just dropping here setups that people have told me they have for whom v008 with scancodes doesn't work with arrow keys:
- windows 11 on IdeaPad Gaming 3 15ARH05
- windows 10 on asus rog gl502vs
Maybe I'll have to support both scancodes and old mode of simulating key presses
i'm on windows 10 with a separate keyboard although i could also try it on my laptop. exact specs for my desktop are an rog strix z370-f gaming motherboard, an i3-8100 cpu, and a gtx 1060 6gb gpu (and a 144hz 1080p monitor).
I have the same issue, it seems to me like the problem is that the program tries to press the left/right buttons on the numpad, which only works with NumLock off. When NumLock is on, it writes 4's and 6's instead of changing the direction.
Specifically for games that accept virtual key codes, not translating to scancodes solves this issue, see my fork as a temporary fix until a better solution is implemented. Alternatively, a release earlier than 0.0.8 can be used, but those don't have the ESC functionality.
Specifically for games that accept virtual key codes, not translating to scancodes solves this issue, see my fork as a temporary fix until a better solution is implemented. Alternatively, a release earlier than 0.0.8 can be used, but those don't have the ESC functionality.
Thank you so much for this fork! saved me!
Ugh yeah thanks for that. It seems like the fucked numpad state depends on the default firmware behavior of a particular keyboard. I recently bought a new keyboard and now I can repro the issue with scancodes myself. I'll fix it in the new version of the program I'm writing, meanwhile either use @TheRealAlph4's fork or my previous version from releases tab (it was doing virtual keycodes). I've changed it because some games don't listen to virtual codes (source games, for example), but yeah. Keyboard firmwares suck :(