Unvanquished Forum

Hello,

Here's my problem, I'm using an AZERTY keyboard on Kubuntu 14.10 with french translation and most of my binds are working except ones related to the i[/i], i[/i] and i[/i] keys in the image below. When I press them nothing happen and when I press them while chatting I got the following error messages in daemon.log:

^3Warning: ^7Rocket_FromQuake: Could not find keynum 34
^3Warning: ^7Rocket_FromQuake: Could not find keynum 40
^3Warning: ^7Rocket_FromQuake: Could not find keynum 95

and the letters don't print in the chat.

My binds in autoexec.cfg are:

[...]
teambind aliens & class level1
teambind aliens é class level1upg
teambind aliens " class level2
teambind aliens ' class level2upg
teambind aliens ( class level3
teambind aliens - class level3upg
teambind aliens è class level4
[...]
teambind humans & "sell weapons;buy +psaw;buy +rifle"
teambind humans é "sell weapons;buy +shotgun;buy +rifle"
teambind humans " "sell weapons;buy +lgun;buy +rifle"
teambind humans ' "sell weapons;buy +mdriver;buy +rifle"
teambind humans ( "sell weapons;buy +chaingun;buy +rifle"
teambind humans - "sell weapons;buy +flamer;buy +rifle"
teambind humans è "sell weapons;buy +prifle;buy +rifle"
teambind humans _ "sell weapons;buy +lcannon;buy +rifle"
[...]

Help me grangers!

Thank you in advance.

I can't test this right now, but it's possible you need to escape some or all of those with a \ before the character being bound like this:

teambind aliens \" class level2

I didn't check daemon.log but I had a similar problem with a bind on \ not working correctly before I escaped it by using \\ instead.

Yes, I confirm, non-ASCII characters don't work at all as bind key or in chat (but works in console, and if you activate debug, there is keypress debug message only for non-ASCII character while you are typing), this is broken since many months (year?).

It's just yet another issue I have in my TOREPORT list!

Thank you guys. Peace, I tried escaping the characters but it didn't worked unfortunately. Illwieckz, OK , do you want to report the issue or do you prefer me to do it?

Yes, since there is no keypress debug messages, I think it's not an autoexec.cfg issue, since Unvanquished seems to not know the key is pressed.

Perhaps the bug comes with the SDL2 port but I don't know exactly when. In the past Unvanquished was able to bind some strange keys (with a better support than tremulous and other idtech3 derivatives), but now it's worse.

I can write the bug report if you want, but if you create it I will comment it for sure.

Done!