Search Unity

Resolved [New Input System] InputActions and UI Module "crash" when adding Virtual Mouse on a control scheme

Discussion in 'Editor & General Support' started by DJ_Math, Feb 7, 2023.

  1. DJ_Math

    DJ_Math

    Joined:
    May 7, 2021
    Posts:
    7
    I'm trying to use the new Input System 1.4.4, and pressing keys do nothing in Play Mode.
    I know that one time it worked, but after ...

    When the Input System can't support Keyboards and mouses ?? Or is it simply very special buttons of these devices that are not supported shown in the Input Debug ? It also seems that my wired Controller is entirely marked as unsupported but it works on a Raspberry !
    Unity Input Debug.png
    Here is my Action asset (named PlayerInputActions)
    Unity Input Actions.png
    Switching Control type to "Axis" does nothing
    Switching Action Type to "Pass Through" does nothing
    Restart Unity, disable hybrid boot (WINDOWS ONLY), and reboot the computer do nothing
    Unity OnMoving Callback.png
    Unity Player Input.png

    Is there something I missed ?
     

    Attached Files:

  2. DJ_Math

    DJ_Math

    Joined:
    May 7, 2021
    Posts:
    7
    I've finally found a REAL way to fix my issue above.

    Use Mouse instead of Virtual Mouse (Search for it, and pick the first "[Mouse]" on the list), Virtual Mouse disables the entire asset and even cause UI Input System Module to not work with custom InputActions Asset. Don't forget to mark the Mouse as a required Device in the control scheme.
    Unity InputAction Asset Fix.png
    You don't need to delete your InputActions Asset and the Input System UI Input Module, just remove the Virtual Mouse from your Control scheme.
    Unity InputAction Asset Fix (Searching for Mouse).png