Bind lost in ET 2.55 to 2.60 transition

(rdd) #1

Hello.

It seems I’ve lost a bind in the transition from ET 2.55 to 2.60. The key in question is my Ö-key (swedish keyboard). On Windows I get a us keymap (at least in quake3…), but since I started using Linux (Gentoo, latest 2.6 kernel) I still have my swedish keymap in quake3 based games. So since Ö obviously isn’t printable in ET I’m using its hexvalue to bind it (“bind 0xf6 +movedown”).
Since I noticed it missing I tried reinstalling version 2.55 to see if it works there and it does (also works in quake3).
Other unprintable keys also doesn’t work to bind using their hex value though I’m not fully sure I ever had those bound in earlier versions either.
Printable keys are accessible through their hex value (using 0x61 to bind A for example) but there’s no real reason for that… :slight_smile:

Is this a (known) bug in 2.60? Anyone know of anything I could do to bind my Ö-key?

(Lekdevil.NL) #2

I might be stating the obvious, but have you tried assigning the key through the graphical interface (Options->Controls->Crouch)?

(rdd) #3

Actually I had not, tried it now though.
In 2.55 it work just fine, but in 2.60 it shows crouch already bound to 0xf6, but when I click it with mouse and then press my Ö-key nothing happens. Seems like it doesn’t recognize the key at all anymore. :frowning:

(Sauron|EFG) #4

It’s not in the 2.60 readme, but it looks like ET now uses DirectInput in Windows. Which DirectX version do you have?

Pressing ‘ö’ in the ingame menu shows ‘;’ for me in 2.60, which is the corresponding key on US keyboards. You could try “bind ; +movedown”.

(rdd) #5

Like I said, in Windows I had a US keyboard map as well, and I used to have “bind semicolon +movedown” in my config. But since switching to Linux I find that I still have my regular SE keymap in quake3 based games. So semicolon for example would be accessible as usual through “shift+,” and the ö key shows nothing when I press it, but until 2.60 I could still bind it using its hexvalue.

(Sauron|EFG) #6

Whoops, should have read it more carefully. Sorry!