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. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice
  4. 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 Update to the Unity Editor Software Terms Unite 2023 - Ask the Experts Online Unite 2023 Registrations are now LIVE!

Warning and not receiving device inputs

Discussion in 'Input System' started by rwbrowne, May 18, 2020.

  1. rwbrowne

    rwbrowne

    Joined:
    Apr 1, 2020
    Posts:
    1
    Hello,

    I created a new project today and installed the Input System package 1.0.0. then got the following warning after restarting Unity for the new Input System to take effect. Also device inputs were not detected in the game, but were through the Input Debugger.

    Library\PackageCache\com.unity.inputsystem@1.0.0\InputSystem\Plugins\HID\HID.cs(14,10): warning CS1030: #warning: 'The 32-bit Windows player is not currently supported by the Input System. HID input will not work in the player. Please use x86_64, if possible.'

    I couldn't resolve the problem until I copied files from a previous working project. These were the ".inputactions" and ".inputsetting.asset" files. I also replaced "Library/PackageCache/com.unity.inputsystem@1.0.0" to get things working again.

    I'm using Unity 2019.3.8f1, which might be part of the issue.
     
    rwbrowne, May 18, 2020
    #1
    josiest and MarNevGames like this.

  2. guilhermeraimondi

    guilhermeraimondi

    Joined:
    Apr 7, 2020
    Posts:
    1
    Same here :/
     
    guilhermeraimondi, May 19, 2020
    #2

  3. MiguelBest

    MiguelBest

    Joined:
    Oct 22, 2018
    Posts:
    17
    Same here. Using 2019.3.12f1
     
    MiguelBest, May 19, 2020
    #3

  4. Zanzikahn

    Zanzikahn

    Joined:
    May 14, 2020
    Posts:
    2
    I had the same issue of the build not building because of this error. "UnityEditor.EditorApplication.isPlaying" was the culprit for me.. I guess the game does not want to build if the scripts affect the editor.
     
    Zanzikahn, Jun 6, 2020
    #4

  5. Rene-Damm

    Rene-Damm

    Unity Technologies

    Joined:
    Sep 15, 2012
    Posts:
    1,779
    The warning will not cause a build to fail unless "warnings as errors" is turned on. (Although I've seen some cases a long time ago where problems with the compiler writing files to disk could cause it to *appear* as if the warning made the build fail.)

    Certain device inputs not being detected in the game is due to what the warning says. Switching to x64 in the build settings works around the problem.
     
    Rene-Damm, Jun 8, 2020
    #5
    NicoGm, ToffyLang, marcusmorgan703 and 6 others like this.

  6. GregoryFenn

    GregoryFenn

    Joined:
    Feb 13, 2018
    Posts:
    43
    How?
     
    GregoryFenn, Jun 21, 2020
    #6

  7. Masea1

    Masea1

    Joined:
    Jun 9, 2018
    Posts:
    41
    Masea1, Jun 29, 2020
    #7
    wannachill, NicoGm, joshuaweathersbee2 and 3 others like this.

  8. Deleted User

    Deleted User

    Guest

    Yup! Turning on 64-bit in build settings turned off the warning!
     
    Deleted User, Jul 23, 2020
    #8
    skelozard1, ScarabGameDev, harizsuzairy_unity and 1 other person like this.

  9. Alphawolfme

    Alphawolfme

    Joined:
    Jul 9, 2020
    Posts:
    16
    thanks, was having the same problem
     
    Alphawolfme, Sep 9, 2020
    #9
    ToffyLang likes this.

  10. donovand4

    donovand4

    Joined:
    May 8, 2013
    Posts:
    9
    I am running x64 and I still have the same problem. I only have usage listed under the devices.

    FIXED: Found that you need to add a controller Scheme in the Input Actions before the input paths become available.
     
    donovand4, Nov 12, 2020
    #10