I’ve got a new macbook pro… And when I’m attaching FPSControl Script and etc to my moving object (to move and look around) - program responsing only to up,down,left,right - but doesn’t response to any qwerty button… Input Manager doesn’t help. Any ideas? (
I think thar findout what’s happening. If go into Unity->Preferences->Keys - and try to reattach buttons - Unity attach buttons codes ( for example ‘w’ is ‘161’ )… I think thats why in game he can’t see ‘w’,‘a’ and etc… But how to solve it? ((
That sounds like some major problem with the OS, unity is working fine with key specifications for all others.
Perhaps its also running on IME or something alike that messes up the keycodes (cause w = 161 can’t be thats neither the ASCII nor the scancode of w / W)
function OnGUI() {
var e : Event = Event.current;
if (e.isKey) {
Debug.Log("Detected key code: " + e.keyCode);
}
}
this code on w pressed return 161 or 174 ( i can’t say for sure for this moment ) …
function OnGUI() {
var e : Event = Event.current;
if (e.isKey) {
Debug.Log("Detected key code: " + e.character);
}
}
This code print w if w is pressed. SO i’m absolutely confused, why unity doesn’t work correctly (((
It prints the characters here; pressing w prints “W”. This is on a Mac Pro running 10.6.4.
–Eric
I’ve got the same system version.
I think that the problem connected with this effect @ If go into Unity->Preferences->Keys - and try to reattach buttons - Unity attach buttons codes ( for example ‘w’ is ‘172’ )@… But I have no idea what to do… Reinstalling the system is quite radical method ((
“Support” - are you here?
Update.
Actually I’ve found one solving of my problem. Unity works fine only if I switch my system to english. ( couse previously I’ve got russian). But it’s can be only temporarily solution…cause won’t like to switch they system to another language from native… May be “suppot” will know some solution? (
Welcome to the forum, Gube!
There are a few issues in the bug database that happen with the system language set to Russian, but they all appear to be related to editor keystrokes, not the Input class. Perhaps you can check if the issue still occurs with Unity 3.1 (if you haven’t already) and then file a bug report if it hasn’t been fixed.
I’ve got 3.1 already And sent bug-report.
Unity started to work correctly with russian system language(i doesn’t mean keyboard layout, but SYSTEM language) after several times of switching system language between russian<->english… Now it’s alright… but there is definetly something wrong