Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Bug Could not find active control after binding resolution - On-Screen Button + One Screen Touch

Discussion in 'Input System' started by Meatloaf4, May 26, 2023.

  1. Meatloaf4

    Meatloaf4

    Joined:
    Jul 30, 2013
    Posts:
    183
    As the title states, I get the "Could not find active control after binding resolution" under some peculiar reproducible circumstances. Essentially if I have an On-Screen button on a child gameobject and I toggle the parent gameobject (of the On-Screen button) on and off after touching the screen than the bug occurs.

    Unity Version: 2020.3.46f1
    Input System Package Version: 1.5.1
    Input Actions: Input actions generated by going to PlayerInput component and clicking "Create Actions".

    Repro Steps:
    1. Open the attached scene.
    2. Press play on the unity editor.
    3. Tap the screen anywhere.
    4. Toggle the "Button Container" gameobject on and off until bug occurs.
    No Bug Repro - No Screen Tap
    1. Open the attached scene.
    2. Press play on the unity editor.
    3. Toggle the "Button Container" gameobject on and off (no bug occurs)
    No Bug Repro - No Parent Container Toggle
    1. Open the attached scene.
    2. Press play on the unity editor.
    3. Toggle either of the "Button" or "Button (1)" gameobjects on and off (no bug occurs)
     
  2. radiantboy

    radiantboy

    Joined:
    Nov 21, 2012
    Posts:
    1,633
    Did you ever find a solution?
     
  3. Meatloaf4

    Meatloaf4

    Joined:
    Jul 30, 2013
    Posts:
    183
    Strangely enough my issue wasn't reproducible even on my end after a week or two. That said I updated to the latest input package update and Unity LTS 2022.3 and that did look like it also resolved my issue.
     
  4. radiantboy

    radiantboy

    Joined:
    Nov 21, 2012
    Posts:
    1,633
    Thanks. Im on 2022.2, I think my issue was caused by 2 PlayerInput scripts being active at the same time.
     
    Meatloaf4 likes this.