Team Fortress 2
"[INSERT KEY] isn't a valid key"?
Has anyone else encountered this issue where a keybind you've used for a long time all of a sudden undoes itself and when you got through all the necessary steps to rebind it (autoexec, you config file, in-game console, etc), it keeps coming up with the error "[KEY] isn't a valid key" (if you replace KEY with the key that is not recognised)?

In my case, it's the hash sign (#) bound to the inspect function that isn't recognised in game. I first noticed after I compared how the username of a friend (which uses the #) was displayed in the steam overlay and in the game's text. I've checked all over online thinking it might perhaps be an error on my end, but considering how the # has disappeared from all aspects of the game...

So anyone out there have any ideas?
Last edited by ShaunOfTheN00bs; Jun 1, 2016 @ 10:34am
< >
Showing 1-13 of 13 comments
skip Jun 1, 2016 @ 10:54am 
I'm assuming you're using a QWERTY keyboard, yes?

And you're trying to bind to the hash (#) key?

So SHIFT + 3?

I'm kind of confused as in what key you're trying to bind to.
Colonel Cosmetic Jun 1, 2016 @ 11:46am 
Originally posted by skippy | <3:
I'm assuming you're using a QWERTY keyboard, yes?

And you're trying to bind to the hash (#) key?

So SHIFT + 3?

I'm kind of confused as in what key you're trying to bind to.
shift + 3 is £ not #
skip Jun 1, 2016 @ 12:39pm 
Originally posted by Colonel Cosmetic:
Originally posted by skippy | <3:
I'm assuming you're using a QWERTY keyboard, yes?

And you're trying to bind to the hash (#) key?

So SHIFT + 3?

I'm kind of confused as in what key you're trying to bind to.
shift + 3 is £ not #

Different keyboard layouts for different countries.

I live in NA, you live in Europe so the keyboard layouts for some keys are changed slightly.
Last edited by skip; Jun 1, 2016 @ 12:41pm
Colonel Cosmetic Jun 1, 2016 @ 1:05pm 
Originally posted by skippy | <3:
Originally posted by Colonel Cosmetic:
shift + 3 is £ not #

Different keyboard layouts for different countries.

I live in NA, you live in Europe so the keyboard layouts for some keys are changed slightly.
well that's pointless, why not just have a universal keyboard for each alphabet
ShaunOfTheN00bs Jun 1, 2016 @ 1:42pm 
Well regardless of regional variations to the QWERTY keyboard, for the record the key I am trying to bind is directly to the left of the return key, directly to the rightt of the apostrophe key (') and above the right shift key.
For further elaboration, when I try binding keys through the option menu, it replaces the # with a '; and when I try to bind it through the console, it comes up with the error message '"#" isn't a valid key'.
skip Jun 1, 2016 @ 2:41pm 
Originally posted by Colonel Cosmetic:
Originally posted by skippy | <3:

Different keyboard layouts for different countries.

I live in NA, you live in Europe so the keyboard layouts for some keys are changed slightly.
well that's pointless, why not just have a universal keyboard for each alphabet

Don't ask me, I'm not a keyboard manufacturer.
skip Jun 1, 2016 @ 2:50pm 
Originally posted by ShaunOfTheN00bs:
Well regardless of regional variations to the QWERTY keyboard, for the record the key I am trying to bind is directly to the left of the return key, directly to the rightt of the apostrophe key (') and above the right shift key.
For further elaboration, when I try binding keys through the option menu, it replaces the # with a '; and when I try to bind it through the console, it comes up with the error message '"#" isn't a valid key'.

So when you bind the key through the options menu, it gives you the binding of this character:

'

Try rebinding that exact key through options again, then type this into console:

key_listboundkeys

It should show you the key it's bound to.
Pakaku Jun 1, 2016 @ 2:51pm 
Originally posted by ShaunOfTheN00bs:
Well regardless of regional variations to the QWERTY keyboard, for the record the key I am trying to bind is directly to the left of the return key, directly to the rightt of the apostrophe key (') and above the right shift key.
For further elaboration, when I try binding keys through the option menu, it replaces the # with a '; and when I try to bind it through the console, it comes up with the error message '"#" isn't a valid key'.
Then use ' for the bind and see what happens.
ShaunOfTheN00bs Jun 1, 2016 @ 3:47pm 
Originally posted by Pakaku:
Then use ' for the bind and see what happens.
I already have that key bound to something else.
Last edited by ShaunOfTheN00bs; Jun 1, 2016 @ 3:47pm
ShaunOfTheN00bs Jun 1, 2016 @ 3:51pm 
Originally posted by skippy | <3:
So when you bind the key through the options menu, it gives you the binding of this character:

'

Try rebinding that exact key through options again, then type this into console:

key_listboundkeys

It should show you the key it's bound to.
Still showing that it's bound to the ' . I'm starting to think this is a bug.
Last edited by ShaunOfTheN00bs; Jun 1, 2016 @ 3:52pm
skip Jun 1, 2016 @ 4:12pm 
Is both the hash sign (#) and the apostrophe ( ' ) printed on the same key?
ShaunOfTheN00bs Jun 1, 2016 @ 5:17pm 
Originally posted by skippy | <3:
Is both the hash sign (#) and the apostrophe ( ' ) printed on the same key?
Nope, they're on seperate keys next to one another.
SaltDough Apr 28, 2024 @ 3:50am 
I typed in bind - kill just like that and it works now
< >
Showing 1-13 of 13 comments
Per page: 1530 50

Date Posted: Jun 1, 2016 @ 10:33am
Posts: 13