test content
Logo
What is the Arc Client?
Install Arc
Keybinds not working
masterriftsgm01
Member Posts: 12 Arc User
I am not a user of custom keybinds, so this is not an issue wherein I created a keybind which screwed up my gameplay. For over a week now, the 1, 2, and 3 buttons (above qwerty, not numpad) will not work on ground missions. This is true on all nine of my characters.
Normally, I use the default keybinds which are:
1 = normal fire
2 = secondary fire
3 = rifle butt
I have attempted to use the options menu to correct this. I can change these functions to other keys, but I _cannot_ assign these functions to their default keybinds (as detailed above).
I have also attempted to simply reset everything to default...no change.
I am at my wit's end here, and rapidly losing interest in continuing to play this game after 3+ years of gameplay, promoting it among my fellow gamers, and throwing money at it. To add insult to injury, I have submitted a number of bug reports on this issue, and requested GM help umpteen times, and received zero assistance in this matter.
Normally, I use the default keybinds which are:
1 = normal fire
2 = secondary fire
3 = rifle butt
I have attempted to use the options menu to correct this. I can change these functions to other keys, but I _cannot_ assign these functions to their default keybinds (as detailed above).
I have also attempted to simply reset everything to default...no change.
I am at my wit's end here, and rapidly losing interest in continuing to play this game after 3+ years of gameplay, promoting it among my fellow gamers, and throwing money at it. To add insult to injury, I have submitted a number of bug reports on this issue, and requested GM help umpteen times, and received zero assistance in this matter.
[SIGPIC][/SIGPIC]
Post edited by masterriftsgm01 on
0
Comments
I know this will come off as sounding dumb and all but, could you have possibly hit the caps lock and/or num lock keys by accident?
Praetor of the -RTS- Romulan Tal Shiar fleet!
There is already a long ongoing issue with that system, and just want to make sure its not related.
Ruling that out (operator error) was the first thing I did. I used to be a technical trouble shooter for the military, so I always rule out the stupid stuff first (because that's usually the problem).
The problem exists whether I'm in shooter mode or using the default RPG keybinds.
The numpad keybinds work fine, but when I try to assign the defaults, they simply won't apply (the field remains black).
Are you sure, you didn't just Kill your 1,2,3 Keys?
This is the same across NINE different characters, as stated in the initial post. So this is entirely N/A.
Example:
3 = normal fire
1 = secondary fire
2 = rifle butt
But no matter freaking what, I cannot assign them as normal:
1 = normal fire
2 = secondary fire
3 = rifle butt
Woops, totally missed that, sorry.
A work around you could do until a Dev chimes in is assign them 3,2,1 and then move the powers on your hot bar to the reverse. If you can get them working that way it would at least let you play.
Yeah, I considered that and tried it out: no dice. Even when assigned out of their normal sequence, the keys will not work for these functions.
Ah, well that sucks. Have you tried setting keys 1,2, and 3 as secondary binds instead of primary? Like the list on the right.
/bind 1 "+STOTrayExecByTray 0 0"
/bind 2 "+STOTrayExecByTray 0 1"
/bind 3 "+STOTrayExecByTray 0 2"
If this doesn't work or the post above doesn't work, then I'm afraid I'm out of ideas.
Gave it a shot, and was REALLY hopeful...nope. It didn't work. I tell you, mate, I even opened up the plasma manifolds and poured all my FEELZ into the effort, and it still didn't work.
*sigh* And, of course, who knows how long it will take for this to get the attention of someone at Cryptic who could actually investigate the issue?
SHEER GENIUS IN ITS SIMPLICITY. Works like a charm. It's not a fix to the problem, but it's an effective workaround. Gracias, mi amigo.
Damn those un-feeling plasma manifolds eh!
I'm really glad that seems to work for you! Hopefully a Dev will take notice of this thread and investigate why you can assign them as secondary binds but not primary binds. At least you can play now.