Emulator

Additional Info: Pressing = key fails to map correctly.

I'm not sure what the problem is here. I regularly use [, ], , and = as C button
keymappings (I have a laptop), and I never have issues. Even before my patch, I
didn't have any problems, IIRC. Maybe you need to update DirectX or something? Also,
Esc didn't clear the keymapping until yesterday... are you using source modifications
or one of those unofficial builds?

Also, you didn't mention the OS. Could have something to do with that as well.

Then it's totally weird. PadSimple can't read these three keys...

I already have the latest version of DirectX, DirectX 10, and there's no new stuffs
being added. I've checked the web setup for it, nothing new.

OS: Windows Vista Home Premium, 32-bit
Model: Acer Aspire 5720-4126

Might have something to do with the keyboard model...

Also, Esc didn't clear the keymapping until yesterday... are you using source
modifications or one of those unofficial builds?

I used r4525, as mentioned above.

Additional info:

= [ \ '

Those four keys above, they get inputted incorrectly in Dolphin.

= doesn't exist.
\ is ].
] is [.
[ doesn't exist.
' doesn't exist.
` doesn't exist.
Alt Gr doesn't exist.
Pause Break doesn't exist.
PrtSc SysRq doesn't exist.

what keyboard maps/languages do the people with the problem have?

English. Keyboard: QWERTY version.

Don't understand your question clearly, sir.

AltGr, Pause/Break, and PrintScreen don't work for me either--but I wouldn't expect
them to. But, it seems to me, the right-hand side alt/ctrl won't map at all
(including both US-International altGr and English/US right-alt).

So do you actually have an altGr key or is it simply mapped to right alt? (The
standard US keyboard layout has no altGr key.)

If you have any other PC games, try mapping =[]'` there and see if they work. If
not, this has something to do with your computer in particular.

I'm using a laptop. It's bought in USA, so it should be a US integrated keyboard with
Alt Gr.

I mapped those keys in CS 1.6, and they seemed to work pretty well. So, no, it's not
my laptop in particular.

Gonna take a look at that! =)

I can't reproduce that on r4735 ...
Does anyone still have this issue on r4735 ?

Why is it fixed? Is it, truly, just me and my recently new laptop's fault?

:(

I believe it has to do with the layout of the keyboard.

Here's a picture of it: http://img695.imageshack.us/img695/8549/54634944.jpg

@tom.mai78101: That's actually exactly the same as my laptop's layout, which I just
tested... Tell me something: what's the configured keyboard layout and language on your
OS?

Also, are you using r4735 ?

Ugh...didn't see that rev. Will check.

Configured Keyboard Layout:

http://img9.imageshack.us/img9/5139/75491764.jpg

I can't seem to set up any customized keyboard layout, so it's basically nothing but
the QWERTY layout.

In the picture of the keyboard, I should've made some notificationsto show: =, [, and
' keys.

OS Language:

English.

And yes, I'm using r4735.

Additional Info: (I'm jumping places to places...Sorry, fgfemperor)

There's no backslash hex code 0x2b detected in Dolphin...There's something missing.

Can you try this patch?

That didn't work out well. :(

Further Investigation:

I'm not using the United States layout.

Instead, it's US-International layout. It's the one with the dead key.
http://en.wikipedia.org/wiki/Keyboard_layout#US-International

I really couldn't think of a better way. However, I didn't come empty-handed.

I did this:

default:
GetKeyNameTextA(keycode << 15, keyStr, 64);
break;

Then press F11, and I got back my missing backslash.

Then I tried many numerous ways to check what value it returned when I press a
specific key button, but in vain. My idea is to use a loop, run a check on what hex
value I got from the inputs I made, make a log of it (them), then debug. But I got
stuck on the first step.

Finally I tried a scanf method. Attached below. I wondered if it break any of your
inputs...It still didn't work. I was thinking of using cout for it though.

Well, That's the layout I'm also using... SInce we got the same layout and the same
configurations, and mine is working and yours isn't... The only thing left to think is
that Acer messed something up... :p
Still gonna investigate it though...

I couldn't agree more.

However, I have this hunch that it's not Acer's fault.

If I can use =, [, and ' to play C.S. 1.6, then it's not either Microsoft's (DirectX,
IME, input detection), Acer's (keyboard layouts and stuffs), or Valve's fault (The
game itself) at all...

The proof of this hunch is below.

I haven't updated Dolphin to the latest rev, but I don't it affects r4738 at all.