Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Unite 2023 Registrations are now LIVE! We are thrilled to announce that Unite 2023 Registration is now live and open for all!
    Dismiss Notice
New Forum User Notice Unite 2023 Registrations are now LIVE!

Resolved 2022.1.16f1 not detecting legacy keyboard input

Discussion in 'Scripting' started by seejayjames, Oct 9, 2023.

  1. seejayjames

    seejayjames

    Joined:
    Jan 28, 2013
    Posts:
    685
    Edit---Project Settings---Active Input Handling = Input Manager (Old)
    2021.1.10f1 works fine with the same script.
    I know everything's migrating to the new Input system, but for now this should be supported. What's going on?
     
    seejayjames, Oct 9, 2023
    #1

  2. spiney199

    spiney199

    Joined:
    Feb 11, 2021
    Posts:
    5,883
    That's a pretty randomly old 2022 version. Have you tried the most recent LTS?
     
    spiney199, Oct 9, 2023
    #2

  3. seejayjames

    seejayjames

    Joined:
    Jan 28, 2013
    Posts:
    685
    I did, same result. BUT! I figured it out.
    In Project Settings---Input Manager, "Use Physical Keys" was checked. I often use DVORAK layout so that was causing the problem, the "c" key wasn't in the same location/mapping etc. I swear I tried everything but am not sure how that exactly works.

    All set now, sorry for the noise!
     
    seejayjames, Oct 9, 2023
    #3

  4. CodeSmile

    CodeSmile

    Joined:
    Apr 10, 2014
    Posts:
    4,054
    Note that it makes a difference whether you check for KeyCode.C vs „c“ in the input methods. The latter requires you to press the key that has c written on it, which may be in different physical locations depending on the keyboard layout/locale.
     
    CodeSmile, Oct 9, 2023
    #4
    seejayjames likes this.