Fizyk
Member
The problem is as follows:
Keys on the keyboard: [ ] \
How Orbiter reads them: <nothing> [ ]
In effect I have no backslash and therefore I can't control retro doors in XR ships (Ctrl-\).
First thing that comes to mind - keyboard layout issues. Well, I ruled that out. I changed my keyboard layout and it didn't change anything. Also, it appears that Orbiter uses keyboard interface independent of keyboard layout, namely scan codes.
Here is the part where it gets really weird - I suspected that for some reason my keyboard sends wrong scan codes and that's why Orbiter can't read them. Therefore I downloaded a program (called Keyboard Test) that shows scan codes for pressed keys. Surprise - scan codes were exactly matching the ones defined in OrbiterAPI.h (the OAPI_KEY_* definitions). So... why the hell does Orbiter read them in such a weird way?
Anyone has any ideas how this can be fixed? Thanks in advance!
Keys on the keyboard: [ ] \
How Orbiter reads them: <nothing> [ ]
In effect I have no backslash and therefore I can't control retro doors in XR ships (Ctrl-\).
First thing that comes to mind - keyboard layout issues. Well, I ruled that out. I changed my keyboard layout and it didn't change anything. Also, it appears that Orbiter uses keyboard interface independent of keyboard layout, namely scan codes.
Here is the part where it gets really weird - I suspected that for some reason my keyboard sends wrong scan codes and that's why Orbiter can't read them. Therefore I downloaded a program (called Keyboard Test) that shows scan codes for pressed keys. Surprise - scan codes were exactly matching the ones defined in OrbiterAPI.h (the OAPI_KEY_* definitions). So... why the hell does Orbiter read them in such a weird way?
Anyone has any ideas how this can be fixed? Thanks in advance!