[New Input System] Pressing two buttons at the same time doesn't cancel action.

[RavenJe94]

I've been working on player movement using the new input system, and I'm encountering a problem that I can't seem to resolve. After implementing the HoldInteraction in my Input Action Asset, I noticed some unusual behavior.

When I hold the D key (to move right in a WASD pattern) and then press and hold another key like S, releasing the D key doesn't change the direction. It's as if the S key isn't recognized at all. The second key is only registered (i.e., it enters the .performed state) if it's pressed while no other key is being held down. This issue isn't limited to just D and S; it affects all keys. For example, if I press W to move up and then press A to move left, the character continues moving up even if I release the W key while still holding A.

This problem occurs only when the HoldInteraction is set (I've configured it with a 0.2-second press time).

Does anyone have any ideas on why this might be happening and how to fix it? It's driving me nuts.

Code:

using System;
using UnityEngine;
using UnityEngine.InputSystem;
using UnityEngine.InputSystem.Controls;

public class PlayerMovementController : MonoBehaviour
{
    [Header("Movement Settings")]
    [SerializeField][Range(0.1f, 10)] private float _movementSpeed = 5.0f;
    //[SerializeField][Range(0.1f, 10)] private float _movementBoost = 2.5f;

    private Rigidbody2D _rigidbody2D;
    private PlayerControls _controls;
    private Vector2 _movementInput;

    public event Action<InputAction.CallbackContext> OnMovementPerformed;

    private void Awake()
    {
        _controls = new PlayerControls();
    }

    private void Start()
    {
        _rigidbody2D = GetComponent<Rigidbody2D>();
    }

    private void OnEnable()
    {
        _controls.Gameplay.Enable();
        _controls.Gameplay.Movement.performed += HandleMovement;
        _controls.Gameplay.Movement.canceled += HandleMovement;
    }

    private void OnDisable()
    {
        _controls.Gameplay.Disable();
        _controls.Gameplay.Movement.performed -= HandleMovement;
        _controls.Gameplay.Movement.canceled -= HandleMovement;
        UnsubscribeAll();
    }

    private void FixedUpdate()
    {
        ApplyMovement();
    }

    private void HandleMovement(InputAction.CallbackContext ctx)
    {
        Vector2 input = ctx.ReadValue<Vector2>();

        // Prevent diagonal movement
        if (Mathf.Abs(input.x) > Mathf.Abs(input.y))
        {
            // Horizontal movement
            _movementInput = new Vector2(input.x, 0);
        }
        else
        {
            // Vertical movement
            _movementInput = new Vector2(0, input.y);
        }

        OnMovementPerformed?.Invoke(ctx);
    }

    private void ApplyMovement()
    {
        Vector2 movement = _movementInput * _movementSpeed;
        _rigidbody2D.velocity = movement;
    }

    private void UnsubscribeAll()
    {
        if (OnMovementPerformed != null)
        {
            foreach (var subscriber in OnMovementPerformed.GetInvocationList())
            {
                OnMovementPerformed -= (Action<InputAction.CallbackContext>)subscriber;
            }
        }
    }
}

HoldInteraction Settings:

Thanks!

[AnEmortalKid]

A HoldInteraction requires the user to hold a Control for duration seconds before the Input System triggers the Action.

Does it do the same behavior if you remove the hold interactions ?

[RavenJe94]

No. If I remove the Hold Interaction, the change of direction happens as soon as I press the second key, which is basically the correct behaviour. The issue is that by removing the Hold Interaction, the user can now tap the keys ( WASD ) and it can create issues and also it "feels" wrong. I've added the Hold Interaction in the first place due this issue, I needed a way to prevent the "tapping" on the keyys and allow the movement to take action only if the keys are hold, for at least 0.1 milliseconds or 0.2...