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!

Gear VR Touchpad quirk

Discussion in 'AR/VR (XR) Discussion' started by Mr-Tsunami, Jul 16, 2015.

  1. Mr-Tsunami

    Mr-Tsunami

    Joined:
    Jul 15, 2015
    Posts:
    21
    Hi, I've noticed strange behavior when observing Input.GetAxis("Mouse X") output from Gear VR touchpad.

    The problem is: in the very first frame of touch - when a touch is registered - you can see a non-zero GetAxis() reading. It seems the last touch location is not resetted, remains in memory and is used in calculations.

    The fix is simple, but this behaviour looks like a bug.
     
    Mr-Tsunami, Jul 16, 2015
    #1

  2. shelshok

    shelshok

    Joined:
    Feb 18, 2013
    Posts:
    8
    >The fix is simple, but this behaviour looks like a bug.

    What is the fix?
     
    shelshok, Jul 17, 2015
    #2
    SanSolo likes this.

  3. Mr-Tsunami

    Mr-Tsunami

    Joined:
    Jul 15, 2015
    Posts:
    21
    Simply zero out or discard the first value of Input.GetAxis() on touchdown.
    I use boolean flag to check if the touch is new inside Update()
     
    Mr-Tsunami, Jul 17, 2015
    #3

  4. shelshok

    shelshok

    Joined:
    Feb 18, 2013
    Posts:
    8
    Thanks. I ended up ignoring the input for the first couple frames after the touch.
     
    shelshok, Jul 17, 2015
    #4

  5. thep3000

    thep3000

    Unity Technologies

    Joined:
    Aug 9, 2013
    Posts:
    399
    Thanks, we're investigating where this was introduced. For now please use the workaround described.
     
    thep3000, Jul 20, 2015
    #5

  6. thep3000

    thep3000

    Unity Technologies

    Joined:
    Aug 9, 2013
    Posts:
    399
    We think it's bad data coming from the touchpad driver. Oculus has been alerted but I don't know if it's fixable.
     
    thep3000, Jul 21, 2015
    #6